MARKETING

Pre-send list quality gate

Before a campaign launches, a webhook triggers a check of the recipient list's historical bounce and complaint rates from Postgres.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerPre-send check posts to the webhookHTTP webhook
  • ActionQuery list's historical bounce/complaint/engagementPostgreSQLPostgres
  • LogicComposite quality score below the bar?
  • ActionReturn approve or block response to send toolHTTP webhook
  • OutputOn block, flag risky segments in SlackSlack

What it does

It intercepts a campaign at launch time and inspects the recipient list's track record before a single message goes out. It scores the list on historical hard-bounce rate, prior complaint rate, and share of stale or never-engaged addresses, then approves or blocks the send.

When to use it

Use it as a mandatory gate in front of every send so bad lists never reach the ESP. Especially valuable for reactivated or imported segments where the failure mode is a reputation hit you can't undo.

How it works

  1. 1Your send tool posts a pre-send check to the webhook with the campaign and list ID.
  2. 2The flow queries Postgres for the list's historical bounce rate, complaint rate, and engagement recency.
  3. 3It computes a composite quality score against your minimum bar.
  4. 4If the list passes, it returns an approve response so the send proceeds. If it fails, it returns a block response to halt the launch.
  5. 5On a block, it posts the failing metrics and the worst segments to Slack so marketing can scrub the list before retrying.

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.