№ 031Developer toolsBuilt and tested
Zapier Run Monitor
Keeps a queryable history of Zapier runs beyond what Zapier retains.
A monitoring application for collecting and examining Zapier run history. Includes a PostgreSQL-backed implementation, tests, deployment packaging and an operator handoff; a running collector was not verified in this audit.
- Python
- PostgreSQL
- Zapier
- Monitoring
Screens coming
Screenshots for this project are being captured with sample data. The write-up below stands on its own.
The problem
Zapier's own run history is short, and it does not distinguish a delivery attempt from a final outcome.
Who it is for
An operator or small team whose delivery depends on Zaps.
What it does
01
Collects through the read-only CLI
02
Stores run history in PostgreSQL
03
Tells attempts from outcomes deterministically
04
Redacts lead and credential data before anything is shared
05
Ships with an install bundle and an operator runbook
How it works
Python 3.11 with psycopg, using the companion CLI as its only data source.
- Python
- PostgreSQL
- Zapier
- Role
- Built by Vas.
- Status
- Built and tested. Not running as a service.
Related
№ 032Public on GitHubSitecore Detector
A command-line website inspection tool that checks whether a site is built on Sitecore CMS.
- Node.js
- CLI
- HTTP inspection
- Sitecore
№ 030Public on GitHubZapier Read-Only CLI
A command-line tool for inspecting Zaps and failed runs. Includes browser-assisted authentication, agent integration and macOS and Windows installation tooling.
- Go
- CLI
- Zapier
- Browser authentication
Next project
Medical Clinic Fax AutomationFaxed referrals and lab results read by AI, checked by a person, then filed in the EMR.