Automated Brex Spend Policy Alerts
Every morning, WebRun opens Brex, reviews the last 24 hours of card transactions, flags any that break a spend policy or are missing a receipt after 48 hours, posts the list to Slack for finance, and pings Telegram immediately when a single transaction crosses your large transaction threshold.
How do I catch risky Brex spend before month end?
WebRun reviews your Brex card transactions every morning, flags any that break a spend policy or are missing a receipt after 48 hours, and posts the list to Slack for finance. Any single transaction over your large transaction threshold also triggers an immediate Telegram alert, so risky spend gets caught the same day.
- Policy breaking spend gets flagged the same morning, not at month end
- Large transactions trigger an immediate alert instead of waiting for a report
- Missing receipts are caught within 48 hours while they are easy to fix
Built for Finance teams · startup operators · controllers · bookkeepers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
dashboard.brex.comin a real browser with your saved login - no setup, no API keys. -
1
Brex - flag policy breaks and missing receipts
- Open Brex and filter transactions to the last 24 hours
- Flag any transaction over its category limit or missing a receipt after 48 hours
- Note the cardholder, amount, and reason for each flag
Done when Every transaction from the last 24 hours has been checked against policy.
-
2
Slack - post the daily spend digest
slack.com
WebRun opens Slack to post the daily spend digest. - Post the flagged transactions to the finance channel
- Group them by cardholder with the amount and reason
- Leave already cleared transactions out of the list
Done when Finance has today's flagged spend in Slack.
-
3
Telegram - alert on large transactions
telegram.org
WebRun opens Telegram to alert on large transactions. - Send an immediate alert for any single transaction over your large transaction threshold
- Include the cardholder, amount, and merchant
- Skip transactions already covered in the Slack digest
Done when Any large transaction has been flagged in Telegram the same day.
How is each run configured?
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.
Every action is checked against this policy before it runs.
Questions, answered
Does it freeze or block the card?
No. WebRun only reads transaction data and flags what looks off. Freezing a card or changing a limit stays a decision for your finance team inside Brex.
How does it decide what counts as risky?
It checks each transaction against the category limit and receipt rule you set, so the flags match your own policy instead of a generic one.
Will it contact the cardholder directly?
No. It only posts to your internal Slack and Telegram channels. Nobody outside your team hears from WebRun.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.