AI Email Routing with n8n in the Philippines

The inbox is usually where work gets messy first. Leads, support issues, invoices, admin notices, and newsletters land in the same place, then someone has to decide what matters.

That makes email routing a better first AI workflow than a shiny chatbot for many teams. It starts with a real operational problem: the right message needs to reach the right person before it goes cold.

For teams comparing n8n Philippines options or looking at AI automation Philippines services, this is a better first workflow than a broad AI agent because the work stays visible, narrow, and testable.

The useful automation is not "AI replies to everything." A safer first version is smaller: read the email, classify what kind of work it is, add a label, and notify the right team channel.

Why this is a good n8n example

This is the kind of workflow where n8n starts to make sense. A simple rule can catch obvious keywords. But real email is messy. A pricing request may not say "sales." A support issue may look like a complaint. A billing problem may mention a contract, invoice, and payment in the same message.

n8n is useful here because the workflow is more than one AI prompt. It needs a trigger, an AI classification step, structured output, category mapping, Gmail labels, routing branches, Slack notifications, and a fallback when the AI output is unclear.

The workflow in plain English

The example workflow is intentionally narrow. It does not try to be a full inbox replacement, CRM, helpdesk, or AI agent with every tool connected.

A simple prompt to start with

The prompt should keep the AI's job small. In this workflow, the AI does not reply to the customer, click buttons, or decide what the business should do. It only reads one email and returns clean JSON that n8n can use in the next step.

You are a strict email triage assistant for a busy team.

Your only job is to classify ONE incoming email into exactly ONE category.

Allowed categories:
- Sales / Lead
- Support
- Finance / Admin
- FYI
- Needs Review

Classification rules:
- Sales / Lead: pricing, quotes, new projects, partnerships, demos, service inquiries, buying intent.
- Support: problems, bugs, access issues, complaints, delivery issues, urgent help.
- Finance / Admin: invoices, payments, billing, contracts, legal, account administration.
- FYI: newsletters, promotions, automated updates, low-priority information, no team action needed.
- Needs Review: unclear, mixed topics, sensitive, risky, or not confident.

Return valid JSON only.
Do not write anything outside the JSON.
Do not create replies.
Do not take actions.
Do not invent missing details.

Classify this email:

Subject: {{subject}}
From: {{from}}
Body: {{body}}

Return JSON using this schema:

{
  "category": "",
  "priority": "",
  "summary": "",
  "reason": "",
  "route": ""
}

Rules for JSON values:
- category must be one of: Sales / Lead, Support, Finance / Admin, FYI, Needs Review
- priority must be one of: high, medium, low
- summary must be one short sentence, max 15 words
- route must be one of: sales, support, admin-finance, fyi, needs-review

Treat this as a starting point, not a universal prompt. Run it against real examples from your own inbox: a sales inquiry, a complaint, an invoice, a newsletter, and one messy email that could go either way. If the results feel wrong, adjust the categories, priority rules, and fallback conditions before connecting notifications.

The four-label version

I like starting with four labels because it is enough structure to be useful, but not so much that the team has to maintain a giant taxonomy.

The exact labels should change by team. A clinic might use Booking, Billing, Patient Concern, and FYI. A service business might use New Lead, Active Client, Supplier, and Low Priority. A small SaaS team might use Sales, Support, Product Feedback, and Admin.

Why not start with a general AI agent?

A general agent can sound more exciting: give it Gmail, Slack, Notion, CRM access, and let it decide what to do.

I would not start there for this kind of workflow.

Email routing needs predictable behavior. The team should be able to inspect why a message went to sales, why an invoice went to admin, and why a newsletter did not interrupt anyone. A narrow n8n workflow makes that easier because the branches are visible.

A full agent may make sense later when the routing is already trusted and the team wants deeper actions: checking a CRM record, creating a task, drafting a reply, or looking up past customer context. But the first useful build should be narrow enough to test.

What can be customized

The nice thing about this workflow is that it can stay small or grow gradually.

• Categories: change the four labels to match how your team actually works.
• Priority rules: decide what should be treated as high priority, normal, or low priority.
• Notification channels: use Slack channels, email, Google Chat, Teams, or a task tool.
• Destinations: send sales leads to a CRM, support issues to a helpdesk, or admin messages to a shared tracker.
• AI model: use a fast low-cost model for classification, then reserve stronger models for drafting or deeper analysis if needed.
• Human review: keep unknown or sensitive messages in Needs Review instead of forcing a category.

For most teams, the customization matters more than the AI model. A clean set of labels and routing rules will beat a clever prompt wrapped around a messy process.

When this is useful

An AI email router is worth considering when the inbox mixes different kinds of work and the wrong person keeps seeing the wrong email.

• Sales inquiries get buried under newsletters and automated notices.
• Support issues sit in a general inbox until someone checks manually.
• Admin or billing messages need to reach a specific person quickly.
• The founder or owner is still acting as the first-pass inbox filter.
• The team wants Slack notifications, but only for messages that actually matter.

When not to build it yet

This is not always the right first automation. If the inbox gets five important emails a week, a shared label and a daily habit may be enough.

I would also avoid automating too early if nobody agrees what the categories mean, if sensitive customer data should not be sent to an AI model, or if the team will ignore the Slack channels anyway.

Start with the manual version first. If people can route five sample emails by hand and agree on the labels, then it is easier to automate.

Cost and ownership

The build cost depends on volume, tools, edge cases, AI model, and how many destinations are involved.

As a rough starting signal, a workflow map can start from PHP 1,000. A simple fixed-scope automation can start from PHP 2,500. A larger n8n or AI workflow buildout can start from PHP 8,000 after the map, especially if it includes testing, handoff notes, multiple routes, CRM records, or support after launch.

Tool subscriptions, hosting, API usage, and ongoing maintenance are separate. n8n can be self-hosted, but someone still has to own updates, credentials, failures, and backups. That ownership is part of the workflow, not an afterthought.

If you are exploring workflow automation Philippines, business automation Philippines, or AI workflows Philippines projects, start by mapping one inbox or lead process before buying more tools.

What to ask before building

Before building an email router, answer these questions:

• Which inbox should trigger the workflow?
• What are the first four labels that matter?
• What counts as urgent enough to notify someone immediately?
• Which messages should never be auto-routed?
• Where should sales, support, admin, and FYI messages go?
• Who owns the Gmail, Slack, n8n, and AI credentials?
• What should be documented so someone else can inspect the workflow later?

Those questions are less exciting than "build an AI agent," but they are what make the workflow usable.

Bottom line

If the inbox is the bottleneck, start with five real emails and decide where each one should go. Then build the smallest workflow that can label, route, and flag the uncertain ones for review.

Sources

• n8n documentation
• Zapier vs Make vs n8n Pricing: A Real Lead Form Example
• Claude connectors and connected AI workflows