Triage Inbox And Route Emails

Overview

Founders, sales teams, and customer success managers waste hours every day manually reading, sorting, and forwarding emails from generic hello@ or sales@ addresses. This workflow acts as an intelligent traffic director: hot leads get an immediate personalized response, invoices go to accounting, support issues become Zendesk tickets, and spam is silently ignored—completely hands-free.

How It Works

The workflow follows a simple four-step pipeline:

1. Receive the email — A webhook trigger accepts incoming email data (sender, subject, body) from your email provider or automation tool.
2. Classify with AI — An AI agent reads the email and categorizes it as exactly one of: Lead, Support, Invoice, or Spam. For leads and support emails, it also extracts the sender's name, company, and a request summary.
3. Build route-specific payloads — A routing code node evaluates the category and constructs the correct data payload for each downstream action. Categories that don't match a given route produce a null payload, which the downstream node safely skips.
4. Execute parallel actions — Up to four actions fire simultaneously depending on the category.

Routing Paths by Category

Workflow Nodes

Prerequisites

To deploy this workflow, you will need:

1. An inbound email webhook — A tool like Make.com, Zapier, or a native Gmail/Outlook webhook configured to send new emails to your Needle trigger URL.
2. CRM API endpoint — Your GoHighLevel, HubSpot, or custom CRM endpoint to receive lead data.
3. Zendesk API credentials — A Base64-encoded auth token with permission to create tickets.
4. Email API provider — An account with Resend, SendGrid, or Mailgun to dispatch forwarded invoices and lead replies.
5. Slack connection — A connected Slack account with access to your #support channel (for support notifications).

Setup Instructions

1. Import the template into your Needle workspace.
2. Update the CRM HTTP node — Replace the placeholder URL and Authorization header with your real CRM endpoint and API key.
3. Update the Zendesk HTTP node — Replace the subdomain in the URL and the Authorization header with your Zendesk credentials.
4. Update the email HTTP nodes (Invoice Forward and Lead Reply) — Replace the API key in the Authorization header with your email provider's key. Update the from address in the routing code node to match your verified sending domain.
5. Connect your Slack account in the Slack notification node and confirm the target channel.
6. Configure your email webhook — Point your email provider or automation tool to send a POST request to the Needle webhook URL whenever a new email arrives.

Testing

Send a test POST payload to your Needle webhook URL to verify the full pipeline. Here's a sample lead email:

{
  "senderEmail": "ceo@startup.io",
  "senderName": "David Chen",
  "subject": "Interested in Voice Automation",
  "body": "Hi team, I run a logistics company and we are looking to automate our inbound dispatch calls. Can we schedule a demo for next Tuesday? Thanks, David."
}

You should see:

• A new lead record created in your CRM
• A personalized reply email sent to the test sender address
• No Zendesk ticket or invoice forward (those paths are skipped for leads)

Try similar test payloads with support, invoice, and spam content to confirm each routing path works correctly.

Tips

• Spam filtering saves money. Because spam is caught before any external API calls, you avoid unnecessary costs on your CRM, Zendesk, and email provider.
• Response speed matters. Studies show that responding to a lead within five minutes makes you 21× more likely to qualify them. This workflow replies in seconds.
• Customize the AI prompt to match your business context. If you sell B2B software, tell the AI what your product does so it can draft more relevant lead replies.