MARKETING

Daily blocklist check for sending IPs

Each morning checks your sending IPs and domains against public blocklists via an HTTP reputation API, and if any are listed.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule fires
  • ActionRead active sending IPs and domainsPostgreSQLPostgres
  • ActionQuery blocklist reputation API per IP/domainHTTP webhook
  • LogicAny IP or domain listed?
  • ActionOpen a Linear ticket per listingLinearLinear
  • OutputPost listing summary to Microsoft TeamsMicrosoft Teams

What it does

It runs a daily reputation sweep of every IP and domain you send from, querying public DNSBL/blocklist services through an HTTP API. When a listing turns up, it creates a tracked remediation ticket and alerts the deliverability channel with the exact blocklist and reason.

When to use it

Run it as your morning deliverability standup automation. Listings often happen silently overnight after a spam trap hit or a shared-IP neighbor's mistake; this catches them before the day's sends compound the problem.

How it works

  1. 1A daily schedule fires before the send window opens.
  2. 2The flow reads your active sending IPs and domains from Postgres.
  3. 3For each, it calls the reputation/blocklist HTTP API and collects any active listings.
  4. 4If the list is empty, it ends clean. If anything is listed, it opens a Linear issue per listing with the blocklist name and delisting link.
  5. 5It posts a summary card to Microsoft Teams so the team sees what's listed and who owns the fix.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect HTTP webhookTrigger any URL on agent actions.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  4. 4
    Connect Microsoft TeamsChannels, chats, files.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.