All templates
For Data teams, content operations teams & backend engineers

Catch Directus and Airtable records falling out of sync

Every night, WebRun opens Directus, compares each collection's record count against the corresponding Airtable tracker, and emails the team whenever the two disagree, so a sync job that silently failed or a record entered in the wrong place gets caught the next morning.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every night at 11:30 PM WebRun
1 Directus check Directus record counts
2 Gmail compare against Airtable
3 Airtable email the mismatch report
Run a sample
In short

How do I catch Directus and Airtable data falling out of sync?

WebRun compares Directus collection record counts against a tracking Airtable base every night, and emails the team only when a mismatch turns up, naming the collection and both counts. This catches a sync job that silently failed or a record added in the wrong place the next morning, instead of weeks later when the data has drifted further.

  • A sync failure gets caught the next morning instead of weeks later
  • The team only hears from it when something is actually wrong
  • Both systems stay trustworthy because they are checked every night

Built for Data teams · content operations teams · backend engineers · no-code and low-code teams

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens directus.cloud in a real browser with your saved login - no setup, no API keys.

  2. 1
    Directus - check Directus record counts
    directus.io
    WebRun in Directus: check Directus record counts
    WebRun opens Directus to check Directus record counts.
    • Open Directus and review the record count for each tracked collection
    • Note the count and the last updated timestamp per collection
    • Record the totals for comparison

    Done when Every tracked collection's current record count is recorded.

  3. 2
    Gmail - compare against Airtable
    gmail.com How to Automate Gmail
    WebRun in Gmail: email the mismatch report
    WebRun opens Gmail to email the mismatch report.
    • Draft and send an email to the team only when a mismatch is found
    • List the affected collection, the Directus count, and the Airtable count
    • Skip sending if every collection matches

    Done when The team has been emailed about any Directus and Airtable mismatch found tonight.

  4. 3
    Airtable - email the mismatch report
    airtable.com How to Automate Airtable
    WebRun in Airtable: compare against Airtable
    WebRun opens Airtable to compare against Airtable.
    • Open the Directus Sync Tracker base
    • Compare each collection's Directus count against the count already logged in Airtable
    • Flag any collection where the counts do not match

    Done when Every mismatch between Directus and the Airtable tracker is identified.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
directus.cloud
ScheduleRuns automatically on this cadence
Every night at 11:30 PM
DeliveryHow each run's result reaches you
Reconciliation alert · Gmail
OutputWhat each run produces - A nightly comparison of Directus and Airtable record counts, with an email sent only when a mismatch is found.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will WebRun fix the mismatch or add missing records?

No. It only compares counts and reports a difference. Investigating and correcting the mismatch stays with your team.

Does it email every night even when nothing is wrong?

No. The email only goes out when a mismatch is actually found, so a clean night stays quiet.

What causes a mismatch like this?

Usually a sync step that failed partway or a record added directly in one system without the other being updated. WebRun surfaces the difference; finding the exact cause is a team follow-up.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.