GitHub Actions monitoring

Monitor your scheduled GitHub Actions workflows — the ones with an on: schedule cron trigger — and get alerted when a run fails or a scheduled run never fires. Connect the crond.io GitHub App once; crond discovers your workflows and creates the monitors for you. No changes to your workflow YAML, no secrets in your Actions config.

Available on the Pro and Enterprise plans. The github_actions monitor source is gated server-side — a Free account can connect the app, but discovered workflows are monitored once you upgrade.

1. Connect the GitHub App

In the dashboard, open Settings → Integrations and click connect github. You'll be redirected to GitHub to install the crond.io app on your personal account or an organization, where you grant it all repositories or just the ones you choose.

crond only needs read access to workflow definitions and run events — it never needs your Actions secrets and never modifies your repositories.

2. Auto-discovery

Once connected, crond scans the repositories you granted and finds every workflow with an on: scheduletrigger, then creates one monitor per workflow at that workflow's cron cadence.

# .github/workflows/nightly.yml
name: Nightly ETL
on:
  schedule:
    - cron: "0 6 * * *"   # crond discovers and monitors this automatically
jobs:
  etl:
    runs-on: ubuntu-latest
    steps:
      - run: ./run-etl.sh   # your job is unchanged

The schedule is synced from GitHub and is read-only in crond — edit the cron in your workflow file and the monitor follows on the next sync. A workflow with several schedule entries is monitored at its tightest interval, so the most sensitive miss detection always wins.

3. What gets reported

Success and failureof each run, delivered via GitHub's workflow_run webhook the instant a run completes.
Missed runs— crond flags the monitor as late or down when the expected run doesn't arrive within the schedule plus your grace period.
Routed to your existing alert channels — Slack, PagerDuty, Discord, Microsoft Teams, Opsgenie, or any webhook. See Alert Channels.

4. Manage and disconnect

Connected installations are listed under Settings → Integrations. GitHub owns the install lifecycle, so to stop monitoring you uninstall the crond app from your account or organization on GitHub — crond reflects the removal and stops monitoring those workflows. Organization installs live under org settings; personal installs under your user settings.

Notes

Only workflows with an on: schedule trigger are discovered — manually or event-triggered workflows are not monitored.
A workflow_runevent can't say which schedule entry fired, so multi-schedule workflows are monitored at their tightest cadence.
The monitor schedule is managed by the integration and is read-only in crond; change it in your workflow YAML instead.