Test and Prod
Every workspace has two environments: Test, where you build and try flows, and Prod, where the flows your business relies on run, apart from your tries.
Why it matters
Change, run and break a flow in Test while its version on Prod keeps answering its webhook and keeping its schedule. Nothing reaches Prod until a workspace admin puts it there.
How it works
Test and Prod at the top of the sidebar pick the environment every page shows. Each thing keeps the two apart:
| Thing | Test and Prod |
|---|---|
| Flows | Built, published and run with Test run in Test; a version reaches Prod when it is put on Prod. |
| Connections | One connection, with separate credentials for each. New connections start with Test credentials only. |
| Secrets | One value for both, or a different value in Prod. |
| Tables | Columns are built in Test and put on Prod; each keeps its own rows. |
| Schemas | One name, one document each; Copy to Prod… copies Test's. |
| Files | Each keeps its own files; Copy to Prod… copies one. |
| Tasks | Each has its own pool of tasks a month. See Usage and tasks. |
An example
Your order flow is on Prod, answering your web shop's webhook. You add a node that checks the order's total and click Test run: it runs in Test, while Prod keeps answering orders. When the check works, you publish it and a workspace admin puts the new version on Prod.
Limits
- Two environments, Test and Prod; you cannot add another.
- Members build and run in Test; only workspace admins change Prod. See Invite members and choose their roles.