How to Set Up Cold Email Reply → Pipedrive Task + Slack Alert in 60 Seconds in n8n

A prospect replies to your cold email at 9:14 AM. You see it at 2:30 PM — after they've already cooled off, forwarded it to a colleague, or replied to your competitor who answered first. The gap between "they wrote back" and "you did something about it" is where deals die. This article shows you how to close that gap to under 60 seconds using a single n8n workflow that watches your inbox, creates a Pipedrive task, and fires a Slack alert the moment a reply lands.

The problem: replies rot in the inbox

Cold outreach only works if the follow-up is fast. Data on reply speed is brutal — responding within five minutes versus thirty minutes can multiply your connect rate by an order of magnitude. But the reality for most founders and SDR teams looks nothing like that:

• Replies land in a shared or personal inbox that nobody watches continuously.
• The person who sent the sequence is heads-down on something else.
• By the time someone notices, the prospect's buying intent has evaporated.
• There's no task, no owner, no record in the CRM — so the reply gets triaged as "I'll deal with it later" and never resurfaces.

Manually refreshing Gmail is not a system. It's a tax on your attention, and it scales terribly. The moment you're running more than one sequence, or more than one rep, inbox-watching becomes the bottleneck that quietly kills your pipeline.

The solution: an event-driven reply pipeline

Instead of pulling — you checking the inbox — you flip it to push. The inbox tells you the instant something happens. The workflow does three things in sequence, all without a human touching a screen:

1. Detects a new inbound email that is a reply to one of your sequences.
2. Creates a Pipedrive activity/task tied to the right deal or person, so the follow-up has an owner and a due time.
3. Sends a Slack alert to the rep or channel with the sender, subject, and a snippet — so someone can act in seconds.

The whole thing runs in n8n, self-hosted or cloud, and touches only APIs you already pay for. No polling scripts, no Zapier task limits, no glue code to maintain.

Step-by-step: building it in n8n

Here's the node-by-node build. Five nodes, roughly ten minutes if your credentials are ready.

1. Gmail Trigger (or IMAP Email) node

Add a Gmail Trigger node as your entry point. Configure:

• Event: Message Received
• Poll Time: every minute (Gmail Trigger polls; for true instant delivery use the Gmail push/webhook via Google Pub/Sub, but a 1-minute poll keeps you comfortably inside the 60-second promise).
• Filters: set a label or query such as from:-yourdomain.com is:unread so you only fire on genuine inbound replies, not your own sent mail or newsletters.

If you're not on Gmail, swap in the IMAP Email node pointed at your mailbox with "Mark as read" enabled to avoid re-processing.

2. Filter / IF node — is this actually a reply?

Add an IF node to weed out noise. A reply typically carries a References or In-Reply-To header, or the subject starts with Re:. A clean condition:

• Boolean: {{ $json.subject.toLowerCase().startsWith('re:') }} is true, OR
• Check that the sender's domain matches a known prospect list, or that In-Reply-To is not empty.

This one node is the difference between a useful alert system and a spam machine that pings Slack every time you get a receipt.

3. Pipedrive node — create the task

Add a Pipedrive node. First, optionally add a Pipedrive → Person → Search operation using the sender's email so you attach the task to the right contact. Then set the main node to:

• Resource: Activity
• Operation: Create
• Subject: Reply from {{ $json.from.value[0].address }} — respond now
• Type: call or email
• Due Date: {{ $now.toFormat('yyyy-MM-dd') }} with a due time ~15 minutes out
• Person ID / Deal ID: map from the Search node output so it lands on the actual deal.
• Note: paste the email snippet {{ $json.textPlain.slice(0,300) }} so the rep has context without opening the inbox.

4. Slack node — fire the alert

Add a Slack node:

• Resource: Message → Operation: Send
• Channel: #replies or DM the sequence owner
• Message: use Block Kit for scannability: 🔥 *New reply* from *{{ $json.from.value[0].address }}*\n*Subject:* {{ $json.subject }}\n> {{ $json.textPlain.slice(0,200) }}\nic

Add a button block linking straight to the Pipedrive activity or the Gmail thread so the rep is one click from replying.

5. Connect and activate

Wire it up: Gmail Trigger → IF → (true) Pipedrive Search → Pipedrive Create → Slack. Toggle the workflow to Active. Send yourself a test reply and watch the task and the ping appear. Done.

The benefits: what changes the day you turn it on

• Speed-to-lead collapses. Reply → alert → action happens inside a minute, not hours. You catch prospects while intent is hot.
• Nothing falls through. Every reply becomes a CRM task with an owner and a due time. "I forgot to follow up" stops being a sentence anyone says.
• Attention is freed. Your reps stop compulsively refreshing Gmail and get their focus back — the system watches so they don't have to.
• It scales linearly. One sequence or fifty, one rep or ten — the workflow doesn't care. Add channels and mailboxes without adding headcount.
• Full visibility. The Slack channel becomes a live feed of pipeline momentum that the whole team can see.

Common pitfalls (and how to avoid them)

• Alerting on your own sent mail. Without a sender filter, the workflow fires when you reply too. Always exclude your own domain in the Gmail query.
• Duplicate tasks from re-polling. If you don't mark messages read (IMAP) or scope the label correctly (Gmail), the same reply triggers repeatedly. Use "Mark as read" or a processed-label move as the last step.
• Out-of-office and auto-replies. Bounces and OOO messages look like replies. Add a condition in the IF node to drop subjects containing out of office, automatic reply, or delivery failed.
• Orphaned tasks. If the Pipedrive Person search returns nothing, the activity has no owner. Add a fallback branch that still creates the task and tags it "unmatched — assign manually."
• Rate limits and credential expiry. Gmail and Pipedrive OAuth tokens expire. Add an Error Trigger workflow that pings Slack if the main flow fails, so a silent auth break doesn't cost you a week of replies.
• Over-notifying. If volume is high, batch or route by rep instead of blasting one channel — alert fatigue kills the very responsiveness you built this for.

Build it once and it runs forever. The 60-second reply loop isn't a nice-to-have — it's the difference between a sequence that books meetings and one that generates polite "sorry, we went with someone else" emails three days too late.

PRONTO PARA USAR

Ja construimos isso pra voce

Nao comece do zero. O Cold Email Reply → Pipedrive Task + Slack Alert in 60 Seconds e um workflow n8n pronto para instalar — conecta suas ferramentas em minutos, sem codigo.

Instalar por $29 →