Workflows
Chain trigger, agent, review and publish on a visual canvas.
Draw the process once, then let it run
Some work is more than one step: a new release note should start an agent, the draft should go to a reviewer, and only the approved posts should publish. Workflows let you draw that as a flow on a canvas, then run it on a schedule or when a source publishes.
A workflow drives the real pipeline, not a copy of it. Drafts land in your Publish Queue, agent runs appear in History, and the usual limits still apply: your task allowance, your budget caps and your approval rules.
Five kinds of step
- Trigger — how it starts: run manually, on a schedule (every hour, day or week), or when a connected doc or RSS source publishes.
- Agent — one of your agents drafts posts, exactly as if you had run it from the Agents page.
- Review — the human gate. Reviewers are notified in the app and by email; on a team you can assign the review to one person.
- Publish — publishes the eligible drafts from this run. The run log shows how many made it.
- Condition — branches the flow on whether the last agent step succeeded, or on how many drafts the run produced.
The rule that always holds
The Publish step never ships a draft that is awaiting approval or was rejected, with or without a Review step in the flow. A Review step adds the notification; the no-unapproved-publishing rule holds regardless.
Make it run itself
Add a schedule or document trigger and switch the workflow On. A scheduled workflow shows its next run time on its card. Switch it Off to pause; nothing runs automatically until it is on again.
"Every day" means about every 24 hours from when the schedule was set, not a clock time. Saving a workflow restarts that countdown.
Workflows suit the repeatable campaigns: a weekly roundup, a launch sequence, an announcement for every changelog entry. For a single agent on a rhythm, a plain schedule is simpler. The builder is explained step by step in Workflows.