Choose a Starter by Goal
Match the expected result to a workflow template.
Start with the result you need to inspect or deliver. A product launch can involve preparing images, gathering research, or submitting a draft to an external site. Each uses a different workflow.
| Expected result | Template to start with | What to verify |
|---|---|---|
| One result from a capability and one delivery | Single Step | One test input reaches the selected capability and its output reaches delivery. |
| A decision before a consequential action | Approval Flow or Review before publish | A person can see the draft before the action, or the branch clearly separates submit and revise. |
| A useful handoff after a failed run | Failure to Inbox | Run details retain the failed-node error, and Inbox triage can surface eligible failures. |
| Three SKU images or a single cutout | Product Image Batch or AI Cutout / White Background | The provider supports the action, and each result can be matched to its source image. |
| A brief with sources, or a refreshed knowledge base | Daily AI Brief or Customer Knowledge Update | Source scope and citations for the brief, or the actual knowledge base and a test question for an update. |
| A web submission with evidence | Browser + Desktop Submission Audit | Account, form fields, attachment contents, approval, and a receipt paired with the browser and desktop evidence. |
| Follow-up, launch, onboarding, or escalation | Sales Follow-up, Campaign Launch Pack, Customer Onboarding Pack, or Support Escalation Resolution | The matching lead, campaign, customer, or ticket data and the exact destinations for each action. |
| A packaged result or an inspectable local preview | Artifact Flow or App Capsule delivery | The artifact source, the output, and who can open the delivered result. |
If the result will go to a real account or service, choose the review and evidence steps by risk before connecting the action. For a template close to your process, adapt the draft and verify one change at a time.