Emelia to Mattermost, never miss a hot lead reply
You finally get a reply to a campaign… and nobody sees it for hours. The lead cools off, the context disappears, and you’re stuck digging through inbox threads to figure out what happened.
This Emelia Mattermost alerts setup hits sales leads first, but marketing managers and client-facing agency owners feel it too. When replies are time-sensitive, “we’ll check later” quietly turns into lost revenue.
This workflow pushes Emelia campaign replies straight into Mattermost so your team can react fast. You’ll see what it does, what you need, and how to tailor it to your channels and process.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Emelia to Mattermost, never miss a hot lead reply
flowchart LR
subgraph sg0["Emelia Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/mattermost.svg' width='40' height='40' /></div><br/>Mattermost"]
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/emelia.svg' width='40' height='40' /></div><br/>Emelia Trigger"]
n1 --> n0
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n1 trigger
classDef customIcon fill:none,stroke:none
class n0,n1 customIcon
The Problem: Hot Lead Replies Get Missed
Email outreach only works when the follow-up is fast. But campaign replies don’t arrive in a neat, obvious place for everyone. They land in one person’s inbox, buried under internal threads, calendar noise, and “quick questions” that are never quick. Then come the human handoffs: someone forwards it, someone forgets, someone says “I thought you were handling that.” Meanwhile the lead is still online, still considering, and you’re not in the conversation.
It adds up fast. Here’s where it usually breaks down in real life.
- A reply can sit unseen for half a day if the owner is in meetings or out of office.
- Forwarded replies lose context, so you waste time re-reading the whole campaign history.
- Teams end up duplicating follow-ups because nobody knows who responded.
- When a lead asks something specific, the best internal expert is not looped in quickly enough.
The Solution: Instant Reply Alerts in Mattermost
This workflow listens for replies coming back to your Emelia campaigns, and the moment a lead responds, it posts an alert to your Mattermost channel. Instead of one person “owning” the inbox, the team sees the reply where they already work and coordinate. The alert includes the key details from the reply, so you can decide what to do next without opening Emelia and hunting for the thread. For many teams, that’s the difference between replying in minutes and replying “sometime today.” Honestly, speed is the whole game for outbound.
The workflow starts with an Emelia Trigger that fires when a lead replies to a campaign. It then formats the relevant reply information and sends a message to your Mattermost “Leads” channel so the right people can jump in immediately.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your team runs 3 outbound campaigns and gets about 10 replies a day. Manually, spotting and routing each reply can easily take 5 minutes (open Emelia, scan, copy key details, forward or Slack it, then answer questions). That’s roughly 50 minutes a day of coordination before the real work even starts. With this workflow, the “sharing” step takes basically no time because the alert is posted instantly; you just reply and assign the right owner. You get close to an hour back on busy days.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Emelia for detecting campaign replies.
- Mattermost to post reply alerts to your team.
- Mattermost access token (create it in Mattermost integrations/bots).
Skill level: Beginner. You will connect accounts, pick a channel, and test with a real reply.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A lead replies to an Emelia campaign. The Emelia Trigger watches for replies and starts the workflow as soon as one lands.
The workflow grabs the details you actually need. Instead of sending a vague “new reply” notification, it uses the reply data (like sender info and message content) so the alert can be acted on quickly.
Mattermost gets a clean, consistent alert. n8n posts to your Mattermost “Leads” channel (or any channel you choose), which means the right people see it without inbox access.
Your team responds and routes the reply. The message is now in the same place where you assign ownership, tag someone for input, and keep a searchable record.
You can easily modify the target channel and the alert format based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Emelia Trigger
Set up the trigger that listens for campaign replies in Emelia and initiates the workflow.
- Add the Campaign Reply Trigger node as the workflow trigger.
- Set Events to include
replied. - Set Campaign ID to
[YOUR_ID]. - Credential Required: Connect your emeliaApi credentials.
⚠️ Common Pitfall: Leaving Campaign ID as [YOUR_ID] will prevent the trigger from receiving real replies.
Step 2: Connect Mattermost
Authorize Mattermost so the workflow can post alerts to your channel.
- Open the Post Mattermost Alert node.
- Credential Required: Connect your mattermostApi credentials.
Step 3: Configure the Mattermost Alert Message
Customize the notification sent to Mattermost when a reply arrives.
- In Post Mattermost Alert, set Message to
={{$json["contact"]["firstName"]}} from {{$json["contact"]["company"]}} has replied back to your campaign.. - Set Channel ID to
[YOUR_ID]. - Keep Attachments empty unless you plan to add structured fields.
Tip: The message uses dynamic fields from Emelia. If a contact lacks firstName or company, consider adding a fallback message.
Step 4: Review the Execution Flow
Confirm the workflow wiring matches the intended sequence.
- Ensure Campaign Reply Trigger connects directly to Post Mattermost Alert.
- Verify there are no parallel branches; this workflow runs in a single linear flow.
- The Flowpast Branding sticky note is informational and does not affect execution.
Step 5: Test and Activate Your Workflow
Validate the trigger and notification before enabling the workflow in production.
- Click Execute Workflow to put Campaign Reply Trigger into listening mode.
- Send a test reply from Emelia for the specified campaign.
- Confirm a new message appears in Mattermost with the contact’s name and company.
- Once confirmed, toggle the workflow to Active for continuous monitoring.
Common Gotchas
- Mattermost credentials can expire or need specific permissions. If things break, check your bot/token settings in the Mattermost Integrations area first.
- If you’re routing alerts to a private channel, the bot must be added to that channel or your message will fail silently.
- Emelia replies can include signatures and long threads. If alerts feel noisy, trim the message content in n8n before posting so the channel stays readable.
Frequently Asked Questions
About 20 minutes if your Emelia and Mattermost accounts are ready.
No. You connect Emelia and Mattermost, then test a reply. Most of the work is picking the channel and deciding what the alert should include.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in any Emelia plan limits you’re on (since reply tracking depends on your campaign volume).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, but you’ll add one small decision point. The simplest approach is to duplicate the Mattermost message step and use a Switch/If condition in n8n so Campaign A posts to one channel and Campaign B posts to another. You can also adjust the “Post Mattermost Alert” message content to tag a specific user or add a short label like “Reply from CFO campaign.”
Most of the time it’s an expired or incorrect token. Regenerate the Mattermost personal access token (or bot token) and update the credentials in n8n. Also check that the token has permission to post, and that the bot is actually a member of the channel you’re targeting. If it only fails during busy periods, you may be hitting server-side limits, so try a different channel or confirm your Mattermost instance isn’t under load.
A typical small team can run hundreds of reply alerts a day without issues, and scaling mostly depends on your n8n plan and your Mattermost server. On n8n Cloud Starter, you’re limited by monthly executions; higher plans handle more. If you self-host, there’s no fixed execution cap, but your VPS resources become the ceiling. This workflow is lightweight because it’s only a trigger and a single message send, so throughput is usually not the bottleneck.
Often, yes. n8n is easier to extend when you want branching rules (like different channels per campaign), and self-hosting avoids per-task pricing when volume grows. It also keeps the workflow logic in one place, which is handy when you want to add steps later, like logging replies to Google Sheets or notifying a backup channel. Zapier or Make can be quicker for a basic alert, though. Talk to an automation expert if you’re deciding based on volume and team workflow.
Once this is live, lead replies stop being a private inbox problem and become a visible team signal. Set it up once, and you’ll wonder why you waited.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
