Automated Fivetran Schema Change Review
Every morning, WebRun opens Fivetran, walks each connector's schema, compares the tables and columns against the record from yesterday, writes every addition or change into a Google Sheet with its connector and destination, and texts you when something new is heading for a modelled table.
How do I review Fivetran schema changes before they reach the warehouse?
WebRun opens Fivetran every morning, walks each connector's schema, and compares the tables and columns against yesterday's record. It writes every new or changed column into a Google Sheet with its connector and destination, and texts you through Twilio when a change touches a modelled table, so nothing lands downstream unnoticed.
- Every new column is seen before it reaches a dashboard
- A dated change log builds up per connector and destination
- Changes touching modelled tables reach a human the same morning
Built for analytics engineers · data teams · data platform owners · BI developers
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
fivetran.comin a real browser with your saved login - no setup, no API keys. -
1
Fivetran - read each connector schema
WebRun opens Fivetran to read each connector schema. - Open Fivetran and go through the connectors on your watchlist
- Read the schema for each: the tables it syncs and the columns inside them
- Note the destination each connector writes to
- Compare against yesterday's record and pick out new tables, new columns, and anything newly blocked or unblocked
- Read only. Never block, unblock, resync, pause, or reconfigure a connector
Done when Every connector's schema has been compared against yesterday's record.
-
2
Google Sheets - log the schema changes
WebRun opens Google Sheets to log the schema changes. - Append one row per change with the date, connector, destination, table, column, and change type
- Keep a second tab holding today's full schema so tomorrow has something to compare against
- Mark changes that touch a table your models already read
- Leave a review column for your team to mark each change accepted or blocked
Done when The sheet holds today's changes and a fresh snapshot for tomorrow.
-
3
Twilio - text the changes worth reviewing
WebRun opens Twilio to text the changes worth reviewing. - Text your own saved number when a change touches a modelled table or a new table appears
- Give the connector, the table, and what changed in one line
- Stay quiet on a morning with no changes
- Send to your own team numbers only. Never text outside the company
Done when Any change worth a human decision has reached you before the day starts.
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 block a column or change a connector?
No. WebRun reads schemas and logs what changed. Blocking a column, pausing a connector, or triggering a resync is always done by your team in Fivetran after reading the log.
How does it know what changed overnight?
It keeps yesterday's full schema in a tab of the same Google Sheet and compares today's against it, so every new table, new column, and blocking change is listed with the connector it came from.
When does it text me?
Only when a change touches a table your models already read, or when a brand new table appears. Routine changes land quietly in the sheet so the text keeps meaning something.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.