Environments
Environments let you run the same workflow with different credentials and configuration values depending on the context — for example, development, staging, and production.
How environments work
An environment is a named profile that can override the values of secrets and connections. When a workflow runs in a specific environment, Blokkio substitutes the environment-specific values instead of the project defaults.
This means a single workflow can call different API endpoints, use different credentials, or apply different signing keys based on which environment it runs in — without changing the workflow definition.
Creating an environment
Go to Settings → Project → Environment Settings and click New Environment. Give it a name (e.g. Production, Staging).
The number of environments per project is controlled by your plan.
Setting a default environment
One environment can be marked as the default. New workflow executions automatically use the default environment unless overridden.
To set the default, open the environment's settings and toggle Set as default.
Overriding values
Within an environment, you can assign environment-specific values to:
- Secrets — override a secret's value for this environment
- Connections — override a connection's credentials for this environment
Values not overridden fall through to the project-level defaults.
Use cases
| Scenario | How environments help |
|---|---|
| Different API keys per environment | Override the API key secret per environment |
| Separate staging and production webhooks | Different connection URLs per environment |
| Testing without affecting production | Use a staging environment with safe credentials |
Plan limits
The number of environments per project is limited by your subscription plan. Check Settings → General → Subscription to see your current limits.