Auto-pause Instantly campaigns when bounce rates spike

Every two hours during business hours, check bounce rates and sender health, pause risky campaigns, and post one Slack alert that says what to do next.

Agentic Task
InstantlySlack BotOperationsSalesNotifications & AlertsResearch & Monitoring

Build an agent workflow that protects my Instantly sending reputation by auto-pausing campaigns that are putting deliverability at risk and alerting me in Slack when it does.

Trigger: a cron schedule that fires every 2 hours during business hours (default Monday through Friday, 8am to 6pm in my local timezone). Make the schedule and timezone easy to change at setup.

Each run, the agent should do the following:

1. Call Instantly List Campaigns filtered to status active (status code 1) to get the campaigns currently sending.

2. For each active campaign, call Instantly Get Campaign Analytics scoped to the trailing 24 hours and compute the bounce rate (bounced divided by emails sent).

3. Call Instantly List Email Accounts once per run and flag every sender mailbox whose status is error, suspended, warmup issue, or otherwise unhealthy (anything that is not a normal healthy/active state).

4. For each campaign, decide whether to pause it. Pause when EITHER condition is true:

- 24-hour bounce rate is at or above the configured threshold (default 5 percent, make this configurable).

- A majority of the campaign's assigned sender accounts are in an unhealthy state.

5. If the campaign meets the pause condition, call Instantly Pause Campaign for that campaign.

6. Then post ONE Slack message per paused campaign using Slack Bot Send a Message to a configurable channel (default #deliverability-alerts). The message should include:

- Campaign name and a link to it in Instantly.

- Current 24-hour bounce rate and the threshold it crossed.

- The specific sender mailboxes that are unhealthy and their statuses.

- A short diagnosis of the likely cause: warmup gap (recently added or under-warmed senders), list quality (high invalid rate), or DNS/auth issue (SPF/DKIM/DMARC) based on what the data shows.

- A recommended remediation, for example pause and re-warm the affected senders, scrub the list with a verifier, or fix the DNS records before resuming.

- A clear note that the campaign has already been paused so nobody scrambles.

If a campaign is healthy (below threshold and senders mostly fine), do NOT post anything. The Slack channel must stay silent unless something is actually wrong, so the alert keeps its signal.

Configuration the user should be able to set at install time: bounce rate threshold (default 5 percent), what fraction of unhealthy senders counts as a majority (default more than half), the cron schedule and business-hours window, the Slack channel for alerts, and an optional allowlist of campaign IDs that should only trigger an alert and never be auto-paused.

Use the Instantly integration for List Campaigns, Get Campaign Analytics, List Email Accounts, and Pause Campaign. Use the Slack Bot integration for Send a Message.

Additional information

What does this prompt do?
  • Watches your active Instantly campaigns every two hours during business hours and reads the last 24 hours of performance.
  • Pauses any campaign whose bounce rate crosses a safety threshold or whose sending mailboxes are mostly in an unhealthy state.
  • Posts a focused Slack alert that names the campaign, the bounce rate, the bad sender accounts, the likely cause, and the recommended fix.
  • Stays silent when everything looks healthy, so the channel only fires when something is actually wrong.
What do I need to use this?
  • An Instantly account on the Growth plan or higher, with an API key generated from Settings, Integrations, API.
  • A Slack workspace and the channel you want deliverability alerts to go to.
  • A bounce-rate threshold you are comfortable with. The default is 5 percent, but you can change it.
How can I customize it?
  • Change the bounce-rate threshold or how strict the sender-health check is before the agent will pause a campaign.
  • Adjust the schedule, for example every hour during a launch week or only weekdays from 9 to 6.
  • Send alerts to a different Slack channel, or DM the person on call instead of posting publicly.
  • Keep an allowlist of high-priority campaigns the agent should always alert on but never auto-pause.

Frequently asked questions

Will this pause my campaigns without asking me first?
Yes, that is the point. The agent only pauses a campaign when the 24-hour bounce rate crosses your threshold or when a majority of the campaign's sending mailboxes are in an unhealthy state. Healthy campaigns are never touched. You can also keep an allowlist of campaigns that should only alert, never auto-pause.
What counts as an unhealthy sender?
Instantly marks sending mailboxes with a status when something is wrong, for example error, suspended, or warmup problems. The agent flags any sender in one of those states and pauses the campaign when most of its assigned senders are unhealthy at the same time.
How often does it run?
Every two hours during business hours by default. You can change the cadence or the window when you set the workflow up. Outside business hours it stays quiet.
Will I get pinged about every campaign every two hours?
No. The agent only posts to Slack when it actually pauses a campaign or finds a deliverability risk that needs a human. If everything is healthy, the channel stays silent.
What does the Slack alert actually say?
It names the campaign, the current bounce rate, the specific sender accounts that look bad, a short diagnosis of the likely cause, for example a warmup gap, a bad list, or a DNS issue, and a recommended next step to fix it.

Stop letting bounce rates burn your sending domain.

Connect Instantly and Slack once, and the agent watches deliverability for you every two hours during business hours.