Fixing broken links

Author: dylburger

docs-v2/pages/cli/reference.mdx

@@ -304,7 +304,7 @@ You can also run `pd signup -p <profile>` if you'd like to sign up for a new Pip
 
 If you're working with resources in an [workspace](/workspaces/), you'll need to add an `org_id` to your profile.
 
-1. [Retrieve your workspaces's ID](/workspaces/#finding-your-workspace-s-id)
+1. [Retrieve your workspaces's ID](/workspaces/#finding-your-workspaces-id)
 2. Open up your [Pipedream config file](#cli-config-file) and create a new [profile](#profiles) with the following information:
 
 ```bash

docs-v2/pages/code/nodejs/delay.mdx

@@ -5,11 +5,9 @@ import VideoPlayer from '@/components/VideoPlayer'
 
 <VideoPlayer title="Delaying Workflow Steps" src="https://www.youtube.com/embed/IBORwBnIZ-k" startAt="148" />
 
-Use `$.flow.delay` to [delay a step in a workflow](/workflows/flow-control/#delay).
-
-These docs show you how to write Node.js code to handle delays. If you don't need to write code, see [our built-in delay actions](/workflows/flow-control/#delay-actions).
-
+Use `$.flow.delay` to [delay a step in a workflow](/workflows/control-flow/delay).
 
+These docs show you how to write Node.js code to handle delays. If you don't need to write code, see [our built-in delay actions](/workflows/control-flow/delay#delay-actions).
 
 ## Using `$.flow.delay`
 
@@ -96,7 +94,7 @@ export default defineComponent({
 
 ## When delays happen
 
-**Pipedream pauses your workflow at the _end_ of the step where you call `$.flow.delay`**. This lets you [send the `cancel_url` and `resume_url` to third-party systems](#cancel-url-and-resume-url).
+**Pipedream pauses your workflow at the _end_ of the step where you call `$.flow.delay`**. This lets you [send the `cancel_url` and `resume_url` to third-party systems](#cancel_url-and-resume_url).
 
 ```javascript
 export default defineComponent({

docs-v2/pages/code/nodejs/index.mdx

@@ -170,7 +170,7 @@ This defines [a Node.js component](/components/api/). Components let you:
 
 - Pass input to steps using [props](/code/nodejs/#passing-props-to-code-steps)
 - [Connect an account to a step](/connected-accounts/#from-a-code-step)
-- [Issue HTTP responses](/workflows/steps/triggers/#http-responses)
+- [Issue HTTP responses](/workflows/triggers/#http-responses)
 - Perform workflow-level flow control, like [ending a workflow early](#ending-a-workflow-early)
 
 When the step runs, Pipedream executes the `run` method:
@@ -190,7 +190,7 @@ export default defineComponent({
 });
 ```
 
-When you [connect an account to a step](/connected-accounts/#from-a-code-step), Pipedream exposes the auth info in the variable [`this.appName.$auth`](/code/nodejs/auth/#accessing-connected-account-data-with-this-appname-auth).
+When you [connect an account to a step](/connected-accounts/#from-a-code-step), Pipedream exposes the auth info in the variable [`this.appName.$auth`](/code/nodejs/auth/#accessing-connected-account-data-with-thisappnameauth).
 
 ## Logs
 
@@ -344,13 +344,13 @@ Within a step, the [normal rules of JavaScript variable scope](https://developer
 There are two ways to make HTTP requests in code steps:
 
 - Use any HTTP client that works with Node.js. [See this example guide for how to use `axios` to make HTTP requests](/code/nodejs/http-requests/).
-- [Use `$.send.http()`](/destinations/http/#using-send-http-in-workflows), a Pipedream-provided method for making asynchronous HTTP requests.
+- [Use `$.send.http()`](/destinations/http/#using-sendhttp-in-workflows), a Pipedream-provided method for making asynchronous HTTP requests.
 
-In general, if you just need to make an HTTP request but don't care about the response, [use `$.send.http()`](/destinations/http/#using-send-http-in-workflows). If you need to operate on the data in the HTTP response in the rest of your workflow, [use `axios`](/code/nodejs/http-requests/).
+In general, if you just need to make an HTTP request but don't care about the response, [use `$.send.http()`](/destinations/http/#using-sendhttp-in-workflows). If you need to operate on the data in the HTTP response in the rest of your workflow, [use `axios`](/code/nodejs/http-requests/).
 
 ## Returning HTTP responses
 
-You can return HTTP responses from [HTTP-triggered workflows](/workflows/steps/triggers/#http) using the [`$.respond()` function](/workflows/steps/triggers/#http-responses).
+You can return HTTP responses from [HTTP-triggered workflows](/workflows/triggers/#http) using the [`$.respond()` function](/workflows/triggers/#http-responses).
 
 ## Invoke another workflow
 

docs-v2/pages/code/nodejs/rerun.mdx

@@ -63,7 +63,7 @@ If you resume a workflow, any data sent in the HTTP request is passed to the wor
 />
 <br />
 
-Requests to the `resume_url` have [the same limits as any HTTP request to Pipedream](/limits/#http-request-body-size), but you can send larger payloads using our [large payload](/workflows/steps/triggers/#sending-large-payloads) or [large file](/workflows/steps/triggers/#large-file-support) interfaces.
+Requests to the `resume_url` have [the same limits as any HTTP request to Pipedream](/limits/#http-request-body-size), but you can send larger payloads using our [large payload](/workflows/triggers/#sending-large-payloads) or [large file](/workflows/triggers/#large-file-support) interfaces.
 
 ### Default timeout of 24 hours
 

docs-v2/pages/code/nodejs/sharing-code.mdx

@@ -7,7 +7,7 @@ import VideoPlayer from '@/components/VideoPlayer'
 
 Pipedream provides two ways to share code across workflows:
 
-- **Publish an action from a Node.js code step**. [Publish any Node.js code step as a reusable action](/code/nodejs/sharing-code/#publish-an-action-from-a-node-js-code-step) from the Pipedream dashboard.
+- **Publish an action from a Node.js code step**. [Publish any Node.js code step as a reusable action](/code/nodejs/sharing-code/#publish-an-action-from-a-nodejs-code-step) from the Pipedream dashboard.
 
 - **Create an action from code**. Develop your action code on your local filesystem and [publish to your Pipedream account using the Pipedream CLI](/components/quickstart/nodejs/actions/).
 
@@ -137,7 +137,7 @@ No, a new version of an action doesn't automatically update all instances of the
 This gives you the control to gradually update. Learn how to [update steps to the newest action versions here](https://pipedream.com/docs/workflows/steps/actions/#updating-actions-to-the-latest-version).
 </Callout>
 
-After publishing a new version, all other steps using this same action will have the option to [update to the latest version](/workflows/steps/actions/#updating-actions-to-the-latest-version).
+After publishing a new version, all other steps using this same action will have the option to [update to the latest version](/workflows/actions/#updating-actions-to-the-latest-version).
 
 ## Differences between publishing actions from workflow Node.js code steps and directly from code
 

docs-v2/pages/code/python/delay.mdx

@@ -2,9 +2,9 @@ import Callout from '@/components/Callout'
 
 # Delaying a workflow
 
-Use `pd.flow.delay` to [delay a step in a workflow](/workflows/flow-control/#delay).
+Use `pd.flow.delay` to [delay a step in a workflow](/workflows/control-flow/delay).
 
-These docs show you how to write Python code to handle delays. If you don't need to write code, see [our built-in delay actions](/workflows/flow-control/#delay-actions).
+These docs show you how to write Python code to handle delays. If you don't need to write code, see [our built-in delay actions](/workflows/control-flow/delay#delay-actions).
 
 ## Using `pd.flow.delay`
 
@@ -91,7 +91,7 @@ In `pd.send.email`, the `html` argument defaults to `""`, so it overrides the em
 
 ## When delays happen
 
-**Pipedream pauses your workflow at the _end_ of the step where you call `pd.flow.delay`**. This lets you [send the `cancel_url` and `resume_url` to third-party systems](#cancel-url-and-resume-url).
+**Pipedream pauses your workflow at the _end_ of the step where you call `pd.flow.delay`**. This lets you [send the `cancel_url` and `resume_url` to third-party systems](cancel_url-and-resume_url).
 
 ```python
 def handler(pd: 'pipedream'):
@@ -108,7 +108,7 @@ You cannot run `pd.respond` after running `pd.flow.delay`. Pipedream ends the or
 
 > $.respond() not called for this invocation
 
-If you need to set a delay on an HTTP request triggered workflow, consider using [`time.sleep`](#time-sleep) instead.
+If you need to set a delay on an HTTP request triggered workflow, consider using [`time.sleep`](#timesleep) instead.
 
 ## `time.sleep`
 

docs-v2/pages/code/python/index.mdx

@@ -104,7 +104,7 @@ See the [Making HTTP Requests with Python](/code/python/http-requests/) docs for
 
 ## Returning HTTP responses
 
-You can return HTTP responses from [HTTP-triggered workflows](/workflows/steps/triggers/#http) using the `pd.respond()` method:
+You can return HTTP responses from [HTTP-triggered workflows](/workflows/triggers/#http) using the `pd.respond()` method:
 
 ```python
 def handler(pd: "pipedream"):
@@ -123,7 +123,7 @@ Unlike the [Node.js equivalent](https://pipedream.com/docs/workflows/steps/trigg
 </Callout>
 
 <Callout type="info">
-_Don't forget_ to [configure your workflow's HTTP trigger to allow a custom response](/workflows/steps/triggers/#http-responses). Otherwise your workflow will return the default response.
+_Don't forget_ to [configure your workflow's HTTP trigger to allow a custom response](/workflows/triggers/#http-responses). Otherwise your workflow will return the default response.
 </Callout>
 
 ## Sharing data between steps

docs-v2/pages/components/api.mdx

@@ -20,7 +20,7 @@ Components are Node.js modules that run on Pipedream's serverless infrastructure
 
 - Trigger Node.js code on HTTP requests, timers, cron schedules, or manually
 - Emit data on each event to inspect it. Trigger Pipedream hosted workflows or access it outside of Pipedream via API
-- Accept user input on deploy via [CLI](/cli/reference/#pd-deploy), [API](/api/rest/#overview), or [UI](https://pipedream.com/sources)
+- Accept user input on deploy via [CLI](/cli/reference/#pd-deploy), [API](/rest-api/#overview), or [UI](https://pipedream.com/sources)
 - Connect to [{process.env.PUBLIC_APPS}+ apps](https://pipedream.com/apps) using Pipedream managed auth
 - Use most npm packages with no `npm install` or `package.json` required
 - Store and retrieve state using the [built-in key-value store](#db)
@@ -878,7 +878,7 @@ When your workflow runs, you'll see the named exports appear below your step, wi
 
 ##### Returning HTTP responses with `$.respond`
 
-`$.respond` lets you issue HTTP responses from your workflow. [See the full `$.respond` docs for more information](/workflows/steps/triggers/#customizing-the-http-response).
+`$.respond` lets you issue HTTP responses from your workflow. [See the full `$.respond` docs for more information](/workflows/triggers/#customizing-the-http-response).
 
 ```javascript
 async run({ $ }) {
@@ -924,35 +924,35 @@ $.export(
 
 **`$.send.http`**
 
-[See the HTTP destination docs](/destinations/http/#using-send-http-in-component-actions).
+[See the HTTP destination docs](/destinations/http/#using-sendhttp-in-component-actions).
 
 **`$.send.email`**
 
-[See the Email destination docs](/destinations/email/#using-send-email-in-component-actions).
+[See the Email destination docs](/destinations/email/#using-sendemail-in-component-actions).
 
 **`$.send.s3`**
 
-[See the S3 destination docs](/destinations/s3/#using-send-s3-in-component-actions).
+[See the S3 destination docs](/destinations/s3/#using-sends3-in-component-actions).
 
 **`$.send.emit`**
 
-[See the Emit destination docs](/destinations/emit/#using-send-emit-in-component-actions).
+[See the Emit destination docs](/destinations/emit/#using-sendemit-in-component-actions).
 
 **`$.send.sse`**
 
-[See the SSE destination docs](/destinations/sse/#using-send-sse-in-component-actions).
+[See the SSE destination docs](/destinations/sse/#using-sendsse-in-component-actions).
 
 ##### `$.context`
 
-`$.context` exposes [the same properties as `steps.trigger.context`](/workflows/events/#steps-trigger-context), and more. Action authors can use it to get context about the calling workflow and the execution.
+`$.context` exposes [the same properties as `steps.trigger.context`](/workflows/events/#stepstriggercontext), and more. Action authors can use it to get context about the calling workflow and the execution.
 
-All properties from [`steps.trigger.context`](/workflows/events/#steps-trigger-context) are exposed, as well as:
+All properties from [`steps.trigger.context`](/workflows/events/#stepstriggercontext) are exposed, as well as:
 
 | Property   |                                                                       Description                                                                       |
 | ---------- | :-----------------------------------------------------------------------------------------------------------------------------------------------------: |
 | `deadline` |               An epoch millisecond timestamp marking the point when the workflow is configured to [timeout](/limits/#time-per-execution).               |
 | `JIT`      |             Stands for "just in time" (environment). `true` if the user is testing the step, `false` if the step is running in production.              |
-| `run`      | An object containing metadata about the current run number. See [the docs on `$.flow.rerun`](/workflows/events/#steps-trigger-context) for more detail. |
+| `run`      | An object containing metadata about the current run number. See [the docs on `$.flow.rerun`](/workflows/events/#stepstriggercontext) for more detail. |
 
 ### Environment variables
 
@@ -1096,7 +1096,7 @@ You can delete a component via the UI at [https://pipedream.com/sources](https:/
 
 #### API
 
-See the [REST API docs](/api/rest/).
+See the [REST API docs](/rest-api/).
 
 ### Managing Actions
 
@@ -1201,7 +1201,7 @@ When you navigate to your source [in the UI](https://pipedream.com/sources), you
 
 #### API
 
-Events can be retrieved using the [REST API](/api/rest/) or [SSE stream tied to your component](/api/sse/). This makes it easy to retrieve data processed by your component from another app. Typically, you'll want to use the [REST API](/api/rest/) to retrieve events in batch, and connect to the [SSE stream](/api/sse/) to process them in real time.
+Events can be retrieved using the [REST API](/rest-api) or [SSE stream tied to your component](/api/sse/). This makes it easy to retrieve data processed by your component from another app. Typically, you'll want to use the [REST API](/rest-api) to retrieve events in batch, and connect to the [SSE stream](/api/sse/) to process them in real time.
 
 #### CLI
 

docs-v2/pages/components/guidelines.mdx

@@ -795,7 +795,7 @@ comply with some requirements. The most important features are:
    against their DB
 2. Proxied execution of commands against a DB, which guarantees that such
    requests are always being made from the same range of static IPs (see the
-   [shared static IPs docs](databases#send-requests-from-a-shared-static-ip))
+   [shared static IPs docs](/databases#send-requests-from-a-shared-static-ip))
 
 When dealing with database components, the Pipedream runtime performs certain
 actions internally to make these features work. For this reason, these

docs-v2/pages/connect/api.mdx

@@ -293,13 +293,13 @@ GET /{project_id}/accounts/
 
 The ID or name slug the app you'd like to retrieve. For example, Slack's unique app ID is `app_OkrhR1`, and its name slug is `slack`.
 
-You can find the app's ID in the response from the [List apps](#list-apps) endpoint, and the name slug under the **Authentication** section of any [app page](https://pipedream.com/apps).
+You can find the app's ID in the response from the [List apps](/rest-api#list-apps) endpoint, and the name slug under the **Authentication** section of any [app page](https://pipedream.com/apps).
 
 ---
 
 `oauth_app_id` **string** (_optional_)
 
-The ID of the custom [OAuth app](/connect/quickstart#creating-a-custom-oauth-client) you'd like to retrieve accounts for.
+The ID of the custom [OAuth app](/connect/quickstart#create-a-pipedream-oauth-client) you'd like to retrieve accounts for.
 
 ---
 
@@ -707,7 +707,7 @@ DELETE /{project_id}/apps/{app_id}/accounts
 
 `app_id` **string**
 
-The app ID for which you want to delete all connected accounts. `app_id` can be `oauth_app_id` for [OAuth apps](/connect/quickstart#creating-a-custom-oauth-client) or [name slug](/connect/quickstart/#find-your-apps-name-slug) for key-based apps.
+The app ID for which you want to delete all connected accounts. `app_id` can be `oauth_app_id` for [OAuth apps](/connect/quickstart#create-a-pipedream-oauth-client) or name slug for key-based apps, which you can find under the **Authentication** section of any [app page](https://pipedream.com/apps)
 
 ##### Examples