You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs-v2/pages/connect/api-proxy.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ import Callout from '@/components/Callout'
5
5
6
6
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:
7
7
8
-
1. You need code-level control and you want to use [Pipedream's OAuth](/connect/oauth-clients#using-pipedream-oauth) instead of [your own OAuth client](/connect/oauth-clients#using-your-own-oauth-client)
8
+
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-your-own-oauth-client)
9
9
2. There isn't a [pre-built tool](/connect/components) (action) for the app, or you need to modify the request
10
10
3. You want to avoid storing end user credentials in your app
@@ -408,7 +408,7 @@ You can find the app's ID in the response from the [List apps](/rest-api#list-ap
408
408
409
409
`oauth_app_id`**string** (_optional_)
410
410
411
-
The ID of the [OAuth app](/connect/quickstart#create-a-pipedream-oauth-client) you'd like to retrieve accounts for.
411
+
The ID of the [OAuth app](/connect/managed-auth/quickstart#create-a-pipedream-oauth-client) you'd like to retrieve accounts for.
412
412
413
413
---
414
414
@@ -427,7 +427,7 @@ Never return user credentials to the client
427
427
</Callout>
428
428
429
429
<Callouttype="info">
430
-
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).
430
+
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).
431
431
</Callout>
432
432
433
433
##### Examples
@@ -680,7 +680,7 @@ Never return user credentials to the client
680
680
</Callout>
681
681
682
682
<Callouttype="info">
683
-
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).
683
+
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).
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)
930
+
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)
Copy file name to clipboardExpand all lines: docs-v2/pages/connect/index.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,14 +10,14 @@ import VideoPlayer from "@/components/VideoPlayer";
10
10
## Use managed auth
11
11
12
12
- Handle authorization or accept API keys on behalf of your users, for any of Pipedream's [{process.env.PUBLIC_APPS}+ APIs](https://pipedream.com/apps)
13
-
- Use the [Client SDK](https://github.com/PipedreamHQ/pipedream/tree/master/packages/sdk) or [Connect Link](/connect/quickstart#or-use-connect-link) to accept auth in minutes
13
+
- Use the [Client SDK](https://github.com/PipedreamHQ/pipedream/tree/master/packages/sdk) or [Connect Link](/connect/managed-auth/quickstart#or-use-connect-link) to accept auth in minutes
14
14
- Ship new integrations quickly with Pipedream's approved OAuth clients, or use your own
15
15
16
16
17
17
## Act on behalf of your users
18
18
19
19
- Retrieve OAuth access tokens and API keys for your end users with Pipedream's [REST API](/connect/api)
20
-
- Add 10k pre-built tools and triggers from {process.env.PUBLIC_APPS}+ APIs to your AI agent or embed them directly in your SaaS app
20
+
- Add 10,000+ pre-built tools and triggers from {process.env.PUBLIC_APPS}+ APIs to your AI agent or embed them directly in your SaaS app
21
21
- Develop and deploy complex multi-step [workflows](/connect/workflows) in our [visual workflow builder](/workflows)
22
22
- Use the Connect proxy to make custom API requests
Copy file name to clipboardExpand all lines: docs-v2/pages/connect/managed-auth/oauth-clients.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,8 +29,8 @@ For any OAuth app that supports it, **you can always use your own client.** Your
29
29
## Using a custom OAuth client
30
30
31
31
1. Follow the steps [here](/connected-accounts/oauth-clients#configuring-custom-oauth-clients) to create an OAuth client in Pipedream.
32
-
2. When connecting an account either via the [frontend SDK](/connect/quickstart#use-the-pipedream-sdk-in-your-frontend), make sure to include the `oauthAppId` in `pd.connectAccount()`.
33
-
3. If using [Connect Link](/connect/quickstart#or-use-connect-link), make sure to include the `oauthAppId` in the URL.
32
+
2. When connecting an account either via the [frontend SDK](/managed-auth/connect/quickstart#use-the-pipedream-sdk-in-your-frontend), make sure to include the `oauthAppId` in `pd.connectAccount()`.
33
+
3. If using [Connect Link](/connect/managed-auth/quickstart#or-use-connect-link), make sure to include the `oauthAppId` in the URL.
Copy file name to clipboardExpand all lines: docs-v2/pages/connect/managed-auth/webhooks.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Connect Webhooks
2
2
3
-
When you [generate a Connect token](/connect/quickstart/#generate-a-short-lived-token), you can pass a `webhook_uri` parameter. Pipedream will send a POST request to this URL when the user completes the connection flow, or if an error occurs at any point. [See the API docs](/connect/api#create-a-new-token) for details.
3
+
When you [generate a Connect token](/connect/managed-auth/quickstart/#generate-a-short-lived-token), you can pass a `webhook_uri` parameter. Pipedream will send a POST request to this URL when the user completes the connection flow, or if an error occurs at any point. [See the API docs](/connect/api#create-a-new-token) for details.
Copy file name to clipboardExpand all lines: docs-v2/pages/connect/workflows.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,7 @@ When you trigger the workflow, Pipedream will look up the corresponding account
71
71
72
72
To run an end-to-end test as an end user, you need to have users and connected accounts in your project. If you already have a **development** account linked, you can skip this step.
73
73
74
-
If you don't, the fastest way to do this is [on the **Users** tab](/connect#users) in your Pipedream project:
74
+
If you don't, the fastest way to do this is [on the **Users** tab](/connect/managed-auth/users) in your Pipedream project:
75
75
- You'll see there's a button to **Connect account**
76
76
- Go through the flow and make sure to create the account in **development** mode
77
77
- Note the **external user ID** of the account you just connected, you'll need it in the next step
@@ -242,7 +242,7 @@ We plan to improve this interface in the future, and potentially allow developer
242
242
To test a step using the connected account of one of your end users in the builder, you'll need a few things to be configured so that your workflow knows which account to use.
243
243
244
244
**Make sure you have an external user with the relevant connected account(s) saved to your project:**
245
-
- Go to the **[Users tab](/connect#users)** in the **Connect** section of your project to confirm
245
+
- Go to the **[Users tab](/connect/managed-auth/users)** in the **Connect** section of your project to confirm
246
246
- If not, either connect one from your application or [directly in the UI](#connect-a-test-account)
247
247
248
248
**Pass the environment and external user ID:**
@@ -393,11 +393,11 @@ Pipedream Connect Error: Required account for hubspot not found for external use
393
393
394
394
#### No matching external user ID
395
395
- There was an external user ID passed, but it didn't match any users in the project.
396
-
- Double-check that the external user ID that you passed when invoking the workflow matches one either [in the UI](/connect#users) or [via the API](/connect/api#accounts).
396
+
- Double-check that the external user ID that you passed when invoking the workflow matches one either [in the UI](/connect/managed-auth/users) or [via the API](/connect/api#accounts).
397
397
398
398
#### Required account not found for external user ID
399
399
- The external user ID was passed when invoking the workflow, but the user doesn't have a connected account forone or more of the apps that are configured to use itin this workflow execution.
400
-
- You can check which connected accounts are available for that user [in the UI](/connect#users) or [via the API](/connect/api#accounts).
400
+
- You can check which connected accounts are available for that user [in the UI](/connect/managed-auth/users) or [via the API](/connect/api#accounts).
401
401
402
402
#### Running workflows for your users in production requires a higher tier plan
403
403
- Anyone is able to run workflows foryour end usersin`development`. The Business plan is required to run on behalf of `production` users.
0 commit comments