-
Notifications
You must be signed in to change notification settings - Fork 5.5k
(docs) Invoke workflows for external users #14589
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
dannyroosevelt
merged 14 commits into
master
from
docs/invoke-workflows-for-external-user
Nov 22, 2024
Merged
Changes from 5 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
6f1eadb
Initial commit of workflow invoke docs
dylburger b2b0c51
More example fixes
dylburger 7c104c4
Small changes
dylburger b529c0a
small patch
dannyroosevelt 2572abe
First cut of workflow invoke errors
dannyroosevelt c9e6a0b
Workflow errors, WIP Connect troubleshooting
dannyroosevelt b8e1a7a
Troubleshooting info
dannyroosevelt 8e73fa8
Fixing `environment` references
dylburger 32f098e
small edits to troubleshooting page
dylburger c065eb4
Merge remote-tracking branch 'origin/master' into docs/invoke-workflo…
dylburger 95975b4
Fixing bad merge
dylburger d0032bd
Info on testing workflows
dannyroosevelt 40c73de
Merge branch 'master' into docs/invoke-workflows-for-external-user
dannyroosevelt 83ba7e1
Update index.mdx
dannyroosevelt File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,10 +1,20 @@ | ||
| import Callout from '@/components/Callout' | ||
|
|
||
| # Environments | ||
|
|
||
| Pipedream Connect projects support two environments: `development` and `production`. | ||
|
|
||
| 1. Connected accounts and credentials stored in `development` remain separate from `production`. | ||
| 2. In `development`, you can use the official Pipedream OAuth apps, so you can test integrations without creating your own OAuth client. | ||
| 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). | ||
|
|
||
| ## How to specify environment | ||
|
|
||
| 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 `project_environment`. | ||
| 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`. | ||
|
|
||
| ## Using development mode | ||
|
|
||
| When connecting an account in `development` mode, the end user who is connecting their account must be signed in to pipedream.com. | ||
|
|
||
| <Callout type="warning"> | ||
| `development` mode should only be used by you and your team for testing. When you're ready to test with real users, switch to `production`. | ||
| </Callout> | ||
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix typos in environment specification
There are two typos in this line:
📝 Committable suggestion