Automated Cloudflare Config Change Review
Every morning, WebRun opens the Cloudflare dashboard, reads the audit log for the last day, records every configuration and DNS record change with the account member behind it in Notion, and raises a Trello card for anything that looks unplanned.
How do I track who changed my Cloudflare DNS settings?
Every morning WebRun opens the Cloudflare dashboard, reads the audit log for the last day, and lists every configuration edit with the account member who made it. DNS record changes and proxy status flips are called out first in Notion, and anything unexpected becomes a Trello card, so an accidental edit is caught the morning after.
- An accidental DNS edit is caught the next morning, not when traffic drops
- Every change is logged with the member who made it
- Unplanned edits become a card someone has to confirm or undo
Built for infrastructure engineers · DevOps teams · web agencies · IT administrators
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
dash.cloudflare.comin a real browser with your saved login - no setup, no API keys. -
1
Cloudflare - read yesterday's audit log
cloudflare.com
WebRun opens Cloudflare to read yesterday's audit log. - Open the Cloudflare dashboard and read the audit log for the last 24 hours
- Capture the action, the zone, the account member, and the timestamp for each entry
- Pull the DNS record changes out separately, including proxy status flips
- Note any change to account members or their access
Done when Every logged change from the last day is captured with who made it.
-
2
Notion - record the daily change log
notion.so
WebRun opens Notion to record the daily change log. - Add today's entry to the change log page, grouped by zone
- Put DNS record edits and proxy status changes at the top
- Record the previous value beside the new one where the log shows it
- Keep the history so a change can be traced back weeks later
Done when Today's change log is written in Notion with DNS edits called out first.
-
3
Trello - raise cards for unplanned edits
trello.com
WebRun opens Trello to raise cards for unplanned edits. - Create a card for any change with no matching ticket or planned work
- Always card a DNS record deletion, a proxy status flip, or a new account member
- Name the zone, the member, and the timestamp on the card
- Never revert a setting. WebRun reports the change and leaves the fix to you
Done when Every unplanned change has a Trello card for someone to confirm or undo.
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
Can it change or revert a Cloudflare setting?
No. WebRun only reads the audit log and writes the change log. Reverting a DNS record or a proxy setting stays a human action in your own dashboard.
Which changes get a Trello card?
Any change with no matching ticket, plus every DNS record deletion, proxy status flip, and new account member, since those are the edits that break traffic quietly.
Does it cover more than one zone?
Yes. It walks every zone on the account and groups the log by zone, so a change on a rarely visited domain still shows up the next morning.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.