Approval Flow Starter
Collect a draft, request a decision, and prepare the approved delivery.
The approval_flow template starts with Goal → Collect → Approval → Prepare result → Delivery. Use it when the next step needs a person to review the collected material. The sample collect node uses table.read and the downstream document.write node has its own approval policy.
| Field or output | How the draft uses it |
|---|---|
topic | Required text for read-source-data. |
sourceData | The result of collection, mapped to manual-review as draft. |
approvalDecision | The review node's output, passed to prepare-approved-result. |
deliverable | Output of the downstream action, mapped to choose-delivery as artifact. |
{
"topic": "Collect the sample release changes for a reviewer to check"
}- Bind the collect node to a test source. Make the review show the material, destination, proposed action, and details needed to decide.
- With a test target, inspect the run while it waits for review. Check how the run handles a declined decision, then use another test run to check the approved delivery and any action-level approval.
- If you replace the downstream action, review its own policy and run the same checks before using the final destination. For project delivery, ensure the action creates an artifact in the run and map its ID to Delivery.
Use Review before publish when the flow needs an explicit revision branch. See Runs and approvals for the approval lifecycle.