The moment it happens

Get a Slack message when a lemlist lead replies

Each reply shows up in Slack with the lead's name, the campaign and the start of their message.

Runs: The moment it happens
Apps: lemlist
AI: Not needed
Access: API key

Send this to your assistant

Create a ClickRuntime automation: when someone replies to any of my lemlist campaigns, post their name, company, campaign name and the first few lines of the reply to #outbound in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Outbound sales runs on timing. A prospect who answers a lemlist sequence email at 2 p.m. is reading their inbox right now, and every hour that passes makes a reply feel stale. Yet the response lands in whichever inbox the campaign was sent from, often a shared mailbox or a sender account that the rep checks twice a day. Replies sit there, and the lead goes cold while the rep is on another call.

When a lead replies, lemlist notifies ClickRuntime, which posts a message to Slack with the lead's name, company, the campaign they answered and a snippet of what they wrote. Whoever owns the pipeline sees it moments after it happens, in a tool they keep open all day, and can jump straight into the conversation.

Founders doing their own outreach and small sales teams sharing several sender accounts benefit most.

What you get out of it

Fast answers win the meeting
A rep who responds within ten minutes of a reply is far more likely to land a call than one who answers the next morning. The Slack ping closes the gap between the prospect's interest and your response.
Replies are not trapped in sender inboxes
When several mailboxes send for one team, nobody can watch all of them. A single channel collects every reply in one place, so no response is missed because it arrived in an account no one opened.
The snippet helps decide who answers
Seeing the first lines of the reply tells the team whether it is a positive answer, a question about pricing or a polite no. They can route it to the right person without opening lemlist.
Campaign results become visible to everyone
A channel full of replies shows how a sequence is landing as it runs. Writers and sales leads can see which angle draws responses and talk about it the same day.
Reps stop refreshing mailboxes
Checking sender accounts all day is a nervous habit that interrupts focus. With the alert, a rep can concentrate on calls and trust that a reply will find them. Focus is worth more than a fast inbox refresh.

How it works

What happens, step by step

When a lead replies to one of your lemlist campaigns, lemlist tells ClickRuntime straight away.
ClickRuntime picks out the lead's name, company, the campaign and the first three lines of their reply.
It posts them to #outbound in Slack, so the team can read the reply without opening lemlist.

Before it runs live

Connect lemlist
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Get a Slack message when a lemlist lead repliesjust nowSucceeded

Slack · #outboundDana Reyes (Northwind) replied to Q4 Ops outreach > Thanks for reaching out, can we talk Thursday?

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other lemlist steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

lead_replied_alert.pyexample

from clickruntime import on_event, notify

@on_event
def handle(event):
    e = event.json or {}
    if e.get("type") != "emailsReplied":
        return {"posted": False}
    name = f"{e.get('leadFirstName', '')} {e.get('leadLastName', '')}".strip() or e.get("leadEmail")
    snippet = "\n".join((e.get("text") or "").strip().splitlines()[:3])
    notify.slack(
        f"{name} ({e.get('companyName') or 'unknown company'}) replied to {e.get('campaignName')}\n> {snippet}",
        channel="#outbound",
    )
    return {"posted": True}

FAQ

Common questions

Does it post automatic replies like out-of-office messages too?

It posts whatever lemlist reports as a reply, which can include auto-responders depending on how lemlist classifies them. If out-of-office messages clutter the channel, you can add a filter on the reply text or use the AI triage version, which sorts them out.

Which details of the lead appear in the Slack message?

The message includes the lead's name and email, company where lemlist has it, the campaign name and a snippet of the reply. If you store extra lead variables in lemlist, such as job title, those can be added to the post too.

Can replies from one campaign go to a different channel?

Yes. The campaign name is part of each event, so replies can be routed by campaign, for example one channel per client or per region. That helps agencies and larger teams keep the channels readable for each owner.

What permissions does it need?

API key. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run for each event the app sends.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

The moment it happens