Starter Input Field Reference
Compare the required run inputs and the first checks for eight workflow starters.
These are the run input schemas for fresh drafts in the desktop template catalog. An existing draft may have been edited. Check its run form and node mappings first. Example file paths and connection targets in the guides must be replaced with resources from your test workspace.
| Template | Required by the draft schema | Optional fields or runtime data |
|---|---|---|
| Single Step | topic | The action produces summary for delivery. |
| Approval Flow | topic | The collected draft and approval decision are passed between nodes. |
| Review before publish | topic | reviewSummary and reviewApproved. Supply an explicit false or true for a branch test. |
| Failure to Inbox | topic | The edge conditions read the collection node's status and the Inbox mapping reads its error. |
| Daily AI Brief | briefTopic, sourceRefs, deliveryChannel, reviewApproved | scheduleHint, reviewSummary |
| Browser + Desktop Submission Audit | portalUrl, accountName, submissionTitle, submissionBody, uploadFileRefs, desktopAppName, reviewApproved | desktopEvidenceZone, reviewSummary |
| Product Image Batch | batchName, outputDirectory, namingPattern, generationPrompt, negativePrompt, qualityChecklist, and itemNSku, itemNPrompt, itemNReferences for slots 1 through 3 | The item reference fields are arrays. Each successful item has its own delivery step. |
| AI Cutout / White Background | sourceImageRefs, prompt, backgroundMode, outputDirectory | namingPattern, qualityChecklist |
Check values before running
- Enter
reviewApprovedas a Boolean. Existing defaults may select the submit or send branch. For a first check usefalse, verify what the preceding nodes can still do, and review the independent approval policy for the action. - Bind each browser or connection node to the intended test account and resource. A URL, account label, or channel label in the input describes a target. Check the actual binding in the node editor.
- Use readable source files and a dedicated writable test directory. For a batch, give each SKU a distinct reference and test the naming pattern on one item first.
- Keep the topic and review summary specific enough for a reviewer to identify the data, target, and proposed action.
See how to choose by risk before connecting a send, upload, or submission to an external system.