Automated Zapier Zap Inventory Export
Every night, WebRun opens Zapier, walks every folder, and records each Zap with its on or off status, its owner, and the app connections it depends on, texts your on-call number through Twilio when ownership or a connection changes, and posts the full register to Telegram.
How do I keep an inventory of every Zap and its owner?
Every night, WebRun opens Zapier and walks your whole account, recording each Zap with its folder, its on or off status, the owner it runs under, and every app connection it depends on. It posts the register to Telegram and texts you through Twilio when a Zap or a connection changes hands.
- Every automation has a named owner on record
- Broken or orphaned app connections surface the night they appear
- Changes since yesterday are listed at the top of every register
Built for ops leads · RevOps teams · IT administrators · automation owners
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
zapier.com/app/loginin a real browser with your saved login - no setup, no API keys. -
1
Zapier - inventory every Zap and connection
zapier.com
WebRun opens Zapier to inventory every Zap and connection. - Open Zapier and go through every folder in the account
- Record each Zap with its name, its folder, and whether it is on or off
- Note the account or user the Zap runs under, so every automation has a named owner
- Open each Zap and capture the app connections it depends on
- Flag any Zap whose connection is disconnected, expired, or owned by someone who has left
- Compare against last night's register and mark what was added, paused, or reassigned
Done when Every Zap is recorded with its status, owner, and app connections, with changes since last night marked.
-
2
Twilio - text you when ownership changes
twilio.com
WebRun opens Twilio to text you when ownership changes. - Send a short SMS from Twilio to your own on-call number when a Zap changes owner or loses a connection
- Name the Zap and what changed, nothing more
- Only your own registered numbers are texted. A message to any number outside that list is queued for your approval instead of sent
Done when Your on-call number has been texted about any ownership or connection change.
-
3
Telegram - post the nightly register
telegram.org
WebRun opens Telegram to post the nightly register. - Post the full register to your ops channel, grouped by folder
- Show each Zap with its status, owner, and connected apps
- List last night's changes in a short block at the top
- Call out Zaps that are off but never deleted, and connections with nobody attached
Done when Tonight's register is in Telegram with the day's changes at the top.
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
Will it turn Zaps on or off?
No. WebRun reads the account and reports. It never edits, pauses, or deletes a Zap, and it never reconnects an app account. Every change stays a human decision.
Who gets the Twilio text?
Only the on-call numbers you register at setup. Any SMS addressed to a number outside that list is queued for your approval rather than sent, so nothing goes to a customer or a colleague unannounced.
How does it spot an automation nobody owns?
It records the account each Zap runs under and the app connections behind it, then flags any connection that is disconnected, expired, or tied to a person who has left the workspace.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.