Handling in-app docs links

Author: dannyroosevelt

docs-v2/pages/account/user-settings.mdx

@@ -50,7 +50,7 @@ Pipedream recommends enabling 2FA with your identity provider.
 
 ### Requiring 2-Factor Authentication
 
-Workspaces on the Business plan can [require all workspace members to configure 2FA](/workflows/workspaces/#requiring-two-factor-authentication) in order to log in to Pipedream.
+Workspaces on the Business plan can [require all workspace members to configure 2FA](/workspaces/#requiring-two-factor-authentication) in order to log in to Pipedream.
 
 If you are a member of any workspace where 2FA is required, you cannot disable 2FA, but you can still reconfigure it in your [account settings](https://pipedream.com/account/) if necessary.
 

docs-v2/pages/apps/apps.mdx

@@ -6,8 +6,8 @@ Pipedream has built-in integrations with more than {process.env.PUBLIC_APPS} app
 
 But Pipedream-integrated apps provide a few benefits:
 
-- You can [connect the app once](/integrations/connected-accounts/) and [link that connected account to any step of a workflow](/integrations/connected-accounts/#connecting-accounts)
-- Pipedream provides [pre-built actions](/workflows/contributing/components/#actions) that wrap common operations for the app. You shouldn't have to write the code to send a message to Slack, or add a new row to a Google Sheet, so actions make that easy. Actions are just code, so you can fork and modify them, or even [publish your own to the Pipedream community](/workflows/contributing/).
+- You can [connect the app once](/apps/connected-accounts/) and [link that connected account to any step of a workflow](/apps/connected-accounts/#connecting-accounts)
+- Pipedream provides [pre-built actions](/components/contributing/#actions) that wrap common operations for the app. You shouldn't have to write the code to send a message to Slack, or add a new row to a Google Sheet, so actions make that easy. Actions are just code, so you can fork and modify them, or even [publish your own to the Pipedream community](/components/contributing/).
 - [You have access to your API keys and access tokens in code steps](/workflows/building-workflows/code/nodejs/auth/), so you can write any code to authorize custom requests to these apps.
 
 ## Premium Apps
@@ -73,7 +73,7 @@ The vast majority of integrated apps on Pipedream are free to use in your workfl
 
 <Callout type="info">
 Missing an integration?
-If we don't have an integration for an app that you'd like to see, please [let us know](https://pipedream.com/support) or [contribute it to the source available Pipedream registry](/workflows/contributing/).
+If we don't have an integration for an app that you'd like to see, please [let us know](https://pipedream.com/support) or [contribute it to the source available Pipedream registry](/components/contributing/).
 </Callout>
 
 **Check out the full list of integrated apps [here](https://pipedream.com/apps).**

docs-v2/pages/apps/connected-accounts.mdx

@@ -12,7 +12,7 @@ Pipedream provides native integrations for [{process.env.PUBLIC_APPS}+ APIs](htt
 
 Pipedream handles OAuth for you, ensuring you always have a fresh access token to authorize requests, and [credentials are tightly-secured](/privacy-and-security/#third-party-oauth-grants-api-keys-and-environment-variables).
 
-If you use an existing secrets store, or manage credentials in a database, you can also [pass those to Pipedream at runtime](/integrations/connected-accounts/external-auth/) instead of connecting accounts in the UI.
+If you use an existing secrets store, or manage credentials in a database, you can also [pass those to Pipedream at runtime](/apps/connected-accounts/external-auth/) instead of connecting accounts in the UI.
 
 ## Supported Apps
 
@@ -236,7 +236,7 @@ You can access credentials for any connected account via API, letting you build
 
 ## Passing external credentials at runtime
 
-If you use a secrets store like [Pipedream Connect](/connect/) or [HashiCorp Vault](https://www.vaultproject.io/), or if you store credentials in a database, you can retrieve these secrets at runtime and pass them to any step. [See the full guide here](/integrations/connected-accounts/external-auth/).
+If you use a secrets store like [Pipedream Connect](/connect/) or [HashiCorp Vault](https://www.vaultproject.io/), or if you store credentials in a database, you can retrieve these secrets at runtime and pass them to any step. [See the full guide here](/apps/connected-accounts/external-auth/).
 
 ## Connecting to apps with IP restrictions
 

docs-v2/pages/apps/external-auth.mdx

@@ -19,7 +19,7 @@ Passing external credentials at runtime is a feature that's available to custome
 2. From your app, retrieve credentials and send them in an HTTP request to the endpoint with the rest of the payload.
 3. In the step of your workflow where you'd like to pass these credentials, select the **Use external authentication** option at the bottom-right of the account selector:
 
-![Select "External Auth"](/images/integrations/select-external-auth.png)
+![Select "External Auth"](/images/apps/select-external-auth.png)
 
 4. You'll be prompted for all required credentials for the app, often just an `oauth_access_token` or `api_key`. [Find the variable that contains your credentials](/workflows/building-workflows/triggers/#copying-references-to-event-data) and pass them to each field:
 
@@ -42,7 +42,7 @@ You can set [the `pd-nostore` flag](/workflows/building-workflows/triggers/#x-pd
 1. Add a step to your workflow to fetch credentials from your DB or secrets store.
 2. In the step of your workflow where you'd like to pass these credentials, select the **Use external authentication** option at the bottom-right of the account selector:
 
-![Select "External Auth"](/images/integrations/select-external-auth.png)
+![Select "External Auth"](/images/apps/select-external-auth.png)
 
 3. You'll be prompted for all required credentials for the app, often just an `oauth_access_token` or `api_key`. [Find the variable that contains your credentials](/workflows/building-workflows/triggers/#copying-references-to-event-data) and pass them to each field:
 

docs-v2/pages/components/contributing/actions-quickstart.mdx

@@ -6,7 +6,7 @@ import Callout from '@/components/Callout'
 
 ## Overview
 
-This document is intended for developers who want to author and edit [Pipedream Actions](/workflows/contributing/components/#actions). After completing this quickstart, you'll understand how to:
+This document is intended for developers who want to author and edit [Pipedream Actions](/components/contributing/#actions). After completing this quickstart, you'll understand how to:
 
 - Develop Pipedream components
 - Publish private actions and use them in workflows
@@ -16,7 +16,7 @@ This document is intended for developers who want to author and edit [Pipedream
 - Use Pipedream managed auth for a 3rd party app
 
 <Callout type="info">
-If you previously developed actions using Pipedream's UI, we recommend reviewing our [migration guide](/workflows/contributing/components/migrating/) after completing this quickstart.
+If you previously developed actions using Pipedream's UI, we recommend reviewing our [migration guide](/components/contributing/migrating/) after completing this quickstart.
 </Callout>
 
 ## Prerequisites
@@ -57,7 +57,7 @@ We recommend that you complete the examples below in order.
 
 ### hello world!
 
-The following code represents a simple component that can be published as an action ([learn more](/workflows/contributing/components/api/) about the component structure). When used in a workflow, it will export `hello world!` as the return value for the step.
+The following code represents a simple component that can be published as an action ([learn more](/components/contributing/api/) about the component structure). When used in a workflow, it will export `hello world!` as the return value for the step.
 
 ```javascript
 export default {
@@ -109,7 +109,7 @@ Keep the browser tab open. We'll return to this workflow in the rest of the exam
 
 ### hello [name]!
 
-Next, let's update the component to capture some user input. First, add a `string` [prop](/workflows/contributing/components/api/#props) called `name` to the component.
+Next, let's update the component to capture some user input. First, add a `string` [prop](/components/contributing/api/#props) called `name` to the component.
 
 ```java
 export default {
@@ -340,7 +340,7 @@ export default {
 };
 ```
 
-Then add an [app prop](/workflows/contributing/components/api/#app-props) to use Pipedream managed auth with this component. For this example, we'll add an app prop for Github:
+Then add an [app prop](/components/contributing/api/#app-props) to use Pipedream managed auth with this component. For this example, we'll add an app prop for Github:
 
 ```javascript
 import { Octokit } from "@octokit/rest";
@@ -397,7 +397,7 @@ export default {
 };
 ```
 
-In order to help users understand what's happening with each action step, we recommend surfacing a brief summary with `$summary` ([read more](/workflows/contributing/components/api/#actions) about exporting data using `$.export`).
+In order to help users understand what's happening with each action step, we recommend surfacing a brief summary with `$summary` ([read more](/components/contributing/api/#actions) about exporting data using `$.export`).
 
 ```javascript
 import { Octokit } from "@octokit/rest";
@@ -486,6 +486,6 @@ Select an existing account or connect a new one, and then deploy your workflow a
 
 ## What's Next?
 
-You're ready to start authoring and publishing actions on Pipedream! You can also check out the [detailed component reference](/workflows/contributing/components/api/#component-api) at any time!
+You're ready to start authoring and publishing actions on Pipedream! You can also check out the [detailed component reference](/components/contributing/api/#component-api) at any time!
 
 If you have any questions or feedback, please [reach out](https://pipedream.com/community)!