Practical guide. Provider claims are attributed to the sources below. This page does not claim a new independent DARC benchmark.
For: Builders automating document, support or content workflows
Before you start: A test integration account · A clear definition of an approved action
⚡ TL;DR — the 30-second version
- Separate drafting from sending.
- Approve exact content and recipient.
- Treat retries and ambiguous delivery as first-class states.
A useful automation does not need an agent to decide everything. For an incoming support request, a model can propose a category and draft a response while ordinary workflow logic validates fields, checks permissions and asks for approval. This is a better first project than an agent that can read and send every email in your account.
The same pattern works in n8n, Dify, Flowise or hand-written code. The interface changes; the responsibilities do not.
“Put flexibility inside the model step and reliability around it.”
Field guide / 01
01 / Normalize and minimize the input
Assign a stable internal event ID before calling a model. Remove attachments or personal fields that are not needed for the task. Validate the input's size and type, and send unsupported formats to review instead of improvising a conversion.
For the first version, process only one known event type. Adding five connectors before you understand duplicate delivery makes debugging much harder.
Field guide / 02
02 / Ask for a proposal, not an action
The model should return a category, a draft and a review reason. It should not receive a send-email credential. Check the category against an allowlist and validate whether the evidence supports the draft.
Use an explicit unknown state for ambiguity. A workflow that forces every request into a category can confidently route a financial complaint to a generic support answer.
| Stage | Allowed behavior | On failure |
|---|---|---|
| Intake | Normalize and deduplicate | Error queue |
| Model | Classify and draft | Review required |
| Validator | Check structure and policy | Reject proposal |
| Reviewer | Approve exact content | Edit or decline |
| Sender | Execute once with scoped credentials | Record outcome, bounded retry |
Field guide / 03
03 / Bind approval to the exact action
Show the recipient, message and relevant evidence to the reviewer. If the content changes after approval, require a new approval. An approval for 'respond to this customer' is broader and less auditable than approval for one exact message.
Timeouts and cancellations need defined behavior. An abandoned approval should not silently become permission after a retry or workflow resume.
Field guide / 04
04 / Replay the event before shipping
Submit the same event twice, interrupt after approval and simulate a provider timeout. Confirm that you create at most one external action and keep a record of uncertain delivery states. A timeout after sending may mean the action succeeded even if your application did not receive confirmation.
The deliverable is a flow diagram, three failure traces and a successful approval path. Only then expand to more event types or automatic approval for a narrow, tested class.
Before you ship
0/5Use this as a review aid. Checks reset when you leave this page.
Sources & verification
Last checked 23 Sept 2026. Publication dates and access conditions belong to the linked originals.
- 01n8n — integrating AI into workflowsn8n↗
- 02Dify — workflow quick startDify↗
- 03Flowise — assistants, chatflows and agentflowsFlowise↗
- 04MCP — tools, permissions and validationModel Context Protocol↗