Weekly Lemlist Campaign Digest in Slack | Outbound Performance Report

Build me an agent workflow that posts a weekly Lemlist performance digest to Slack.

Trigger: cron, every Monday at 9:00am America/New_York.

On each run, the agent should do the following:

1. Call Lemlist List Campaigns filtered to status=running to get the full set of active campaigns. Page through results until exhausted. Also separately note any campaign whose status is errors so it can be called out at the end of the digest as needing operator attention.

2. For each running campaign, call Lemlist Get Campaign Stats twice: once for the last 7 days (the just-completed week) and once for the prior 7 days. Use these two windows to compute week-over-week deltas for contacted volume, open rate, reply rate, bounce rate, and interested-lead count. Pace requests to respect Lemlist's 20 requests per 2 seconds rate limit; if there are many campaigns, sleep between batches and back off on any 429.

3. Synthesize a written digest. Rank campaigns by reply rate over the last 7 days. Call out the top two performers and the bottom two laggards by name with their key numbers. Flag any campaign whose bounce rate is above 4% or whose reply rate dropped more than 30% week over week as a deliverability risk. List any campaign in errors status separately under an Action Needed section. End with one or two concrete, specific recommendations (pause a particular campaign, duplicate a winner, refresh the copy on a specific underperformer).

4. Post the digest to the #outbound-weekly Slack channel using Slack Bot Send a Message. Format it using Slack mrkdwn with clear section headers (Top Performers, Laggards, Deliverability Risk, Action Needed, Recommendations) and a compact metrics table showing campaign name, contacted, open rate, reply rate, bounce rate, interested count, and the week-over-week delta for reply rate. Keep the message scannable in under 30 seconds.

Notes for the agent: Use the slackbot integration (bot identity) for posting, not the user OAuth Slack integration. The bot must be a member of #outbound-weekly, or chat:write.public must be granted. If there are zero running campaigns, post a short message saying so instead of skipping the run silently.

Additional information

What does this prompt do?

Pulls every running outbound campaign from Lemlist and compares last week to the week before across contacted volume, open rate, reply rate, bounce rate, and interested count.
Ranks campaigns by reply rate and calls out the two top performers and the two laggards so your team knows where to lean in.
Flags deliverability risk when bounce rate climbs above 4 percent or reply rate drops more than 30 percent week over week, plus any campaign sitting in an error state that needs operator attention.
Posts the whole digest to your outbound Slack channel as a readable summary with section headers, a compact metrics table, and one or two concrete recommendations such as pause, duplicate, or refresh the copy.

What do I need to use this?

A Lemlist account with at least one running outbound campaign.
A Slack workspace and the channel where you want the weekly digest posted, for example #outbound-weekly.
About five minutes to connect both accounts the first time you run the prompt.

How can I customize it?

Change the schedule. Many teams prefer Friday afternoon or a daily check-in instead of Monday 9am ET.
Swap the Slack channel, send the digest as a direct message, or post it into a thread under a recurring anchor message.
Tune the alert thresholds. Lower the bounce rate trip wire to 2 percent if your team is sensitive, or relax the week-over-week reply rate drop to 50 percent for noisier programs.
Adjust what gets ranked or hidden. You can limit the digest to a specific campaign tag, ignore campaigns under a certain send volume, or include paused campaigns alongside running ones.

Frequently asked questions

How is this different from the reports inside Lemlist?

Lemlist shows you raw numbers per campaign. This digest does the work of comparing weeks, ranking the portfolio, and telling you which campaigns are worth acting on, then drops the answer in Slack so your team sees it without logging in.

What if I have a lot of running campaigns?

The digest covers every campaign in running status. Lemlist limits how quickly we can pull data, so the agent paces itself. Expect the message to land within a couple of minutes even with dozens of campaigns.

Can I send it to multiple Slack channels or to a private channel?

Yes. Tell the agent which channels to post in. For a private channel, just invite the General Input bot to that channel first so it has permission to post.

Will the digest miss campaigns that just launched?

Brand new campaigns may not have a full prior week of data yet. The agent will still include them and note that week over week comparisons are not meaningful until enough send history exists.

Can I tweak the recommendations the agent makes?

Yes. You can tell the agent to be more conservative, to never suggest pausing a campaign automatically, or to focus its advice on copy refresh and audience changes only.