Skip to main content
Every published workflow can be executed in three ways. You can enable any combination of triggers for a single workflow.

Manual

Run a workflow directly from the editor by filling out the input form and clicking Run. This is useful during development and for one-off executions. The form is auto-generated from the inputs section of your config.yaml. Required fields must be filled; optional fields use their default values if left empty.

API

Trigger a workflow programmatically by sending an HTTP POST request to the execute endpoint. Enable the API trigger in the config.yaml:
Then call the endpoint with your workflow’s API key:
The request body maps to the workflow’s declared inputs. The response includes the execution status and outputs. API triggers always run the latest commit of the workflow.
Each workflow has its own API key, visible in the API Trigger tab of the editor. Keep this key secret — it authenticates requests to your workflow.
See the API reference for full details.

Schedule

Run workflows on a recurring schedule using cron expressions. Configure schedules in the config.yaml:
Scheduled runs execute the latest commit. To pause a schedule, set enabled: false and commit the change.

Choosing the right trigger