How do LinkedIn reply notifications work?

What this is

WarmySender's reply notification feature pushes a "reply received on LinkedIn" event to any external system you've subscribed to receive it. The notification carries the basics — which connected LinkedIn account received the message, the prospect's name and profile URL (when we can identify them), and a timestamp — so your downstream automation can act on it: a Slack alert in your sales channel, a new task in your CRM, a Zapier flow that updates a Google Sheet, an n8n workflow that pings the right rep, and so on. WarmySender is a 4-pillar outreach platform — Cold Emailing, Email Warmup, LinkedIn Outreach, and Multichannel sequences — and this notification is part of the LinkedIn Outreach pillar.

When you receive a notification

You receive a LinkedIn reply notification for every inbound LinkedIn direct message on a connected LinkedIn account. That includes two kinds of inbound message:

• Replies to messages you sent through WarmySender. Someone you've been outreaching to through a LinkedIn campaign replies to one of your messages. This is the most common case and the one most customers set up notifications for in the first place.
• First-time inbound DMs from people you haven't messaged. Someone you've never written to through WarmySender opens a fresh conversation with you on LinkedIn — a cold inbound from a prospect who found your profile, a peer reaching out, a recruiter pitching a role. These produce a notification on the same connected account.

The notification fires whether or not WarmySender can tie the inbound message back to a known prospect in your campaigns. If we can identify the sender as a prospect on one of your campaigns, the notification includes that context; if we can't (because the inbound is from someone outside your campaigns), the notification still fires with the sender's profile information so your downstream system can decide what to do with it.

Notification deduplication

A single conversation thread produces one notification per reply event, not one notification per message. If a prospect sends you three messages back-to-back — for example a quick "hi" followed by a longer reply followed by an attachment — your Slack channel doesn't light up with three separate alerts seconds apart. WarmySender groups the activity at the conversation level and notifies your external system based on the conversation's reply events, not the raw message count.

This matters in practice for two reasons. First, it keeps your Slack / Zapier / CRM channels readable — a chatty prospect doesn't drown out your other notifications. Second, it makes downstream automation (like a Zapier flow that creates a CRM task) idempotent at the conversation level — your CRM won't end up with three tasks for what is really one inbound conversation event.

If you specifically need per-message granularity for an unusual integration, open the unified Inbox in WarmySender — every individual inbound message is visible there in chronological order. The notification feed is intentionally conversation-grouped because that matches how the vast majority of customers actually want to use it.

How to set up an external receiver

Open Settings → Webhooks in WarmySender, click Add webhook, paste the receiving URL from your external system (a Slack incoming webhook URL, a Zapier catch-hook URL, your CRM's webhook endpoint, etc.), and tick the LinkedIn reply received event in the list. Save, then click Send test event on the row to verify your external system received and processed the test payload. The receiving URL needs to accept a JSON POST request and respond with a success status; every modern automation platform (Slack, Zapier, Make, n8n, HubSpot, Pipedrive, Salesforce) handles this out of the box.

You can have multiple receivers subscribed to the same event — for example one for your Slack channel and a separate one for your CRM — and each receives its own copy of the notification. There's no extra cost for additional receivers; the limit is your own external system's rate limits, not ours.

For the wider REST API surface (creating webhooks programmatically, listing subscriptions, rotating secrets), see the API and webhook integration guide. The Settings → Webhooks UI is the easier path for most customers; the API is there if you need to manage webhooks from your own automation.

"I didn't get a notification I expected"

Four common reasons a notification you expected didn't arrive. Walk through them in order; the first one resolves most cases.

1. No external receiver is subscribed to the LinkedIn reply event. Open Settings → Webhooks and check each row's event list. If none of your receivers have LinkedIn reply received ticked, no external system is being notified — the event is firing on our side, but there's nothing listening for it. Add the event to an existing receiver or create a new one for the integration you want to wire up.
2. Your external system rejected the delivery. WarmySender records every delivery attempt and the response your external system returned. Open Settings → Webhooks, click into the receiver row, and review the recent delivery log. If you see rejection responses, the issue is on the external side — usually the receiving URL has changed, the integration was deleted, or the external system is rate-limiting. Update the URL or fix the rate-limit issue, then send a test event to confirm the path is healthy again.
3. The reply was on a conversation that was already active. Per the deduplication section above, you receive one notification per reply event on a conversation, not one per message. If the prospect already pinged you minutes ago, a follow-up message in the same thread within the same activity window is intentionally not a second notification — it's the same conversation event. Check the unified Inbox if you want to see every individual message.
4. The connected LinkedIn account is currently disconnected. If the LinkedIn account that should have received the reply is in a session-lapse state, WarmySender can't observe new inbound activity on it until you reconnect. Open the LinkedIn accounts page and look for a Reconnect badge on the affected account. See Why am I getting reconnect emails from WarmySender? for the full reconnect flow. Once reconnected, future inbound replies notify normally.

If none of those four match what you're seeing, email [email protected] with the connected LinkedIn account's name, the approximate time of the inbound reply, and the receiver you expected to fire — we'll trace the specific event.

People also ask

Common adjacent questions about LinkedIn reply notifications.

Does this work for inbound messages from people I haven't messaged through a campaign?

Yes. Every inbound LinkedIn direct message on a connected account produces a notification, whether or not we can tie the sender back to a prospect in one of your WarmySender campaigns. A cold inbound DM from someone who found your profile, a peer reaching out, a recruiter pitching a role — all of these notify the same way as a reply to one of your campaign messages. The notification payload includes the sender's profile information either way, so your downstream system can decide how to handle each one.

How quickly after a reply does the notification fire?

Within seconds in the typical case. WarmySender's reply detection picks up new inbound activity on each connected LinkedIn account on a continuous basis, then dispatches the notification to every subscribed external receiver as soon as the activity is observed. End-to-end (prospect hits Send on LinkedIn → your Slack channel pings) is usually well under a minute, with most events landing in under 15 seconds. If you're consistently seeing delays of several minutes, that's a sign something upstream is throttled — open Settings → Webhooks to check the receiver's recent delivery log.

What does the notification payload contain?

A compact JSON payload with the basics: an event type identifying it as a LinkedIn reply, the connected LinkedIn account that received the inbound message, the prospect's name and profile URL when we can identify them, a timestamp, and an event identifier you can use to correlate or dedupe on your side. Send a test event from Settings → Webhooks to see the exact field structure before wiring up your downstream automation — that's the canonical reference and what your automation will actually receive in production.

Will I get a notification if I reply to the prospect myself from LinkedIn directly?

No. Notifications are scoped to inbound activity — messages someone else sends to you. Outbound messages you send (whether through WarmySender's campaigns, through the WarmySender unified Inbox, or directly from LinkedIn's own web interface) don't produce inbound-reply notifications. This is intentional: outbound activity is something you initiated, so there's no "alert me" use case for it.

Does this same notification feature exist for cold email replies?

Yes. WarmySender's webhook feature supports event types for replies on the cold email side too, alongside the LinkedIn reply event covered on this page. Open Settings → Webhooks, click Add webhook (or edit an existing receiver), and tick the email-side reply events in the same list. The same external receivers (Slack, Zapier, your CRM) can subscribe to both LinkedIn and email events on a single webhook configuration, so your Slack channel can be one unified "someone replied" signal across both channels of a multichannel campaign.