Recurring work, done the same way every time.
A workflow is a sequence of steps you define once, plus a rule for when it starts. Because every run produces the same shape of result, it's safe to put on a schedule and forget about.
Five kinds of steps
Each step does one thing. Put them in order and the workflow runs them top to bottom. No code.
- Ask the AI. Send a prompt to a model and keep the result.
- Call an agent. Hand the current result to one of your agents, with its skills and knowledge.
- Check a condition. Up to three rules, built from choices and numbers, with a branch for each outcome.
- Send a notification. Tell people what happened.
- Save as a file. Write the result to Storage, where the team can open it.
When it runs, and what it reads
- On a schedule. Fixed times you add to the workflow. Runs count against your plan's monthly allowance.
- On demand. Start it yourself, or let an agent kick it off from a conversation.
- Up to 10 references. Files the workflow reads directly on every run, separate from the Knowledge your agents answer from.
- One run at a time per workflow. If it's asked to start while it's already running, that request is recorded as failed rather than queued, so two runs never overlap.
Every run is reported
A failed run notifies the people listed on the workflow; success notifications can be switched on as well. The run history stays with the workflow, and files it produced land in Artifacts.
- Enable and disable a workflow without deleting it. Choose who is notified, on failure (default on) and on success.
- Test before you publish. A workflow can be published only after a full test run succeeds, and a change closes it again until the next successful test.
- Restart from the failed step. Earlier results are kept.
What teams put on a schedule
Monday pipeline digest
Read the sales sheet, have the report agent summarize it, alert leads if pipeline dropped, save the digest.
Daily ticket triage
Pull new tickets, draft first replies from the help center, save drafts for the support lead to send.
Weekly release notes
Collect the week's changes, write them in the house format, notify the team, file the result.