All templates
For data engineering teams, analytics engineers & data platform admins

Keep your Airbyte syncs healthy

Every morning, WebRun opens Airbyte, checks every connection's last sync status, posts a Teams summary of any failed or stale syncs, and schedules a calendar reminder to fix a broken connector before its next scheduled run.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every day at 7:30 AM WebRun
1 Airbyte check every connection's sync status
2 Microsoft Teams report failed or stale syncs
3 Google Calendar schedule a fix reminder
Run a sample
In short

How do I catch a failed or stale Airbyte sync before it causes a data gap?

WebRun checks every Airbyte connection each morning, compares its last sync time against its expected schedule, and posts a Microsoft Teams summary of any connection that failed or has gone stale. It also schedules a Google Calendar reminder to fix each broken connector before its next run, so silent sync failures never sit unnoticed.

  • Failed and stale syncs get caught the same morning, not weeks later
  • Every broken connector gets a scheduled reminder, not a forgotten ticket
  • Healthy connections drop off the list automatically, no manual triage

Built for data engineering teams · analytics engineers · data platform admins · BI 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 cloud.airbyte.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Airbyte - check every connection's sync status
    airbyte.com
    WebRun in Airbyte: check every connection's sync status
    WebRun opens Airbyte to check every connection's sync status.
    • Open Airbyte and list every connection
    • Check each connection's last sync status and timestamp
    • Flag any connection that failed or hasn't synced within its expected window

    Done when Every connection has a checked sync status.

  3. 2
    Microsoft Teams - report failed or stale syncs
    microsoft.com How to Automate Microsoft Teams
    WebRun in Microsoft Teams: report failed or stale syncs
    WebRun posts to Microsoft Teams to report failed or stale syncs.
    • Post a summary of failed or stale connections to the data team channel
    • Name the source, destination, and the last successful sync time for each

    Done when The team has a Teams summary of every connection needing attention.

  4. 3
    Google Calendar - schedule a fix reminder
    calendar.google.com How to Automate Google Calendar
    WebRun in Google Calendar: schedule a fix reminder
    WebRun opens Google Calendar to schedule a fix reminder.
    • Add a reminder event for each broken connector naming the fix needed
    • Set it before the connector's next scheduled sync window

    Done when A calendar reminder exists for every connector that needs fixing.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
cloud.airbyte.com
ScheduleRuns automatically on this cadence
Every day at 7:30 AM
DeliveryHow each run's result reaches you
Sync health report · Microsoft Teams
OutputWhat each run produces - A list of failed or stale Airbyte connections with a scheduled reminder to fix each.
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 it retry or fix a broken sync automatically?

No. WebRun only reports the failure and schedules a reminder. Re-authorizing a connector or fixing the underlying source is left to a human.

How does it know a sync is stale, not just quiet?

It compares each connection's last successful sync time to its expected schedule, so a source with nothing new to sync isn't flagged as broken.

What happens once the connector is fixed?

It reads the live sync status from Airbyte each morning, so a connector that's back to healthy drops off the list automatically.

Put this on autopilot.

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