All templates

Automated Mailgun Suppression List Reconciliation

Every Monday, WebRun opens Mailgun, pulls the week's bounce, complaint, and unsubscribe events across your sending domains, reconciles them into a master suppression list archived in Google Drive, and posts a Slack summary of new suppressions and any domain issues.

Runs on WebRun · Strict Lockdown policy
Every Monday at 8:00 AM WebRunorchestrates each step
1 Mailgun pull bounce and complaint events
2 Google Drive archive the master suppression list
3 Slack summarize what changed
In short

How do I keep a Mailgun suppression list reconciled and current?

WebRun pulls your Mailgun bounce, complaint, and unsubscribe events every Monday, reconciles them into one master suppression list archived in Google Drive, and posts a Slack summary of what changed. That keeps every sending domain's suppression record current and gives the team an early flag on any domain with a rising bounce rate.

  • The suppression list stays current without anyone exporting CSVs by hand
  • A rising bounce rate on any sending domain gets flagged the same week
  • Every suppression event is archived with a date, not lost in the Mailgun dashboard

Built for developers · email infrastructure teams · marketing ops · SaaS platforms

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.mailgun.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Mailgun - pull bounce and complaint events
    mailgun.com
    WebRun in Mailgun: pull bounce and complaint events
    WebRun opens Mailgun to pull bounce and complaint events.
    • Open Mailgun and pull this week's bounces, complaints, and unsubscribes across sending domains
    • Note which domain and address list each event belongs to
    • Check each sending domain's delivery stats for anything unusual

    Done when Every suppression event from the week has been pulled with its domain.

  3. 2
    Google Drive - archive the master suppression list
    drive.google.com
    WebRun in Google Drive: archive the master suppression list
    WebRun opens Google Drive to archive the master suppression list.
    • Open the master suppression file in Google Drive
    • Add this week's new bounces, complaints, and unsubscribes without duplicating existing entries
    • Archive a dated copy so history is never lost

    Done when The master suppression list in Drive reflects every event from the week.

  4. 3
    Slack - summarize what changed
    slack.com
    WebRun in Slack: summarize what changed
    WebRun opens Slack to summarize what changed.
    • Post a summary of how many addresses were newly suppressed this week
    • Flag any sending domain whose bounce rate looks off
    • Link to the updated file in Drive

    Done when The team has this week's suppression summary in Slack.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.mailgun.com
ScheduleRuns automatically on this cadence
Every Monday at 8:00 AM
DeliveryHow each run's result reaches you
Suppression summary · Slack
OutputWhat each run produces - A reconciled suppression list with this week's new bounces, complaints, and unsubscribes, plus a change summary.
Report
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does it send any email or change my sending domains?

No. WebRun only reads events and updates the suppression file it maintains in Drive. It never sends mail or edits your Mailgun domain settings.

How does it avoid double-counting the same bounce?

It checks the existing master list before adding a row, so an address already recorded as suppressed is not logged twice.

What if a sending domain has a real deliverability problem?

It flags an unusual bounce rate in the Slack summary so someone can investigate, but the fix itself is left to your team.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.