Build a privacy-friendly AI support responder

Why not just use LIAM or similar tools?

AI email assistants are becoming mainstream. Tools like LIAM promise to draft replies, manage your inbox, and handle scheduling — all for $25/month. The catch? They need full OAuth access to your mailbox. Every email you've ever received, every attachment, every conversation.

That's a lot of trust to put in a single service. If they get breached, if their AI hallucinates a response to the wrong person, if their privacy policy changes — your entire email history is exposed.

There's a better architecture.

How it works

At no point does the AI have access to your mailbox. It sees one email at a time, only when EmailConnect forwards it. That's the fundamental architectural difference.

What you'll need

Step 1: Set up EmailConnect

Create an alias for your support email — something like support@in.yourdomain.com. Point it at an n8n webhook URL. EmailConnect handles the MX records, email parsing, spam filtering, and DKIM/SPF validation. You get clean, structured JSON.

If you haven't set up EmailConnect yet, follow the getting started guide — it takes about 10 minutes.

{
  "from": {
    "email": "customer@example.com",
    "name": "Sarah Johnson"
  },
  "subject": "Can't reset my password",
  "content": {
    "text": "Hi, I've tried resetting my password three times but I'm not getting the email. Can you help?",
    "html": "..."
  },
  "attachments": []
}

Step 2: Build the Notion knowledge base

Create a Notion database for your support articles. This is what the AI will search when a question comes in. Keep it simple:

Populate it with your existing FAQ, help docs, or common support responses. The more articles you add, the better the AI gets at finding relevant answers. Start with 10–20 articles covering your most common questions.

Step 3: Build the n8n workflow

This is where the magic happens. The n8n flow connects EmailConnect's webhook to your Notion KB and the LLM.

The complete n8n workflow — Webhook → KB lookup → LLM match → draft reply or escalate

Node-by-node walkthrough

Conversation memory

A subtle but powerful detail: the flow includes conversation memory per sender. Each LLM agent has a buffer window memory keyed by the sender's email address. If the same person emails again, the AI has context from previous exchanges — it can reference past conversations and avoid asking the same questions twice.

Step 4: The human-in-the-loop option

Here's where this setup really pulls ahead of tools like LIAM: you can add a human approval step. Instead of the AI sending responses autonomously, it can send you the draft via Telegram with approve/reject buttons.

This gives you the speed of AI with the safety net of human judgment. Run it in approval mode until you trust the system, then switch to fully automatic when you're confident.

How we use it at EmailConnect

This isn't hypothetical. We run this exact setup on support@emailconnect.eu. When a customer emails our support address:

• EmailConnect receives and parses the email
• n8n queries our Notion knowledge base (help articles, FAQs, docs)
• An LLM drafts a response grounded in our actual documentation
• If the match is strong, the reply goes out. If not, the customer hears that their message was forwarded, and we handle it manually.

It handles the majority of common questions automatically. The rest get escalated — no false confidence, no hallucinated answers.

Tips and considerations

The privacy argument

This build demonstrates a broader principle: you don't need full mailbox access to build smart email automation. Selective email routing — where you control exactly what the AI sees — is both safer and more flexible.

With EmailConnect, the AI never has persistent access to anything. Each email is a single, isolated event. Your mailbox stays yours. Your customer data stays under your control. And you can swap out any component — the LLM, the KB, the automation platform — without being locked into a single vendor.

Questions about building this workflow? Reach out at hello@emailconnect.eu.