Workflows
Triggers and Approvals
Start workflow runs from manual, API, schedule, or webhook triggers, and review human approval gates.
Every workflow has one trigger. After you Publish, the trigger is what creates new runs.
Triggers
| Trigger | When a run starts |
|---|---|
| Manual | You click Run in the editor and pass optional JSON input |
| API | Your application starts a run through the console product API for that workflow |
| Schedule | A cron expression (with timezone) fires after the workflow is published |
| Webhook | An inbound webhook arrives (for example a chat-platform message) |
Change the trigger type from the canvas, then publish again so the live version matches.
Scheduled workflows only fire while they remain published. Archiving or replacing the published version stops the previous schedule.
Approval gates
Add an Approval node when a person must review the work so far.
- The run pauses (
waiting for approval). - The request appears under Products → Workflows → Approvals.
- A reviewer approves or rejects.
- The graph continues on the approved branch or the else branch.
You can connect the else branch back to an earlier agent or LLM node so a rejection can request a revision. Cap how many times that loop may repeat in the approval node settings (the console default is conservative).
Timed-out approvals follow the else branch.
Tips
- Keep approval nodes close to irreversible actions (sends, writes, external posts).
- Use Delay when you need to wait, not when you need a person.
- Agent invocation nodes still produce normal runs under Products → Agents → Runs, so you can inspect both the workflow timeline and the agent trace.