Automating CRM updates and email triage with n8n
Every inbound email gets a category and an urgency, a row in a sheet that acts as your CRM, and an alert only when it matters. Built node by node, with the error branches included.
What the page covers
- The workflow at a glance, from Gmail trigger to alert
- Cleaning the email body before the model sees it
- A classification prompt that returns strict JSON
- Validating the output, routing it and writing to the CRM
- Error workflows, retries and a daily heartbeat
- Testing on real mail, and the ways this goes wrong
Frequently asked questions
- Do I need to know how to code to build this in n8n?
- No. Every step here uses built-in nodes: a Gmail trigger, an LLM node, a Switch, a Google Sheets node and a notification node. The only text you write is the prompt. A little JavaScript in a Code node helps with cleaning email bodies, but it is optional.
- Is it safe to let an LLM read my customers’ emails?
- It depends on where the data goes. Check the data-handling terms of the model provider you choose, send only the fields the workflow needs, and strip signatures and quoted history first. If emails contain regulated or sensitive data, run a self-hosted model or keep that mailbox out of the workflow.
- Should the workflow reply to emails automatically?
- Not at first. Have it create a draft and notify you, so a person approves each reply. Once the classifications have been correct for weeks on real mail, you can let it auto-send narrow, low-risk replies such as a receipt acknowledgement.
Akshay Mahajan — full-stack & AI web developer, Surat, Gujarat, India. akshaymad0608@gmail.com · +91 76008 85080