Danny/fixing docs apps redirect (#16478)

* Update pnpm-lock.yaml

* Fixing bad /apps redirect, adding catch-all redirect

* Update pnpm-lock.yaml

* Escaping unsafe characters and pnpm lock

* Update 404.tsx

* Merge branch 'danny/fixing-docs-apps-redirect' of github.com:PipedreamHQ/pipedream into danny/fixing-docs-apps-redirect

* Update pnpm-lock.yaml

* Delete apps.mdx

* Updating header anchor tags

* Update users.mdx

* Modifying 404 handling

* Add redirects for /apps/apps/ and /integrations/ paths

* Linting

* Removing 404 and middleware changes

* Capitalize section headers in API docs

* Update API reference links to match capitalized section headers

* Update api.mdx

* Update pnpm-lock.yaml

Author: dannyroosevelt

.gitignore

@@ -18,3 +18,5 @@ docs/.vuepress/dist
 components/**/package-lock.json
 /packages/evals/
 /packages/sdk/examples/.next/
+
+**/.claude/settings.local.json

docs-v2/next.config.mjs

@@ -34,6 +34,11 @@ export default withNextra({
   },
   async redirects() {
     return [
+      {
+        source: "/apps/apps/",
+        destination: "/apps/",
+        permanent: true,
+      },
       {
         source: "/v3/",
         destination: "/",
@@ -69,11 +74,6 @@ export default withNextra({
         destination: "https://pipedream.com/apps/",
         permanent: true,
       },
-      {
-        source: "/apps/:path*/",
-        destination: "https://pipedream.com/apps/:path*/",
-        permanent: true,
-      },
       {
         source: "/support/",
         destination: "https://pipedream.com/support/",
@@ -481,6 +481,11 @@ export default withNextra({
         destination: "/integrations/oauth-clients/",
         permanent: true,
       },
+      {
+        source: "/integrations/",
+        destination: "/apps/",
+        permanent: true,
+      },
       {
         source: "/integrations/:path*/",
         destination: "/apps/:path*/",
@@ -561,6 +566,10 @@ export default withNextra({
         source: "/api-demo-connect/accounts/:id/",
         destination: "/api/demo-connect/accounts/:id",
       },
+      {
+        source: "/workflows/errors/",
+        destination: "/workflows/building-workflows/errors/",
+      },
     ];
   },
   env: {

docs-v2/pages/apps/apps.mdx

@@ -67,7 +67,7 @@ const pd = createBackendClient({
 
 You'll primarily use the browser SDK to let your users securely connect apps from your frontend. Here, you
 
-1. [Create a short-lived token on your server](#create-a-new-token)
+1. [Create a short-lived token on your server](#create-token)
 2. Initiate auth with that token to securely connect an account for a specific user
 
 Here's a Next.js example [from our quickstart](/connect/managed-auth/quickstart/):
@@ -240,7 +240,7 @@ Your app will initiate the account connection flow for your end users in your fr
 
 See [the Connect tokens docs](/connect/tokens/) for more information.
 
-#### Create a new token
+#### Create token
 
 ```
 POST /{project_id}/tokens
@@ -383,9 +383,9 @@ curl -X POST https://api.pipedream.com/v1/connect/{project_id}/tokens \
 
 ### Accounts
 
-#### List all accounts
+#### List All Accounts
 
-List all connected accounts for all end users within a project.
+List all connected accounts for all externalusers within a project.
 
 ```
 GET /{project_id}/accounts/
@@ -650,7 +650,7 @@ curl -X GET \
 }
 ```
 
-#### Retrieve account details by ID
+#### Retrieve Account Details by ID
 
 Retrieve the account details for a specific account based on the account ID
 
@@ -823,9 +823,9 @@ curl -X GET \
 }
 ```
 
-#### Delete connected account
+#### Delete Connected Account
 
-Delete a specific connected account for an end user, and any deployed triggers.
+Delete a specific connected account for an external user, and any deployed triggers.
 
 ```
 DELETE /{project_id}/accounts/{account_id}
@@ -910,7 +910,7 @@ curl -X DELETE "https://api.pipedream.com/v1/connect/{project_id}/accounts/{acco
 
 Pipedream returns a `204 No Content` response on successful account deletion
 
-#### Delete all connected accounts for an app
+#### Delete All Connected Accounts for an App
 
 Delete all connected accounts for a specific app
 
@@ -999,9 +999,9 @@ curl -X DELETE "https://api.pipedream.com/v1/connect/{project_id}/accounts/{acco
 
 Pipedream returns a `204 No Content` response on successful account deletion
 
-#### Delete an end user
+#### Delete External User
 
-Delete an end user, all their connected accounts, and any deployed triggers.
+Delete an external user, all their connected accounts, and any deployed triggers.
 
 ```
 DELETE /{project_id}/users/{external_user_id}
@@ -1091,7 +1091,7 @@ Pipedream returns a `204 No Content` response on successful account deletion
 
 ### Components
 
-#### List components
+#### List Components
 
 List all the components in the Pipedream registry.
 
@@ -1239,7 +1239,7 @@ curl -X GET "https://api.pipedream.com/v1/connect/{your_project_id}/components?a
 ```
 
 
-#### Retrieve a component
+#### Retrieve Component
 
 Retrieve a specific component from the Pipedream registry.
 
@@ -1378,7 +1378,7 @@ curl -X GET "https://api.pipedream.com/v1/connect/{your_project_id}/components/g
 
 
 
-#### Configure a component
+#### Configure Component
 
 Configure the a component's prop, based on the current component's
 configuration. This endpoint will use the component's configuration to retrieve
@@ -1592,7 +1592,7 @@ curl -X POST "https://api.pipedream.com/v1/connect/{your_project_id}/components/
 }
 ```
 
-#### Reload a component's props (i.e. configure dynamic props)
+#### Reload Component Props
 
 Reload the component's props after configuring a dynamic prop, based on the
 current component's configuration. This endpoint will use the component's
@@ -1820,7 +1820,7 @@ curl -X POST "https://api.pipedream.com/v1/connect/{your_project_id}/components/
 }
 ```
 
-#### Invoke an action
+#### Invoke Action
 
 Invoke an action component for a Pipedream Connect user in a project.
 
@@ -2009,7 +2009,7 @@ curl -X POST "https://api.pipedream.com/v1/connect/{your_project_id}/actions/run
 }
 ```
 
-#### Deploy a trigger
+#### Deploy Trigger
 
 <Callout type="info">
 See [here](/connect/components/#deploying-triggers) for more info on supported trigger types with example payloads
@@ -2242,7 +2242,7 @@ curl -X POST "https://api.pipedream.com/v1/connect/{your_project_id}/triggers/de
 }
 ```
 
-#### List deployed triggers
+#### List Deployed Triggers
 
 List all of the deployed triggers for a given user.
 
@@ -2503,7 +2503,7 @@ curl -X GET \
 }
 ```
 
-#### Retrieve a deployed trigger
+#### Retrieve Deployed Trigger
 
 Retrieve a single deployed trigger for a given user.
 
@@ -2688,7 +2688,7 @@ curl -X GET \
 }
 ```
 
-#### Delete a deployed trigger
+#### Delete Deployed Trigger
 
 Delete deployed trigger for a given user.
 
@@ -2798,7 +2798,7 @@ curl -X DELETE \
 Pipedream returns a `204 No Content` response on successful deletion
 
 
-#### Retrieve the events emitted by a deployed trigger
+#### Retrieve Events Emitted by Deployed Trigger
 
 Retrieve a list of the last events that a deployed trigger emitted.
 
@@ -2995,7 +2995,7 @@ curl -X GET \
 }
 ```
 
-#### Retrieve the webhooks listening to a deployed trigger
+#### Retrieve Webhooks Listening to Deployed Trigger
 
 Retrieve the list of webhook URLs listening to a deployed trigger.
 
@@ -3116,7 +3116,7 @@ curl -X GET \
 }
 ```
 
-#### Update the webhooks listening to a deployed trigger
+#### Update Webhooks Listening to Deployed Trigger
 
 Update the list of webhook URLs that will listen to a deployed trigger.
 
@@ -3255,7 +3255,7 @@ curl -X PUT \
 }
 ```
 
-#### Retrieve the workflows listening to a deployed trigger
+#### Retrieve Workflows Listening to Deployed Trigger
 
 Retrieve the list of workflow IDs listening to a deployed trigger.
 
@@ -3377,7 +3377,7 @@ curl -X GET \
 }
 ```
 
-#### Update the workflows listening to a deployed trigger
+#### Update Workflows Listening to Deployed Trigger
 
 Update the list of workflows that will listen to a deployed trigger.
 

docs-v2/pages/connect/api.mdx

@@ -821,7 +821,7 @@ These are 2 categories of triggers you can deploy on behalf of your end users:
 - [Native triggers](#native-triggers)
 
 <Callout type="info">
-Refer to the [full Connect API reference](/connect/api/#deploy-a-trigger) to list, retrieve, delete, and manage triggers for your user.
+Refer to the [full Connect API reference](/connect/api/#deploy-trigger) to list, retrieve, delete, and manage triggers for your user.
 </Callout>
 
 ### App-based event sources
@@ -833,7 +833,7 @@ Refer to the [full Connect API reference](/connect/api/#deploy-a-trigger) to lis
 - Many event sources attempt to retrieve a small set of historical events on deploy to provide visibility into the event shape for end users and developers
 - Exposing real test events make it easier to consume the event in downstream systems without requiring users to trigger real events ([more info](/components/contributing/guidelines/#surfacing-test-events))
 - However, this results in emitting those events to the listening webhook immediately, which may not always be ideal, depending on your use case
-- If you'd like to avoid emitting historical events, you can deploy a trigger without defining a `webhook_url`, then [update the listening webhooks for the deployed trigger](/connect/api/#update-the-webhooks-listening-to-a-deployed-trigger) after roughly a minute
+- If you'd like to avoid emitting historical events, you can deploy a trigger without defining a `webhook_url`, then [update the listening webhooks for the deployed trigger](/connect/api/#update-webhooks-listening-to-deployed-trigger) after roughly a minute
 
 
 ### Native triggers

docs-v2/pages/connect/components.mdx

@@ -27,7 +27,7 @@ The `development` environment is not intended for production use with your custo
 
 ## How to specify the environment
 
-You specify the environment when [creating a new Connect token](/connect/api/#create-a-new-token) with the Pipedream SDK or API. When users successfully connect their account, Pipedream saves the account credentials (API key, access token, etc.) for that `external_user_id` in the specified environment.
+You specify the environment when [creating a new Connect token](/connect/api/#create-token) with the Pipedream SDK or API. When users successfully connect their account, Pipedream saves the account credentials (API key, access token, etc.) for that `external_user_id` in the specified environment.
 
 Always set the environment when you create the SDK client:
 

docs-v2/pages/connect/environments.mdx

@@ -27,6 +27,6 @@ https://pipedream.com/_static/connect.html?token={token}&connectLink=true&app={a
 
 ## Success and error redirect URLs
 
-To automatically redirect users somewhere after they complete the connection flow (or if an error occurs), define the `success_redirect_uri` and `error_redirect_uri` parameters during token creation. [See the API docs](/connect/api/#create-a-new-token) for details.
+To automatically redirect users somewhere after they complete the connection flow (or if an error occurs), define the `success_redirect_uri` and `error_redirect_uri` parameters during token creation. [See the API docs](/connect/api/#create-token) for details.
 
 In the absence of these URLs, Pipedream will redirect the user to a Pipedream-hosted success or error page at the end of the connection flow.

docs-v2/pages/connect/managed-auth/connect-link.mdx

@@ -78,7 +78,7 @@ In the code below you can see how we generate a Connect token for an example use
 Once you have a token, return it to your frontend to start the account connection flow for the user, or redirect them to a Pipedream-hosted URL with [Connect Link](#or-use-connect-link).
 
 <Callout type="info">
-Refer to the API docs for [full set of parameters you can pass](/connect/api/#create-a-new-token) in the `ConnectTokenCreate` call.
+Refer to the API docs for [full set of parameters you can pass](/connect/api/#create-token) in the `ConnectTokenCreate` call.
 </Callout>
 
 ### Connect your user's account
@@ -121,7 +121,7 @@ After generating a token in the [step above](#generate-a-short-lived-token), you
 <Callout type="info">
 Make sure to add the `app` parameter to the end of the URL to specify the app.
 
-Check out the [full API docs](/connect/api/#create-a-new-token) for all parameters you can pass when creating tokens, including setting redirect URLs for success or error cases.
+Check out the [full API docs](/connect/api/#create-token) for all parameters you can pass when creating tokens, including setting redirect URLs for success or error cases.
 </Callout>
 
 ### Make authenticated requests