Monday morning Lemlist performance digest in Slack

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.