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/environments.mdx
+12-10Lines changed: 12 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,22 +3,16 @@ import Image from 'next/image'
3
3
4
4
# Environments
5
5
6
-
Pipedream Connect projects support two environments: `development` and `production`.
6
+
Pipedream Connect projects support two environments: `development` and `production`. Connected accounts and credentials stored in `development` remain separate from `production`.
7
7
8
-
1. Connected accounts and credentials stored in `development` remain separate from `production`.
9
-
2. In `development`, you can use the official Pipedream OAuth clients, so you can test integrations without creating your own OAuth client, and you can also use features that are typically only available on higher paid tiers, like [running workflows on behalf of your end users](/connect/workflows).
10
-
11
-
<Callouttype="warning">
12
-
When connecting an account in `development`, make sure you're signed in to pipedream.com in the same browser where you're connecting your account. This is only a requirement for the `development` environment. **You should only use the `development` environment with your own accounts when testing and developing, and not with your end users.**
8
+
<Callouttype="info">
9
+
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.
13
10
</Callout>
14
11
15
-
<br />
16
-
17
-
<Imagesrc="https://res.cloudinary.com/pipedreamin/image/upload/v1732654019/Google_Chrome_-_Pipedream_Connect_2024-11-26_at_12.45.06_PM_yp4gnl.png"alt="Connect in development mode"width={350}height={529} />
18
12
19
13
## How to specify environment
20
14
21
-
You specify the environment when [creating a new Connect token](/connect/api/#create-a-new-token) with the Pipedream SDK or API. By default, the enviromment is set to `production`. When users succesfully connect their account, Pipedream saves it for that `external_user_id` in the specified environment.
15
+
You specify the environment when [creating a new Connect token](/connect/api/#create-a-new-token) with the Pipedream SDK or API. When users succesfully connect their account, Pipedream saves the account credentials (API key, access token, etc) for that `external_user_id` in the specified environment.
22
16
23
17
Always set the environment when you create the SDK client:
24
18
@@ -45,3 +39,11 @@ curl -X POST https://api.pipedream.com/v1/connect/{project_id}/tokens \
45
39
"external_user_id": "your-external-user-id"
46
40
}'
47
41
```
42
+
43
+
<Callouttype="warning">
44
+
When connecting an account in `development`, make sure you're signed in to pipedream.com in the same browser where you're connecting your account. This is only a requirement for the `development` environment. **You should only use the `development` environment with your own accounts when testing and developing, and not with your end users.**
45
+
</Callout>
46
+
47
+
<br />
48
+
49
+
<Imagesrc="https://res.cloudinary.com/pipedreamin/image/upload/v1732654019/Google_Chrome_-_Pipedream_Connect_2024-11-26_at_12.45.06_PM_yp4gnl.png"alt="Connect in development mode"width={350}height={529} />
0 commit comments