MARKETING

Pre-Send Deliverability Gate: Block Risky Campaign Launches by Domain

When a campaign is about to launch it checks each target domain's recent bounce and complaint history, holds the send for any domain currently in a risky state.

CategoryMarketing
Enginesim
Difficultybeginner
Triggerwebhook
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCampaign-launch webhook receivedHTTP webhook
  • ActionLook up recent risk status per domainPostgreSQLPostgres
  • LogicSplit safe-to-send vs held domains
  • ActionHold risky domains, release safe segmentPostgreSQLPostgres
  • OutputEmail owner the held-domain reportGmailGmail

What it does

This is a preventive gate that runs at the moment a campaign is queued for launch. For every recipient domain in the target audience, it looks up the recent bounce and complaint history and decides whether that domain is currently safe to mail. Domains in a risky or paused state are held back from the send, while the rest proceed normally. The campaign owner gets an email listing precisely which domains were held, the reason, and the safe send volume that went out.

When to use it

Use this when you want deliverability protection before damage happens rather than after. Instead of detecting a spike post-send, it stops you from mailing into a domain you already know is compromised, while still letting the healthy majority of the audience receive the campaign.

How it works

  1. 1A campaign-launch webhook fires with the target audience.
  2. 2Postgres returns recent bounce and complaint status for each recipient domain.
  3. 3A logic step splits domains into safe-to-send and held.
  4. 4Postgres records held domains and releases the safe segment for sending.
  5. 5Gmail emails the campaign owner the held-domain report and safe volume.

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 GmailRead, draft, send, label.
  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.