The problem
Shared inboxes mix time-sensitive issues, invoices, and routine mail. A naive AI agent can route quickly but may also make a confident-looking mistake with no review trail.
The workflow classifies an incoming email as urgent, invoice, or routine—but AI never gets the last word when confidence is low.
Public demonstration. Accounts and credentials are not included; the workflow uses buyer-supplied services and synthetic examples.
This browser demo uses fixed examples to show the decision boundary. It does not call an AI service or connect to an inbox.
Shared inboxes mix time-sensitive issues, invoices, and routine mail. A naive AI agent can route quickly but may also make a confident-looking mistake with no review trail.
The model must return a fixed JSON schema: category, confidence, and one-sentence reason. Confidence below 0.70 bypasses automation and alerts a human-review queue.
Urgent messages alert the team, invoices move through filing and ledger steps, and routine messages are labeled. The workflow—not the model—chooses the allowed action.
The importable n8n JSON contains no credentials. Operators connect their own inbox, model, team-chat, storage, and sheet accounts after reviewing the nodes.
email → {category, confidence, reason} → confidence gate → route → decision logThe complete workflow is available as an importable starter kit. The same pattern can be adapted to lead intake, support queues, document review, or approval routing without claiming autonomous judgment.
Send the categories, exception examples, tools, and desired human-review rule.
[email protected]