Running Workflows
There are four ways to trigger a workflow execution, depending on the trigger node type.
Manual Execution
The simplest way to run a workflow:
- Open the workflow in the builder
- Click the Run button in the toolbar
- The execution starts immediately using the working version
You can also right-click any node and select "Run from here" to start execution from a specific node (useful for testing individual nodes).
Single-Node Test Mode
When you run from a specific node, only that node executes — downstream nodes are not triggered. This is useful for:
- Testing a database query returns the expected results
- Verifying an HTTP request reaches the right endpoint
- Checking a transform produces the correct output
Webhook Triggers
Workflows with a Webhook trigger run when an external service sends an HTTP request to the webhook URL:
GET/POST https://your-domain/api/webhook/{token}/{slug}/The webhook URL is generated when you publish the workflow. Webhook triggers always use the published version.
Scheduled (Cron) Triggers
Workflows with a Cron trigger run automatically on a schedule — hourly, daily, or weekly. Cron triggers use the published version.
DataStore Triggers
Workflows with a DataStore trigger run when records are inserted, updated, or deleted in a specific DataStore table. DataStore triggers use the published version.
Execution Limits
Your team's plan determines:
- Daily run limit — maximum number of executions per day
- Concurrent execution limit — maximum workflows running simultaneously
If a limit is reached, new executions are rejected with an error message.