The draft is not the deliverable. The review is
Automated replies fail in a specific way. The answer is fluent, confident, and subtly wrong about a limit or policy, and the customer acts on it. Recovering costs more than the ticket would have.
A draft held for approval changes the economics entirely. The agent gets ninety percent that is typing and keeps ten percent that is judgment, which is the correct division.
What makes the review fast is not the draft quality. It is showing the agent which knowledge base passages the draft was built from. Reading three cited passages takes seconds. Verifying an uncited claim takes minutes and usually does not happen.
A draft that cannot cite anything should say so rather than answer anyway. That is the case where the agent needs to write, and knowing it immediately is worth more than a plausible paragraph.
How the ActionFlow runs on the canvas
The reply is generated before anyone approves it, and the sequence matters. Nothing reaches a person until the flow knows it can support what it wrote.
A Webhook trigger delivers the ticket. An HTTP Request node or a Notion node searches the knowledge base for relevant articles.
A Generate Object node returns three fields together: the draft reply, the passages it relied on, and a confidence flag indicating whether the knowledge base answered the question. Producing all three in one call keeps them consistent.
An If node reads the confidence flag. Drafts with support go to a Slack node in the Human in the Loop category with the passages attached. Drafts without support go to the same place marked unsupported, so the agent knows to write rather than edit.
After approval, an Email or Resend node sends the reply, or an HTTP Request node posts it to the helpdesk so the thread stays in one place.
A Google Sheets node records how often agents heavily edit the draft. A rising edit rate is the earliest signal that the knowledge base has drifted from the product.
Nodes this ActionFlow uses
- Webhook (Trigger): delivers the ticket as it arrives.
- Notion (Integration): searches the knowledge base. HTTP Request covers other systems.
- Generate Object (AI Core): returns draft, cited passages, and a support-confidence flag together.
- If (Control): marks unsupported drafts so the agent writes rather than edits.
- Slack (Human in the Loop): holds every draft with its passages attached. Teams and Email fit the same slot.
- Resend (Communication): sends the approved reply. Email and SMTP fit the same slot.
- Google Sheets (Integration): records edit rates as an early warning on knowledge base drift.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.