Audience
- Power users automating operational tasks
- Admins responsible for secure trigger-based automation
Prerequisites
- Workspace access with workflow permissions
- Plan level that includes workflow functionality
- Clear ownership for trigger token distribution
Plan and security caveats
- Workflows are plan-gated. If the feature is unavailable, verify subscription and workspace context first.
- Trigger tokens grant execution capability; treat token URLs as secrets.
- Regenerating a token invalidates old trigger links and integrations.
Steps
1) Create workflow
- Open Workflows.
- Select Create Workflow and define flow logic.
- Save draft and run initial validation.
2) Publish workflow
- Review draft logic and connected actions.
- Select Publish to enable runtime execution.
- Confirm published state in workflow list/details.
3) Trigger workflow externally
- Copy trigger URL/token from workflow settings.
- Call trigger endpoint from external system.
- Confirm execution appears in history.
4) Regenerate trigger token (when required)
- Open workflow trigger settings.
- Regenerate token after suspected leak or rotation policy.
- Update all upstream systems with the new token URL.
5) Unpublish workflow
- Open workflow settings.
- Select Unpublish to stop new executions.
- Verify that new trigger attempts no longer execute.
Expected result
You can operate the full workflow lifecycle (create -> publish -> trigger -> monitor -> unpublish) with controlled token security and execution visibility.Troubleshooting
Workflow does not trigger
- Confirm workflow is published.
- Verify token URL is current (not regenerated since integration setup).
- Confirm external caller sends expected payload shape.
Execution starts but fails
- Review execution history details for failing step.
- Validate dependencies/integrations used by workflow action.
- Re-test with minimal payload.
Feature unavailable/permission denied
- Confirm plan includes workflows.
- Confirm user role has workflow access in this workspace.