Choose a Starter by Risk
Decide where a workflow needs review, approval, and evidence of an external action.
Check the effect of each node. Reading a source and producing a local draft have a different impact from uploading a file, editing a knowledge base, sending a message, or publishing a page.
| Effect | Starting point | First check |
|---|---|---|
| Read, summarize, or prepare a local result | Single Step | Use a test source and check which delivery target is selected. |
| Let a person inspect a result before the next action | Approval Flow | Provide the draft, intended action, destination, and evidence the reviewer needs. |
| Allow submit or return for revision | Review before publish | Test both paths on a non-production target. Inspect the condition and the submit node's separate approval policy. |
| Submit a form and retain evidence | Browser + Desktop Submission Audit | Check what upload does before review, and verify the account, final submission receipt, and evidence after the action. |
| Recover from a failed step | Failure to Inbox | Include enough context to decide whether to retry, especially if an earlier external action may have succeeded. |
A reviewApproved input selects a branch in templates that use it. Some starter drafts prefill true. For a first branch check use false, test resources, and the approval controls for the actual node. For browser templates, form entry and uploading may already occur before the review branch. Use an account and files designated for testing even when final submission is blocked.
For an external write, check the concrete account, target, data, and action at approval time. If a run stops after sending or submitting, look for a receipt or verify the external state before rerunning. See Runs and approvals.