PipedreamHQ · dannyroosevelt · Feb 6, 2025 · Jan 31, 2025 · Jan 31, 2025 · Feb 4, 2025
diff --git a/docs-v2/next.config.mjs b/docs-v2/next.config.mjs
@@ -50,7 +50,7 @@ export default withNextra({
     TMP_SIZE_LIMIT: "2GB",
     DELAY_MIN_MAX_TIME:
       "You can pause your workflow for as little as one millisecond, or as long as one year",
-    PUBLIC_APPS: "2,400",
+    PUBLIC_APPS: "2,500",
     REGISTRY_ACTIONS: "5,300",
     REGISTRY_SOURCES: "2,500",
     REGISTRY_COMPONENTS: "8,000",

diff --git a/docs-v2/pages/_meta.tsx b/docs-v2/pages/_meta.tsx
@@ -5,7 +5,7 @@ export default {
   "projects": "Projects",
   "workflows": "Workflows",
   "connect": {
-    title: "Pipedream Connect",
+    title: "Connect",
   },
   "code": "Code",
   "data-stores": "Data Stores",

diff --git a/docs-v2/pages/connect/_meta.tsx b/docs-v2/pages/connect/_meta.tsx
@@ -5,35 +5,23 @@ export default {
   "use-cases": {
     "title": "Use cases",
   },
-  "quickstart": {
+  "managed-auth": {
     "title": "Managed auth",
   },
-  "workflows": {
-    "title": "Running workflows",
-  },
   "components": {
-    "title": "Embedding components",
+    "title": "Pre-built tools",
   },
-  "api": {
-    "title": "API & SDK reference",
+  "api-proxy": {
+    "title": "API proxy",
   },
-  "tokens": {
-    "title": "Connect tokens",
+  "workflows": {
+    "title": "Workflows",
   },
   "environments": {
     "title": "Environments",
   },
-  "oauth-clients": {
-    "title": "OAuth clients",
-  },
-  "webhooks": {
-    "title": "Webhooks",
-  },
-  "connect-link": {
-    "title": "Connect Link",
-  },
-  "customize-your-app": {
-    "title": "Customize your app",
+  "api": {
+    "title": "API & SDK reference",
   },
   "troubleshooting": {
     "title": "Troubleshooting",

diff --git a/docs-v2/pages/connect/api-proxy.mdx b/docs-v2/pages/connect/api-proxy.mdx
@@ -0,0 +1,123 @@
+import { Tabs } from 'nextra/components'
+import Callout from '@/components/Callout'
+
+# Connect API Proxy
+
+Pipedream Connect provides a proxy API that you can use to send authenticated requests to any integrated API on behalf of your users, which is useful in a few scenarios:
+
+1. You need code-level control and you want to use [Pipedream's OAuth](/connect/managed-auth/oauth-clients#using-pipedream-oauth) instead of [your own OAuth client](/connect/managed-auth/oauth-clients#using-a-custom-oauth-client)
+2. There isn't a [pre-built tool](/connect/components) (action) for the app, or you need to modify the request
+3. You want to avoid storing end user credentials in your app
+
+## Overview
+
+The Connect proxy enables you to interface with any integrated API and make authenticated requests on behalf of your users, without dealing with OAuth or storing end user credentials.
+
+1. You send a request to the proxy and identify the end user you want to act on behalf of
+2. The proxy sends the request to the downstream API and dynamically inserts your end user's auth credentials
+3. The proxy returns the response from the downstream API back to you
+
+![Connect API proxy visualization](https://res.cloudinary.com/pipedreamin/image/upload/v1738822030/pd-connect-proxy-viz_k5iksb.png)
+
+<Callout type="info">
+Before getting started with the Connect proxy, make sure you've already gone through the [managed auth quickstart](/connect/managed-auth/quickstart) for Pipedream Connect.
+</Callout>
+
+## 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).
+
+- A [Pipedream OAuth client](/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`)
+
+Refer to the full Connect API [here](/connect/api).
+
+### Using the Pipedream SDK (preferred)
+
+You can use the [Pipedream SDK](https://www.npmjs.com/package/@pipedream/sdk) to send a fetch-style request:
+
+```javascript
+import { createBackendClient } from "@pipedream/sdk/server";
+
+const pd = createBackendClient({
+  environment: {development | production},
+  projectId: {your_projectId},
+  credentials: {
+    clientId: {your_oauth_client_id},
+    clientSecret: {your_oauth_client_secret}
+  },
+});
+
+
+const resp = await pd.makeProxyRequest(
+  {
+    searchParams: {
+      account_id: "{account_id}", // The account ID for your end user (ex, apn_1234567)
+      external_user_id: "{external_user_id}", // The external user ID for your end user
+    }
+  },
+  {
+    url: "https://slack.com/api/chat.postMessage", // Include any query params you need; no need to Base64 encode the URL if using the SDK
+    options: {
+      method: "POST",
+      headers: {
+        hello: "world!" // These get sent to the downstream API
+      },
+      body: {
+        text: "hello, world",
+        channel: "C03NA8B4VA9"
+      },
+    },
+  }
+)
+
+// Parse and return the data you need
+console.log(resp);
+```
+
+### Using the REST API
+
+You can also send a request to the Connect REST API with the below config:
+
+**URL**
+
+- The URL of the API you want to call (ex, `https://slack.com/api/chat.postMessage`)
+- When using the REST API, this should be an URL-safe Base64 encoded string (ex, `aHR0cHM6Ly9zbGFjay5jb20vYXBpL2NoYXQucG9zdE1lc3NhZ2U`)
+
+**HTTP method**
+
+- Use the HTTP method required by the downstream API
+
+**Body**
+
+- Optionally include a body to send to the downstream API
+
+**Headers**
+
+- If using the REST API, include the `Authorization` header with your Pipedream OAuth access token (`Bearer {access_token}`)
+- Headers that contain the prefix `x-pd-proxy` will get forwarded to the downstream API
+
+```bash
+# First, obtain an OAuth access token
+curl -X POST https://api.pipedream.com/v1/oauth/token \
+  -H "Content-Type: application/json" \
+  -d '{
+    "grant_type": "client_credentials",
+    "client_id": "{your_oauth_client_id}",
+    "client_secret": "{your_oauth_client_secret}"
+  }'
+
+# The response will include an access_token. Use it in the Authorization header below.
+
+curl -X POST "https://api.pipedream.com/v1/connect/{your_project_id}/proxy/{url_safe_base64_encoded_url}?external_user_id={external_user_id}&account_id={apn_xxxxxxx}" \
+  -H "Authorization: Bearer {access_token}" \
+  -H "x-pd-environment: {development | production}" \
+  -d '{
+    "text": "hello, world",
+    "channel": "C03NA8B4VA9"
+  }'
+
+# Parse and return the data you need
+```
diff --git a/docs-v2/pages/connect/api.mdx b/docs-v2/pages/connect/api.mdx
@@ -70,7 +70,7 @@ You'll primarily use the browser SDK to let your users securely connect apps fro
 1. [Create a short-lived token on your server](#create-a-new-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/quickstart):
+Here's a Next.js example [from our quickstart](/connect/managed-auth/quickstart):
 
 ```typescript
 import { createFrontendClient } from "@pipedream/sdk/browser"
@@ -408,7 +408,7 @@ You can find the app's ID in the response from the [List apps](/rest-api#list-ap
 
 `oauth_app_id` **string** (_optional_)
 
-The ID of the [OAuth app](/connect/quickstart#create-a-pipedream-oauth-client) you'd like to retrieve accounts for.
+The ID of the [OAuth app](/connect/managed-auth/quickstart#create-a-pipedream-oauth-client) you'd like to retrieve accounts for.
 
 ---
 
@@ -427,7 +427,7 @@ Never return user credentials to the client
 </Callout>
 
 <Callout type="info">
-To retrieve the credentials for any account in `production` for OAuth apps (Slack, Google Sheets, etc), the connected account must be using [your own OAuth client](/connect/oauth-clients#using-a-custom-oauth-client). You can only retrieve end user credentials for accounts that are using Pipedream's OAuth clients in `development`. [Learn more here](/connect/oauth-clients#using-pipedream-oauth).
+To retrieve the credentials for any account in `production` for OAuth apps (Slack, Google Sheets, etc), the connected account must be using [your own OAuth client](/connect/managed-auth/oauth-clients#using-a-custom-oauth-client). You can only retrieve end user credentials for accounts that are using Pipedream's OAuth clients in `development`. [Learn more here](/connect/managed-auth/oauth-clients#using-pipedream-oauth).
 </Callout>
 
 ##### Examples
@@ -680,7 +680,7 @@ Never return user credentials to the client
 </Callout>
 
 <Callout type="info">
-To retrieve the credentials for any account in `production` for OAuth apps (Slack, Google Sheets, etc), the connected account must be using [your own OAuth client](/connect/oauth-clients#using-a-custom-oauth-client). You can only retrieve end user credentials for accounts that are using Pipedream's OAuth clients in `development`. [Learn more here](/connect/oauth-clients#using-pipedream-oauth).
+To retrieve the credentials for any account in `production` for OAuth apps (Slack, Google Sheets, etc), the connected account must be using [your own OAuth client](/connect/managed-auth/oauth-clients#using-a-custom-oauth-client). You can only retrieve end user credentials for accounts that are using Pipedream's OAuth clients in `development`. [Learn more here](/connect/managed-auth/oauth-clients#using-pipedream-oauth).
 </Callout>
 
 ##### Examples
@@ -927,7 +927,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#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)
+The app ID for which you want to delete all connected accounts. `app_id` can be `oauth_app_id` for [OAuth apps](/connect/managed-auth/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
 

diff --git a/docs-v2/pages/connect/components.mdx b/docs-v2/pages/connect/components.mdx
@@ -1,22 +1,33 @@
 import { Steps, Tabs } from 'nextra/components'
 import Callout from '@/components/Callout'
 
-# Embedding components in your application
+# Pre-built tools for your app or agent
 
-Pipedream Connect provides APIs to embed [pre-built components](/components) directly in your application
-or AI agent, unlocking access to {process.env.REGISTRY_COMPONENTS}+ pre-built API operations. Enable [your end users](/connect/api#external-users) to
+Pipedream Connect provides APIs to embed pre-built tools ([triggers and actions](/components)) directly in your application
+or AI agent, enabling access to 10,000+ built-in API operations. Enable [your end users](/connect/api#external-users) to
 configure, deploy, and invoke Pipedream triggers and actions for more than {process.env.PUBLIC_APPS} APIs.
 
-## What are components?
+## What are triggers and actions?
 
-In Pipedream, [components](/components) are self-contained executable units of code. Your end users configure the inputs and the components produce a
+In Pipedream, we call triggers and actions [components](/components), which are self-contained executable units of code. Your end users configure the inputs and these components produce a
 result that's exported as output. These components are developed and maintained by Pipedream
 and our community and their source code is available in our [public Github repo](https://github.com/PipedreamHQ/pipedream/tree/master/components).
 
+## Implementation
+
+### Use Pipedream's frontend React SDK
+- Pipedream provides an SDK that you can use to automatically render React UI components in your application to enable your users to configure and run the triggers and actions
+- Style the UI components however you want to match the design of your app, and you can also fork the SDK
+- Refer to the [SDK](https://github.com/PipedreamHQ/pipedream/blob/master/packages/connect-react/README.md) to get started
+
 <Callout type="info">
-Running components for your end users via Pipedream Connect is in **beta**, and we're looking for feedback. Please [let us know](https://pipedream.com/support) how you're using it, what's not working, and what else you'd like to see.
+Check out the [public demo app](https://pdrm.co/connect) to see the API and SDK in action. You can also [run it locally and explore the code](https://github.com/PipedreamHQ/pipedream-connect-examples/tree/master/connect-react-demo).
 </Callout>
 
+### Use your own frontend
+- See below to get started with the REST API
+- Refer to the [full API reference](/connect/api#components) for supported SDK methods as well
+
 ## Getting started
 
 <Callout type="info">

diff --git a/docs-v2/pages/connect/environments.mdx b/docs-v2/pages/connect/environments.mdx
@@ -6,7 +6,7 @@ import Image from 'next/image'
 Pipedream Connect projects support two environments: `development` and `production`. Connected accounts and credentials stored in `development` remain separate from `production`.
 
 <Callout type="info">
-Pipedream customers on any plan can use all of the Connect features in `development` mode. To use Connect in `production`, click **Contact Sales** [here](https://pipedream.com/pricing?plan=Enterprise) to get in touch with our team.
+You can use all of the Connect features in `development` mode **on any plan**. **[Get in touch with our Sales team](https://pipedream.com/pricing?plan=Enterprise)** when you're ready to ship to production.
 </Callout>