Skip to content

Commit 27c2d6c

Browse files
Update environments.mdx
1 parent 275a6ab commit 27c2d6c

File tree

1 file changed

+12
-10
lines changed

1 file changed

+12
-10
lines changed

docs-v2/pages/connect/environments.mdx

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -3,22 +3,16 @@ import Image from 'next/image'
33

44
# Environments
55

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`.
77

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-
<Callout type="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+
<Callout type="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.
1310
</Callout>
1411

15-
<br />
16-
17-
<Image src="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} />
1812

1913
## How to specify environment
2014

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.
2216

2317
Always set the environment when you create the SDK client:
2418

@@ -45,3 +39,11 @@ curl -X POST https://api.pipedream.com/v1/connect/{project_id}/tokens \
4539
"external_user_id": "your-external-user-id"
4640
}'
4741
```
42+
43+
<Callout type="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+
<Image src="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

Comments
 (0)