PROJECT EVIDENCE / EMAIL CLASSIFICATION / N8N

Cupid Errands:
route with evidence.

An automation demonstrator for structured AI email classification and deterministic departmental routing. The system is a tested portfolio workflow, not a claim of production-ready enterprise email infrastructure.

n8nGoogle GeminiGmailSlackData Tables
Watch public walkthrough ↗Inspect repository ↗
01 / VERIFIED COMPONENTS

Architecture and decision boundaries

Screenshot showing the Cupid Errands n8n email classification and departmental routing workflow.
Workflow screenshot from the public GitHub case-study directory. For implementation details and other screenshots, inspect the repository.
Ingest

A dedicated Gmail trigger captures messages, then Edit Fields normalizes the incoming request.

Classify

Gemini with a structured output parser returns a department and supporting fields.

Route

An n8n Switch chooses a department, followed by Gmail and Slack actions.

This workflow includes a duplicate-guard lookup and a processed-state update. Its existing execution screenshots and narrated walkthrough support a portfolio demonstration, but the current public repository does not include a sanitized executable n8n export.

02 / DEMONSTRATION EVIDENCE

What was tested and what remains open

AreaEvidenceCurrent limitation
Five department routesRecorded execution evidence and public walkthroughNot a regression suite
Duplicate-guard behaviorOne documented duplicate suppression testConcurrent message races not proven safe
Gemini temporary failuresRetry configuration described in the projectDead-letter and incident-alert handling not demonstrated
Low confidenceOutput includes a confidence fieldSeparate confidence-threshold gate needs verification or implementation
Integrity rule: A narrated demonstration and screenshot document observed behavior. They are not substitutes for sanitized workflow exports, automated test fixtures, security checks or independent deployment verification.
03 / ENGINEERING FOLLOW-UP

How this becomes stronger

Control

Add a deterministic confidence gate with explicit ambiguous-input behavior.

Idempotency

Use an atomic unique record before notifications to prevent concurrent duplicate sends.

Reliability

Reconcile partial failures, capture dead-letter events and alert after final retry.

Proof

Publish a sanitized workflow export, test scenarios, expected decisions and an evidence index.

These are proposed remediation steps. They are not represented as already implemented.

04 / ACADEMY APPLICATION

What learners can reproduce

Start with a deterministic router before adding AI classification. Compare the model's suggested department against a validated list, avoid automatic external actions when classification is uncertain, and test retry and duplicate-delivery scenarios.