Use cases → Reporting and data
Reconcile records between two systems automatically
Compare what your tracking sheet says against what the source system says, and report the differences.
| Who it is for | Anyone maintaining a spreadsheet alongside a real system of record. |
|---|---|
| APIs | Sheets API, Gmail API |
| Typical scopes | spreadsheets, gmail.readonly |
The problem
Two records of the same truth always drift. The drift is discovered during an audit, a dispute, or a month-end that will not balance.
How it works
- Pull both sides on a schedule.
- Match on a stable key and compare the fields that matter.
- Report only mismatches, with enough context to resolve each one.
What changes
Drift is caught within a day instead of a quarter.
Questions people ask
What if the key is unreliable?
Then fixing the key is the project. Fuzzy matching on names produces confident, wrong reconciliations.
Want this built?
This is a pattern we run in production. We will set up the delegation and build this on top of it — $500 per hour, most of it working the same day.
Talk to us Or read the setup guideRelated use cases
Send a daily digest that catches problems early
One scheduled email that checks the things that fail quietly and reports only what changed.
Work out which sources actually produce customers
Join enquiry records to outcomes so spend goes where the revenue is.
Run automation from a spreadsheet non-engineers can edit
Keep rules, templates and routing in a Sheet so the operations team changes behaviour without a deploy.