MARKETING

Auto-pause sends when bounce rate spikes

Listens for your ESP's bounce webhook, computes a rolling bounce rate from your send log.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerESP posts a bounce eventHTTP webhook
  • ActionLog bounce and read rolling send/bounce countsPostgreSQLPostgres
  • LogicBounce rate over the hard threshold?
  • ActionCall ESP API to pause the campaignHTTP webhook
  • OutputPost red alert to SlackSlack

What it does

It catches every bounce event your email provider fires, recalculates the bounce rate for the campaign over a rolling window, and pulls the emergency brake the moment that rate crosses a danger line. No more discovering a blacklisting hours after the damage is done.

When to use it

Run this on any high-volume campaign where a bad list segment or a typo'd domain can torch your sender reputation in minutes. It's the safety net for batch sends, drip sequences, and re-engagement blasts.

How it works

  1. 1Your ESP posts a bounce event to the webhook as each message hard-bounces.
  2. 2The flow writes the event to Postgres and reads back the send count and bounce count for that campaign in the last 60 minutes.
  3. 3It computes the rolling bounce rate and compares it to your configured ceiling (default 5%).
  4. 4If the rate is under the ceiling, it stops. If over, it calls the ESP API to pause the campaign immediately.
  5. 5It posts a red alert to Slack naming the campaign, the rate, and the bounce sample so an operator can investigate.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.