Overview
A workflow is a sequence of steps: a trigger plus one or more tasks. Triggers can be manual, API, webhook, scheduled, form submission, or another workflow completing.
Steps
- Create a new workflow and name it.
- Add a trigger and configure it (e.g. schedule interval or form link).
- Add tasks. Each task can use a platform tool (e.g. send email, update a sheet), call an AI model, or run code.
- Use the workflow environment for secrets and variables.
- Save, then publish to make it active. You can roll back to a previous version if needed.
Tips
- Every workflow belongs to an app. Create an app first if you don't have one.
- Start from a template to see a full example.
- Test with manual runs before enabling a schedule or form.
- Check run history and logs if something fails.
Version behavior
Runtime non-manual triggers (API, webhook, scheduled, form, and workflow triggers) execute the currently published version. Test runs can target the specific version you open in the dashboard/editor.
See Workflow Versioning and Publishing for detailed behavior.
Real-world example: a nightly Slack digest
Post a summary of yesterday's sign-ups to Slack every morning:
- Trigger — Scheduled (cron), daily at 08:00 in your timezone.
- Task 1 · Platform tool — query your database (or a Data Sheet) for rows created in the last 24 hours.
- Task 2 · AI Model — summarise those rows into a short paragraph ("12 new sign-ups, 3 from the EU…").
- Task 3 · Platform tool (Slack) — post the summary to
#growth.
Publish, then watch the first run under run history. Swap the schedule for a Webhook trigger and the same three tasks become an on-demand digest you can fire from anywhere.