Skip to main content
An environment is a separate set of subscribers, workflows and integrations inside a workspace. Use one for testing so you never email real people by accident. Every workspace starts with Production. Add as many others as you like, such as staging or one per developer. Only production counts towards your plan.

Create and switch environments

Every command runs against the current environment. To run one command against another, add --environment <environmentId>.
Tell your agent which environment to use, such as “use staging”.

What’s separate

Nothing is shared between environments. A new environment starts empty, with no subscribers, workflows or integrations.

Moving from staging to production

Nothing copies workflows between environments, so keep each workflow’s JSON in your repo and create it in each environment:
After a change, run workflows update <workflowId> --file welcome.json in each environment. Your agent can do the same: “Copy the welcome workflow from staging to production.”