fix broken links

Author: andrewjschuang

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

@@ -82,4 +82,4 @@ For example, you can:
 
 ## Environment Variables
 
-Environment variables allow you to securely store secrets or other config values that you can access in Pipedream workflows via `process.env`. [Read more about environment variables here](/environment-variables/).
+Environment variables allow you to securely store secrets or other config values that you can access in Pipedream workflows via `process.env`. [Read more about environment variables here](/workflows/environment-variables/).

docs-v2/pages/connect/api.mdx

@@ -7,7 +7,7 @@ Pipedream provides a TypeScript SDK and a REST API to interact with the Connect
 
 ## REST API base URL
 
-Pipedream Connect resources are scoped to [projects](/projects), so you'll need to pass [the project's ID](/projects#finding-your-projects-id) as a part of the base URL:
+Pipedream Connect resources are scoped to [projects](/projects), so you'll need to pass [the project's ID](/workflows/projects#finding-your-projects-id) as a part of the base URL:
 
 ```
 https://api.pipedream.com/v1/connect/{project_id}
@@ -249,7 +249,7 @@ POST /{project_id}/tokens
 
 `project_id` **string**
 
-[The project's ID](/projects#finding-your-projects-id)
+[The project's ID](/workflows/projects#finding-your-projects-id)
 
 ##### Body parameters
 
@@ -394,15 +394,15 @@ GET /{project_id}/accounts/
 
 `project_id` **string**
 
-[The project's ID](/projects#finding-your-projects-id)
+[The project's ID](/workflows/projects#finding-your-projects-id)
 
 ##### Query parameters
 
 `app` **string** (_optional_)
 
 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](/rest-api#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](/workflows/rest-api#list-apps) endpoint, and the name slug under the **Authentication** section of any [app page](https://pipedream.com/apps).
 
 ---
 
@@ -661,7 +661,7 @@ GET /{project_id}/accounts/{account_id}
 
 `project_id` **string**
 
-[The project's ID](/projects#finding-your-projects-id)
+[The project's ID](/workflows/projects#finding-your-projects-id)
 
 ---
 
@@ -834,7 +834,7 @@ DELETE /{project_id}/accounts/{account_id}
 
 `project_id` **string**
 
-[The project's ID](/projects#finding-your-projects-id)
+[The project's ID](/workflows/projects#finding-your-projects-id)
 
 ---
 
@@ -921,7 +921,7 @@ DELETE /{project_id}/apps/{app_id}/accounts
 
 `project_id` **string**
 
-[The project's ID](/projects#finding-your-projects-id)
+[The project's ID](/workflows/projects#finding-your-projects-id)
 
 ---
 
@@ -1010,7 +1010,7 @@ DELETE /{project_id}/users/{external_user_id}
 
 `project_id` **string**
 
-[The project's ID](/projects#finding-your-projects-id)
+[The project's ID](/workflows/projects#finding-your-projects-id)
 
 ---
 
@@ -1112,7 +1112,7 @@ 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](/rest-api#list-apps) endpoint, and the name slug under the
+apps](/workflows/rest-api#list-apps) endpoint, and the name slug under the
 **Authentication** section of any [app page](https://pipedream.com/apps).
 
 ---

docs-v2/pages/connect/components.mdx

@@ -33,7 +33,7 @@ Check out the [public demo app](https://pdrm.co/connect) to see the API and SDK
 <Callout type="info">
 Refer to the [Connect API docs](/connect/api) for the full API reference. Below is a quickstart with a few specific examples.
 
-You can skip steps 1 and 2 if you already know the component you want to use or if you'd prefer to [pass a natural language prompt to Pipedream's component search API](/rest-api#search-for-registry-components).
+You can skip steps 1 and 2 if you already know the component you want to use or if you'd prefer to [pass a natural language prompt to Pipedream's component search API](/workflows/rest-api#search-for-registry-components).
 </Callout>
 
 <Steps>

docs-v2/pages/connect/managed-auth/oauth-clients.mdx

@@ -28,7 +28,7 @@ For any OAuth app that supports it, **you can always use your own client.** Your
 
 ## Using a custom OAuth client
 
-1. Follow the steps [here](/workflows/integrations/connected-accounts/oauth-clients#configuring-custom-oauth-clients) to create an OAuth client in Pipedream.
+1. Follow the steps [here](/workflows/integrations/oauth-clients#configuring-custom-oauth-clients) to create an OAuth client in Pipedream.
 2. When connecting an account either via the [frontend SDK](/connect/managed-auth/quickstart#use-the-pipedream-sdk-in-your-frontend), make sure to include the `oauthAppId` in `pd.connectAccount()`.
 3. If using [Connect Link](/connect/managed-auth/quickstart#or-use-connect-link), make sure to include the `oauthAppId` in the URL.
 

docs-v2/pages/connect/workflows.mdx

@@ -15,13 +15,13 @@ Whether you're building well-defined integrations or autonomous AI agents, workf
 <img width="500px" src="https://res.cloudinary.com/pipedreamin/image/upload/v1730935490/docs/pCBdtm7Ca9CdPHTe76PwfzddY_qowz2v.avif" />
 </div>
 
-Workflows are sequences of [steps](/workflows/steps) [triggered by an event](/docs/workflows/visual-builder/triggers), like an HTTP request, or new rows in a Google sheet.
+Workflows are sequences of [steps](/workflows/steps) [triggered by an event](/workflows/visual-builder/triggers), like an HTTP request, or new rows in a Google sheet.
 
 You can use [pre-built actions](/workflows/actions/) or custom [Node.js](/workflows/visual-builder/code/nodejs/), [Python](/workflows/visual-builder/code/python), [Golang](/workflows/visual-builder/code/go/), or [Bash](/workflows/visual-builder/code/bash/) code in workflows and connect to any of our {process.env.PUBLIC_APPS} integrated apps.
 
 Workflows also have built-in:
 
-- [Flow control](/workflows/control-flow)
+- [Flow control](/workflows/visual-builder/control-flow)
 - [Concurrency and throttling](/workflows/concurrency-and-throttling)
 - [Key-value stores](/data-stores)
 - [Error handling](/workflows/errors)
@@ -36,13 +36,13 @@ Read [the quickstart](/quickstart/) to learn more.
 
 ### Create a workflow
 
-[Create a new workflow](/workflows#how-do-i-create-a-new-workflow) or open an existing one.
+[Create a new workflow](/workflows) or open an existing one.
 
 ### Add an HTTP trigger
 
 To get started building workflows for your end users:
 
-1. Add an [HTTP trigger](/docs/workflows/visual-builder/triggers#http) to your workflow
+1. Add an [HTTP trigger](/workflows/visual-builder/triggers#http) to your workflow
 2. Generate a test event with the required headers:
    - `x-pd-environment: development`
    - `x-pd-external-user-id: {your_external_user_id}`
@@ -112,7 +112,7 @@ npm i @pipedream/sdk
 To invoke workflows, you'll need:
 
 1. The OAuth client ID and secret from your OAuth client in **step 2 above** (if configured)
-2. Your [Project ID](/projects#finding-your-projects-id)
+2. Your [Project ID](/workflows/projects#finding-your-projects-id)
 3. Your workflow's HTTP endpoint URL
 4. The [external user ID](/connect/api#external-users) of the user you'd like to run the workflow for
 5. The [Connect environment](/connect/environments) tied to the user's account
@@ -268,7 +268,7 @@ The most common way to trigger workflows is via HTTP webhook. We strongly recomm
 To get started, you'll need:
 
 - [OAuth client ID and secret](/workflows/rest-api/auth#creating-an-oauth-client) (optional but recommended)
-- Your [project ID](/projects#finding-your-projects-id)
+- Your [project ID](/workflows/projects#finding-your-projects-id)
 - Your workflow's HTTP endpoint URL
 - The [external user ID](/connect/api#external-users) of your end user
 - The [Connect environment](/connect/environments)

docs-v2/pages/deprecated/migrate-from-v1/index.mdx

@@ -248,7 +248,7 @@ After testing the step, you'll see the Slack app will appear in the **Configurat
 
 You can still return an HTTP response from an HTTP-triggered workflow.
 
-Use [`$.respond`](/docs/workflows/visual-builder/triggers/#http) to send a JSON or string response from the HTTP call that triggered the workflow.
+Use [`$.respond`](/workflows/visual-builder/triggers/#http) to send a JSON or string response from the HTTP call that triggered the workflow.
 
 ```javascript
 export default defineComponent({

docs-v2/pages/glossary.mdx

@@ -130,11 +130,11 @@ A workflow setting that allows you to configure how long Pipedream stores event
 
 ### Delay
 
-[A built-in service](/workflows/control-flow/delay) that lets you pause a workflow for a specified amount of time. You can delay workflows using pre-built actions, or delay in code.
+[A built-in service](/workflows/visual-builder/control-flow/delay) that lets you pause a workflow for a specified amount of time. You can delay workflows using pre-built actions, or delay in code.
 
 ### Destination
 
-[Destinations](/destinations) are built-in services that abstract the delivery and connection logic required to send events to services like Amazon S3, or targets like HTTP and email.
+[Destinations](/workflows/data-management/destinations) are built-in services that abstract the delivery and connection logic required to send events to services like Amazon S3, or targets like HTTP and email.
 
 ### Domain
 
@@ -146,7 +146,7 @@ Synonum for [custom domain](#custom-domain).
 
 ### Deploy key
 
-When you configure [GitHub Sync](#github-sync), you can use a deploy key to authenticate Pipedream with your GitHub repository. [See the docs](/workflows/projects/git#create-a-new-project-and-enable-github-sync) for more details.
+When you configure [GitHub Sync](#github-sync), you can use a deploy key to authenticate Pipedream with your GitHub repository. [See the docs](/workflows/git#create-a-new-project-and-enable-github-sync) for more details.
 
 ## E
 
@@ -183,15 +183,15 @@ Events are emitted by [sources](#event-source) and consumed by workflows. Events
 
 ### Event context
 
-Metadata about a workflow execution, including the timestamp of the event, the event ID, and more. Exposed in [`steps.trigger.context`](/docs/workflows/visual-builder/triggers#stepstriggercontext).
+Metadata about a workflow execution, including the timestamp of the event, the event ID, and more. Exposed in [`steps.trigger.context`](/workflows/visual-builder/triggers#stepstriggercontext).
 
 ### Event data
 
-The content of the event, exposed in [`steps.trigger.event`](/docs/workflows/visual-builder/triggers).
+The content of the event, exposed in [`steps.trigger.event`](/workflows/visual-builder/triggers).
 
 ### Event history
 
-A log of all workflow events and executions, available in the [event inspector](#inspector) or the global [event history UI](/event-history).
+A log of all workflow events and executions, available in the [event inspector](#inspector) or the global [event history UI](/workflows/event-history).
 
 ### Event queue
 
@@ -222,7 +222,7 @@ Depending on the context, **export** can function as a noun or verb:
 
 ### Expression
 
-In programming, expressions are code that resolve to a value. In Pipedream, [you can use expressions within props forms](/workflows/using-props#entering-expressions) to reference prior steps or compute custom values at runtime.
+In programming, expressions are code that resolve to a value. In Pipedream, [you can use expressions within props forms](/workflows/visual-builder/using-props#entering-expressions) to reference prior steps or compute custom values at runtime.
 
 ### External credentials
 
@@ -254,7 +254,7 @@ Press `Ctrl + K` or `Cmd + K` to open the global search bar in the Pipedream UI.
 
 ### GitHub Sync
 
-When enabled on a [project](#project), GitHub Sync syncs the project's workflow code with a GitHub repository. [See the docs](/workflows/projects/git) for more details.
+When enabled on a [project](#project), GitHub Sync syncs the project's workflow code with a GitHub repository. [See the docs](/workflows/git) for more details.
 
 ### Golang runtime
 
@@ -304,7 +304,7 @@ A resource that listens for events emitted by [emitters](#emitter). Listeners ca
 
 ### Logs
 
-Standard output and error logs generated by steps during a workflow execution. Logs are available as a part of the step execution details in the [event inspector](#inspector) or the global [event history UI](/event-history).
+Standard output and error logs generated by steps during a workflow execution. Logs are available as a part of the step execution details in the [event inspector](#inspector) or the global [event history UI](/workflows/event-history).
 
 ## M
 
@@ -332,15 +332,15 @@ A [connected account](#connected-account) that uses OAuth to authenticate with a
 
 ### Premium apps
 
-Pipedream's built-in [integrations](#integrations) that require a paid plan to use. [See the pricing page](https://pipedream.com/pricing) for more details and the [full list of premium apps](/apps#premium-apps).
+Pipedream's built-in [integrations](#integrations) that require a paid plan to use. [See the pricing page](https://pipedream.com/pricing) for more details and the [full list of premium apps](/workflows/integrations/apps#premium-apps).
 
 ### Project
 
 A container for workflows, secrets, and other resources in Pipedream. Projects can be synced with a GitHub repository using [GitHub Sync](#github-sync). [See the docs](/projects) for more details.
 
 ### Project-based access control
 
-You can restrict access to projects to specific individuals or share with the entire workspace. [See the docs](/projects#access-controls) for more details.
+You can restrict access to projects to specific individuals or share with the entire workspace. [See the docs](/workflows/projects#access-controls) for more details.
 
 ### Project changelog
 
@@ -372,7 +372,7 @@ Pipedream's internal code in the [execution environment](#execution-environment)
 
 ### Object explorer
 
-The [builder](#builder) UI that allows you to search objects [exported](#export) from prior steps. [See the docs](/workflows/using-props#use-the-object-explorer) for more details.
+The [builder](#builder) UI that allows you to search objects [exported](#export) from prior steps. [See the docs](/workflows/visual-builder/using-props#use-the-object-explorer) for more details.
 
 ## Q
 
@@ -406,11 +406,11 @@ Synonym for [event source](#event-source).
 
 ### Step export
 
-JSON-serializable data returned from steps, available in future steps of a workflow. [See the docs](/workflows/steps#step-exports) for more details.
+JSON-serializable data returned from steps, available in future steps of a workflow. [See the docs](/workflows#step-exports) for more details.
 
 ### Step notes
 
-[Step notes](/workflows/steps#step-notes) are Markdown notes you can add to a step to document its purpose.
+[Step notes](/workflows#step-notes) are Markdown notes you can add to a step to document its purpose.
 
 ### Subscription
 
@@ -440,7 +440,7 @@ Triggers process data from third-party APIs and [emit](#emit) [events](#event) t
 
 ### Two-factor authentication (2FA)
 
-Two-factor authentication. [Configure 2FA](/user-settings#two-factor-authentication) to add an extra layer of security to your Pipedream account.
+Two-factor authentication. [Configure 2FA](/account/user-settings#two-factor-authentication) to add an extra layer of security to your Pipedream account.
 
 ## U
 
@@ -462,7 +462,7 @@ You create a workspace when you sign up for Pipedream. Workspaces contain projec
 
 ### Workspace admin
 
-A workspace can have multiple [admins](/workspaces#promoting-a-member-to-admin), who can administer the workspace, manage billing, and more.
+A workspace can have multiple [admins](/workflows/workspaces#promoting-a-member-to-adminn), who can administer the workspace, manage billing, and more.
 
 ### Workspace member
 

docs-v2/pages/hidden/scheduling-future-tasks/index.mdx

@@ -13,7 +13,7 @@ To [schedule a new task](#scheduling-a-task), just send an HTTP `POST` request t
 }
 ```
 
-When the timestamp arrives and the task is invoked, the source will emit the payload passed in your original, scheduled request. This allows you to trigger [a Pipedream workflow](/workflows/) at the scheduled time, passing the `message` and `timestamp` to the workflow as an [incoming event](/docs/workflows/visual-builder/triggers/).
+When the timestamp arrives and the task is invoked, the source will emit the payload passed in your original, scheduled request. This allows you to trigger [a Pipedream workflow](/workflows/) at the scheduled time, passing the `message` and `timestamp` to the workflow as an [incoming event](/workflows/visual-builder/triggers/).
 
 You can also listen for these events in your own app / infra, by [subscribing to your source's SSE stream](/api/sse/). Each time a scheduled task is emitted from your Pipedream source, it also emits a message to that SSE stream. Any application (a Docker container, a Rails app, etc.) listening to that SSE stream can react to that message to run whatever code you'd like.
 
@@ -177,4 +177,4 @@ Scheduled tasks are emitted by the event source as events, which you can consume
 - [The Pipedream REST API](/api/rest/)
 - [The Pipedream CLI](/workflows/cli/reference/#installing-the-cli)
 
-[See the docs on consuming events from sources](/sources/#consuming-events-from-sources) for more information.
+[See the docs on consuming events from sources](/workflows/visual-builder/sources#consuming-events-from-sources) for more information.

docs-v2/pages/index.mdx

@@ -50,7 +50,7 @@ Our [community](https://pipedream.com/community) uses Pipedream for a wide varie
 
 ## Source-available
 
-Pipedream maintains a [source-available component registry](https://github.com/pipedreamhq/pipedream/) on GitHub so you can avoid writing boilerplate code for common API integrations. Use components as no code building blocks in workflows, or use them to scaffold code that you can customize. You can also [create a PR to contribute new components](/apps/contributing/#contribution-process) via GitHub.
+Pipedream maintains a [source-available component registry](https://github.com/pipedreamhq/pipedream/) on GitHub so you can avoid writing boilerplate code for common API integrations. Use components as no code building blocks in workflows, or use them to scaffold code that you can customize. You can also [create a PR to contribute new components](/workflows/contributing#contribution-process) via GitHub.
 
 ## Contributing
 

docs-v2/pages/pricing/faq.mdx

@@ -12,7 +12,7 @@ Pipedream charges credits proportional to the memory configuration. If you run y
 
 When you upgrade to a paid tier, Stripe will immediately charge your payment method on file for the platform fee tied to your plan (see [https://pipedream.com/pricing](https://pipedream.com/pricing))
 
-If you accrue any [additional credits](#additional-credits), that usage is reported to Stripe throughout the [billing period](/pricing/#billing-period). That overage, as well as the next platform fee, is charged at the start of the _next_ billing period.
+If you accrue any [additional credits](/pricing#additional-credits), that usage is reported to Stripe throughout the [billing period](/pricing/#billing-period). That overage, as well as the next platform fee, is charged at the start of the _next_ billing period.
 
 ## Do any plans support payment by invoice, instead of credit / debit card?