Review Before Publish Starter
Route a prepared draft to submit or revision and review the external action separately.
The review_publish template sets up draft preparation and a condition node named review-before-submit. The condition checks reviewApproved. Its submit branch uses the high-risk browser.submit_form node, which has its own approval requirement. The revise branch ends at return-to-edit.
| Input | How the draft uses it |
|---|---|
topic | Required text, mapped to draft preparation and submission context. |
reviewApproved | Optional in the schema. Explicit false selects the revise edge and true selects the submit edge. A fresh draft may prefill true. |
reviewSummary | Optional reviewer context mapped to the submit node. |
{
"topic": "Prepare test release notes for a staging form",
"reviewApproved": false,
"reviewSummary": "Check the draft title, content, and target before submission"
}- Check the mappings for what the submission actually reads. The default submit node maps
topicandreviewSummary. When a platform needs a prepared body, account, or concrete form target, configure that mapping and browser binding in the draft. - Test
falseand confirm the run ends on the revision branch. Check what a reviewer would need to edit before a new run. - With a test account and form, test
true. Verify the submit action still requires its own approval and inspect the receipt after an approved test submission.
For a template with an explicit human review step, see Approval Flow. For evidence after browser submission, see Browser submission workflows.