Integrations / GitHub Actions
GitHub Actions
Scheduled workflows are loops too.
Why connect it
Every repo has Actions, and scheduled workflows fail quietly for months — a nightly job that has failed 47 runs in a row is the same finding as a broken cron.
What you'll see
- Every workflow with an `on: schedule`, its cron, 7-day runs and failures
- Total and failed-ever counts, and the job and step that failed last
- Billable minutes this cycle
- Disabled workflows shown as paused
What the credential can and cannot do
Where to get it: github.com → Settings → Developer settings → Fine-grained tokens, with Actions: read and Contents: read on the repositories you want read.
It grants: Read on Actions and repository contents for the repositories you select.
It cannot: Cannot push, cannot change workflows. Pausing a workflow is a command you run, shown with its undo.
Whatever you connect lives in an encrypted cookie in your browser and nowhere else. Sign out and it's gone; revoke it at the provider and it stops working immediately.