fix some broken links

Author: andrewjschuang

docs-v2/README.md

@@ -22,7 +22,7 @@ We're moving from VuePress to Nextra. Here's what's the same and what's differen
 - New docs are here, in the `docs-v2/` directory.
 - All docs are still Markdown. Now MDX files instead of just Markdown, so extensions have been renamed to `.mdx`.
 - Keep images in `public/images/foo.png`, reference with `![alt text](/images/foo.png)`
-- Leaf nodes in VuePress were at files like `/docs/workspaces/sso/google/README.md`. Nextra allows leaf nodes to be non-index files like `/docs/workspaces/sso/google.mdx`, so there's no need for the final directory, which simplifies things.
+- Leaf nodes in VuePress were at files like `/docs/workflows/workspaces/sso/google/README.md`. Nextra allows leaf nodes to be non-index files like `/docs/workflows/workspaces/sso/google.mdx`, so there's no need for the final directory, which simplifies things.
 - VuePress used Vue, Nextra uses React. All of the custom components used in MDX files are either [built-in Nextra components](https://nextra.site/docs/guide/built-ins) or Pipedream-specific components in `components/`, ported from Vue.
 - Learn the [built-in Nextra components](https://nextra.site/docs/guide/built-ins). All the `::: tip`, `::: warning`, or other special VuePress components have an equivalent Nextra component.
 
@@ -50,8 +50,8 @@ pages
   workspaces/
     index.mdx  # /docs/workspaces
     sso/
-      index.mdx  # /docs/workspaces/sso
-      google.mdx  # /docs/workspaces/sso/google
+      index.mdx  # /docs/workflows/workspaces/sso
+      google.mdx  # /docs/workflows/workspaces/sso/google
 ```
 
 The `_meta.tsx` files in each directory defines a mapping between the labels in the sidebar and the files in that directory. If you want to add an item to the sidebar, you'll probably want to edit the `_meta.tsx` file. [See the Nextra docs](https://nextra.site/docs/docs-theme/page-configuration) for more info.

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

@@ -2,7 +2,7 @@ import Callout from '@/components/Callout'
 
 # Billing Settings
 
-You'll find information on your usage data (for specific [Pipedream limits](/limits/)) in your [Billing Settings](https://pipedream.com/settings/billing). You can also upgrade to [paid plans](https://pipedream.com/pricing) from this page.
+You'll find information on your usage data (for specific [Pipedream limits](/workflows/limits/)) in your [Billing Settings](https://pipedream.com/settings/billing). You can also upgrade to [paid plans](https://pipedream.com/pricing) from this page.
 
 ## Subscription
 
@@ -28,7 +28,7 @@ Users on the free tier will see the last 30 days of usage in this chart. Users o
 
 Control the maximum number of compute credits permitted on your account with an _Credit Budget_.
 
-This will restrict your account-wide usage to the specified number of [credits](/pricing/#credits) on a monthly or daily basis. The compute budget does not apply to credits incurred by [dedicated workers](/workflows/settings/#eliminate-cold-starts).
+This will restrict your account-wide usage to the specified number of [credits](/pricing/#credits) on a monthly or daily basis. The compute budget does not apply to credits incurred by [dedicated workers](/workflows/visual-builder/settings/#eliminate-cold-starts).
 
 To enable this feature, _click_ on the toggle and define your maximum number of credits in the period.
 
@@ -40,4 +40,4 @@ In an example scenario, with cap set at 20 credits and long running workflow tha
 
 ## Limits
 
-For users on the [Free tier](/pricing/#free-tier), this section displays your usage towards your [credits quota](/limits/#daily-credits-limit) for the current UTC day.
+For users on the [Free tier](/pricing/#free-tier), this section displays your usage towards your [credits quota](/workflows/limits/#daily-credits-limit) for the current UTC day.

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](/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](/workflows/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.
 
@@ -62,7 +62,7 @@ Only workspace owner and admin members can enable or disable 2FA for an entire w
 
 ## Pipedream API Key
 
-Pipedream provides a [REST API](/api/) for interacting with Pipedream programmatically. You'll find your API key here, which you use to [authorize requests to the API](/rest-api/auth/).
+Pipedream provides a [REST API](/api/) for interacting with Pipedream programmatically. You'll find your API key here, which you use to [authorize requests to the API](/workflows/rest-api/auth/).
 
 You can revoke and regenerate your API key from here at any time.
 

docs-v2/pages/connect/api-proxy.mdx

@@ -25,9 +25,9 @@ Before getting started with the Connect proxy, make sure you've already gone thr
 
 ## Getting started
 
-You can send requests to the Connect proxy using the [Pipedream SDK](/connect/sdk) with a fetch-style interface, or by making a request to the [REST API](/rest-api/connect/proxy).
+You can send requests to the Connect proxy using the [Pipedream SDK](/connect/sdk) with a fetch-style interface, or by making a request to the [REST API](/workflows/rest-api/connect/proxy).
 
-- A [Pipedream OAuth client](/rest-api/auth#oauth) to make authenticated requests to Pipedream's API
+- A [Pipedream OAuth client](/workflows/rest-api/auth#oauth) to make authenticated requests to Pipedream's API
 - Connect [environment](/connect/environments) (ex, `production` or `development`)
 - The [external user ID](/connect/api#external-users) for your end user (ex, `abc-123`)
 - The [account ID](/connect/api#accounts) for your end user's connected account (ex, `apn_1234567`)
@@ -120,4 +120,4 @@ curl -X POST "https://api.pipedream.com/v1/connect/{your_project_id}/proxy/{url_
   }'
 
 # Parse and return the data you need
-```
+```

docs-v2/pages/connect/api.mdx

@@ -41,13 +41,13 @@ or a specific version:
 
 ## Authentication
 
-See the [REST API Authentication docs](/rest-api/auth).
+See the [REST API Authentication docs](/workflows/rest-api/auth).
 
 ### TypeScript SDK (server)
 
 Most of your interactions with the Connect API will happen on the server, to protect API requests and user credentials. You'll use the SDK in [your frontend](#typescript-sdk-browser) to let users connect accounts. Once connected, you'll use the SDK on the server to retrieve credentials, invoke workflows on their behalf, and more.
 
-[Create a Pipedream OAuth client](/rest-api/auth#oauth) and instantiate the SDK with your client ID and secret:
+[Create a Pipedream OAuth client](/workflows/rest-api/auth#oauth) and instantiate the SDK with your client ID and secret:
 
 ```typescript
 import { createBackendClient } from "@pipedream/sdk/server";
@@ -206,7 +206,7 @@ curl -X POST https://api.pipedream.com/v1/connect/rate_limits \
 **Example usage**
 
 ```bash
-# The response will include a rate limit token. 
+# The response will include a rate limit token.
 # Pass it as a header in your downstream requests to the Connect API.
 # Below is an example request that runs the "List Commits" action for the Gitlab app.
 
@@ -1120,7 +1120,7 @@ apps](/rest-api#list-apps) endpoint, and the name slug under the
 `q` **string** (_optional_)
 
 A search query to filter the components by key (see the [component structure
-table](/components/api#component-structure)).
+table](/workflows/contributing/components/api#component-structure)).
 
 ##### Examples
 
@@ -1257,7 +1257,7 @@ Either `triggers`, `actions`, or `components`.
 `component_key` **string**
 
 The key that identifies the component (see the [component structure
-table](/components/api#component-structure)).
+table](/workflows/contributing/components/api#component-structure)).
 
 ##### Examples
 
@@ -1414,7 +1414,7 @@ want to retrieve accounts for.
 `id` **string**
 
 The key that identifies the component (see the [component structure
-table](/components/api#component-structure)).
+table](/workflows/contributing/components/api#component-structure)).
 
 ---
 
@@ -1597,7 +1597,7 @@ Reload the component's props after configuring a dynamic prop, based on the
 current component's configuration. This endpoint will use the component's
 configuration to retrieve a new list of props depending on the value of the
 props that were configured so far. See the [Dynamic
-Props](/connect/components#dynamic-props-optional) section for more information.
+Props](/connect/workflows/contributing/components#dynamic-props-optional) section for more information.
 
 ```text
 GET /{component_type}/props
@@ -1629,7 +1629,7 @@ want to retrieve accounts for.
 `id` **string**
 
 The key that identifies the component (see the [component structure
-table](/components/api#component-structure)).
+table](/workflows/contributing/components/api#component-structure)).
 
 ---
 
@@ -1832,7 +1832,7 @@ POST /actions/run
 `id` **string**
 
 The key that identifies the action component (see the [component structure
-table](/components/api#component-structure)).
+table](/workflows/contributing/components/api#component-structure)).
 
 ---
 
@@ -2021,7 +2021,7 @@ POST /triggers/deploy
 `id` **string**
 
 The key that identifies the action component (see the [component structure
-table](/components/api#component-structure)).
+table](/workflows/contributing/components/api#component-structure)).
 
 ---
 
@@ -3500,4 +3500,3 @@ curl -X PUT \
   ]
 }
 ```
-

docs-v2/pages/connect/components.mdx

@@ -150,7 +150,7 @@ Here's the response:
 To configure and run a component for your end users, you need to understand
 the component's definition. Now that you have the component's key from the previous step,
 you can retrieve its structure from the Pipedream API. See the [component
-structure](/components/api#component-structure) section in our docs for more
+structure](/workflows/contributing/components/api#component-structure) section in our docs for more
 details.
 
 As an example, the following API call will return the structure of the **List
@@ -162,7 +162,7 @@ GET /v1/connect/components/gitlab-list-commits
 
 The response will contain the component's structure, including its user-friendly name,
 version, and most importantly, the configuration options the component accepts
-(also known as [props](/components/api#props) or "properties").
+(also known as [props](/workflows/contributing/components/api#props) or "properties").
 Here's an example of the response for the component in the example above:
 
 ```json
@@ -346,7 +346,7 @@ For example, to retrieve the configuration options for the `refName` prop:
 
 The set of props that a component can accept might not be static, and may change
 depending on the values of prior props. Props that behave this way are called
-[dynamic props](/components/api#dynamic-props), and they need to be configured
+[dynamic props](/workflows/contributing/components/api#dynamic-props), and they need to be configured
 in a different way. Props that are dynamic will have a `reloadProps` attribute
 set to `true` in the component's code.
 
@@ -447,8 +447,8 @@ To illustrate, the response for the request above would look like this:
 ### Execution
 
 Once all the props have been configured, the component can be invoked. Pipedream
-supports two types of components: [actions](/components#actions) and
-[sources](/components#sources) (aka triggers).
+supports two types of components: [actions](/workflows/contributing/components/api#actions) and
+[sources](/workflows/contributing/components/api#sources) (aka triggers).
 
 Actions are components that perform a task by taking an input either during
 [configuration](#configure-the-component) and/or during invocation (usually both), and
@@ -495,7 +495,7 @@ The output of executing the action will be a JSON object containing the
 following fields:
 
 1. `exports`: all the named exports produced by the action, like when calling
-   [`$.export` in a Node.js](/code/nodejs#using-export) component.
+   [`$.export` in a Node.js](/workflows/visual-builder/code/nodejs#using-export) component.
 2. `os`: a list of observations produced by the action (e.g. logs, errors, etc).
 3. `ret`: the return value of the action, if any.
 

docs-v2/pages/connect/index.mdx

@@ -5,7 +5,7 @@ import VideoPlayer from "@/components/VideoPlayer";
 
 # Pipedream Connect
 
-**Connect provides a developer toolkit that lets you add {process.env.PUBLIC_APPS}+ integrations to your app or AI agent.** You can build AI agents, in-app messaging, CRM syncs, [and much more](/connect/use-cases), all in a few minutes. You have full, code-level control over how these integrations work in your app. You handle your product, Pipedream simplifies the integration. 
+**Connect provides a developer toolkit that lets you add {process.env.PUBLIC_APPS}+ integrations to your app or AI agent.** You can build AI agents, in-app messaging, CRM syncs, [and much more](/connect/use-cases), all in a few minutes. You have full, code-level control over how these integrations work in your app. You handle your product, Pipedream simplifies the integration.
 
 ![Connect visualization](https://res.cloudinary.com/pipedreamin/image/upload/v1738731467/pd-connect-viz_cep0uq.png)
 
@@ -64,5 +64,5 @@ All credentials and tokens are sent to Pipedream securely over HTTPS, and encryp
 - **App**: GitHub, Notion, Slack, Google Sheets, and more. The app is the API you want your users to connect to in your product. See the [full list here](https://pipedream.com/apps).
 - **Developer**: This is probably you, the Pipedream customer who's developing an app and wants to use Connect to make API requests on behalf of your end users.
 - **End User**: Your customer or user, whose data you want to access on their behalf. End users are identifed via the `external_user_id` param in the Connect SDK and API.
-- **Connected Account**: The account your end user connects. [Read more about connected accounts](/connected-accounts).
-- **OAuth Client**: This is admittedly a bit of an overloaded term and refers both to [custom OAuth clients](/connect/managed-auth/oauth-clients) you create in Pipedream to use when your end users authorize access to their account, as well as [OAuth clients to authenticate to Pipedream's API](/rest-api/auth#oauth).
+- **Connected Account**: The account your end user connects. [Read more about connected accounts](/workflows/integrations/connected-accounts).
+- **OAuth Client**: This is admittedly a bit of an overloaded term and refers both to [custom OAuth clients](/connect/managed-auth/oauth-clients) you create in Pipedream to use when your end users authorize access to their account, as well as [OAuth clients to authenticate to Pipedream's API](/workflows/rest-api/auth#oauth).

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

@@ -3,7 +3,7 @@ import Callout from '@/components/Callout'
 
 # OAuth Clients
 
-When connecting an account for any OAuth app via Pipedream Connect, we'll default to using Pipedream's official OAuth client, which enables you to quickly get up and running. [Read more about OAuth clients in Pipedream here](/connected-accounts/oauth-clients).
+When connecting an account for any OAuth app via Pipedream Connect, we'll default to using Pipedream's official OAuth client, which enables you to quickly get up and running. [Read more about OAuth clients in Pipedream here](/workflows/integrations/connected-accounts/oauth-clients).
 
 ## Using Pipedream OAuth
 
@@ -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](/connected-accounts/oauth-clients#configuring-custom-oauth-clients) to create an OAuth client in Pipedream.
+1. Follow the steps [here](/workflows/integrations/connected-accounts/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.
 
@@ -38,4 +38,4 @@ For any OAuth app that supports it, **you can always use your own client.** Your
 
 <br />
 
-<Image src="https://res.cloudinary.com/pipedreamin/image/upload/v1730241292/oauth-app-id_umhhqi.png" alt="Copy OAuth App ID" width={650} height={529} />
+<Image src="https://res.cloudinary.com/pipedreamin/image/upload/v1730241292/oauth-app-id_umhhqi.png" alt="Copy OAuth App ID" width={650} height={529} />

docs-v2/pages/connect/migrating-from-project-keys-to-oauth.mdx

@@ -12,7 +12,7 @@ This guide is only relevant if:
 
 ## What changed
 
-- In the `0.x` version of the SDK and the original Connect API, you could authenticate with keys scoped to a specific project. In the `1.x` version of the SDK, you need to authenticate with [OAuth clients](/rest-api/auth#oauth).
+- In the `0.x` version of the SDK and the original Connect API, you could authenticate with keys scoped to a specific project. In the `1.x` version of the SDK, you need to authenticate with [OAuth clients](/workflows/rest-api/auth#oauth).
 - The `createClient` method from both the browser and Node.js SDKs has been replaced with separate methods: `createFrontendClient` and `createBackendClient`, respectively.
 - The `connectTokenCreate` method has been renamed `createConnectToken`
 - New SDK methods: `projectInfo`, `invokeWorkflow`, and more
@@ -23,7 +23,7 @@ This guide is only relevant if:
 
 ### Create an OAuth client
 
-Follow the instructions [here](/rest-api/auth#oauth) to create an OAuth client.
+Follow the instructions [here](/workflows/rest-api/auth#oauth) to create an OAuth client.
 
 ### Update your SDK version
 
@@ -75,7 +75,7 @@ You'll need to make three changes to your backend code:
 <Tabs.Tab>
 ```typescript
 import { createBackendClient, HTTPAuthType } from "@pipedream/sdk/server";
- 
+
 // These secrets should be saved securely and passed to your environment
 const pd = createBackendClient({
   credentials: {
@@ -100,4 +100,4 @@ const pd = createBackendClient({
 </Tabs.Tab>
 </Tabs>
 
-</Steps>
+</Steps>

docs-v2/pages/connect/use-cases.mdx

@@ -30,7 +30,7 @@ Sync data between your app and Salesforce, HubSpot, or any CRM. Pipedream lets y
 
 ### AI products
 
-Talk to any AI API or LLM. Build chat apps or interact in real-time with your users. Or run asynchronous tasks in the background, like image classification, article summarization, or other tasks you want to offload to an AI agent. You can use built-in functions like [`$.flow.suspend`](/code/nodejs/rerun#flowsuspend) to send a message to your team, or directly to the user, to approve specific actions.
+Talk to any AI API or LLM. Build chat apps or interact in real-time with your users. Or run asynchronous tasks in the background, like image classification, article summarization, or other tasks you want to offload to an AI agent. You can use built-in functions like [`$.flow.suspend`](/workflows/visual-builder/code/nodejs/rerun#flowsuspend) to send a message to your team, or directly to the user, to approve specific actions.
 
 ### Spreadsheet integrations