All templates

Automated Braze Campaign Error Alerts

Every hour, WebRun checks Braze campaign analytics for pushes, emails, and in-app messages sent recently, and when a campaign's bounce or error rate crosses your set threshold, it logs an incident row to Airtable with the details and updates a Notion incident-log page so the growth team can investigate.

Runs on WebRun · Strict Lockdown policy
Every hour WebRunorchestrates each step
1 Braze check campaign delivery rates
2 Airtable log the incident
3 Notion update the incident page
In short

How do I catch Braze campaign delivery problems before they escalate?

WebRun checks your Braze campaign analytics every hour and, when a push, email, or in-app send's bounce or error rate crosses the threshold you set, logs the incident to Airtable with the campaign and rate, then updates a Notion incident log page, so delivery problems get caught and tracked before they affect more customers.

  • Delivery problems get logged within the hour instead of at the weekly review
  • Every incident has a paper trail in Airtable and Notion
  • No campaign issue goes unnoticed until customers complain

Built for growth teams · lifecycle marketers · mobile marketing teams · CRM managers

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 dashboard.braze.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Braze - check campaign delivery rates
    braze.com
    WebRun in Braze: check campaign delivery rates
    WebRun opens Braze to check campaign delivery rates.
    • Open Braze and review analytics for campaigns sent in the last hour
    • Compare each campaign's bounce and error rate to your set threshold
    • Capture the campaign name, channel, and rate for anything over threshold

    Done when Every campaign over threshold this hour has been identified.

  3. 2
    Airtable - log the incident
    airtable.com
    WebRun in Airtable: log the incident
    WebRun opens Airtable to log the incident.
    • Open the incident-tracking base in Airtable
    • Add a row with the campaign, channel, rate, and timestamp
    • Mark the incident as open for review

    Done when Every flagged campaign has an open incident row in Airtable.

  4. 3
    Notion - update the incident page
    notion.so
    WebRun in Notion: update the incident page
    WebRun opens Notion to update the incident page.
    • Open the incident-log page in Notion
    • Add a summary entry linking back to the Airtable row
    • Note the campaign and rate so the team can see it at a glance

    Done when The Notion incident log reflects every open incident.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
dashboard.braze.com
ScheduleRuns automatically on this cadence
Every hour
DeliveryHow each run's result reaches you
Incident log · Notion
OutputWhat each run produces - An incident record for any campaign whose bounce or error rate crosses your threshold.
Alert
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 pause or change my Braze campaigns?

No. WebRun only reads campaign analytics. It never pauses, edits, or resends a campaign, it just flags the numbers for a human to act on.

What counts as an error worth flagging?

Whatever bounce or error rate threshold you set. WebRun compares each campaign's live Braze numbers against it every hour and only logs the ones that cross it.

Where do incidents show up?

As a new row in your Airtable incident base and a matching entry on a Notion incident log page, so the growth team sees it in both places.

Put this on autopilot.

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