EvoHub

GitHub alerts, routed to the right on-call engineer

Page on failed GitHub Actions runs and deployments on your default branch, and on Dependabot, code scanning and secret scanning alerts. Signed with your webhook secret. EvoHub turns each GitHub alert into an on-call alert, runs it through your escalation policy, and pages people by voice call, mobile push and email.

How the GitHub integration works

  1. Create a GitHub integration in EvoHub On-Call and pick the escalation policy it should notify.
  2. EvoHub gives the integration its own URL (or inbound address) with a unique key — paste it into GitHub using the steps below.
  3. Each GitHub alert opens an EvoHub alert, and your escalation policy pages the on-call person — then the next step if nobody acknowledges.
  4. Resolves automatically: a successful run of the same workflow, a successful deployment to the same environment, or the alert being fixed, dismissed, withdrawn or resolved on GitHub.

Set up GitHub

Create the integration in EvoHub first — it shows your personal integration URL to paste below.

# 1. Repository (or organization) → Settings → Webhooks → Add webhook
Payload URL: <your EvoHub integration URL>
Content type: application/json
Secret: the signing secret from this integration (Signing secret → Generate)

# 2. "Let me select individual events" — tick what should page:
#    Workflow runs, Deployment statuses,
#    Dependabot alerts, Code scanning alerts, Secret scanning alerts

# 3. Add webhook. GitHub sends a ping — EvoHub answers OK, no alert.

# What pages:
#  • a workflow run that fails, times out or cannot start on the
#    default branch → high; the next successful run resolves it
#  • a failed deployment → critical for production, else high;
#    the next successful deployment to that environment resolves it
#  • Dependabot alert → the advisory's severity; fixed / dismissed /
#    withdrawn resolves
#  • code scanning alert on the default branch (or one that
#    appears there when a branch is merged) → its severity;
#    fixed / closed resolves
#  • secret scanning alert → critical; resolved on GitHub resolves.
#    EvoHub never reads or stores the secret itself.
# Other events and branches (and organization events with no
# repository) are answered OK and open nothing.

# With a secret set, every delivery must carry a valid
# X-Hub-Signature-256 — anything else is refused.

GitHub + EvoHub — FAQ

How do I connect GitHub to EvoHub?

In EvoHub, go to On-Call → Integrations, add GitHub, and choose an escalation policy. Then configure GitHub with the integration URL EvoHub shows you — the exact steps are on this page.

Do GitHub alerts resolve automatically in EvoHub?

Resolves automatically: a successful run of the same workflow, a successful deployment to the same environment, or the alert being fixed, dismissed, withdrawn or resolved on GitHub.

How is the GitHub integration priced?

Integrations are included. EvoHub bills on usage, not per seat: an ingested alert costs 1 EvoHub token (about $0.015), push and webhook notifications are free, and every account gets 200 free tokens each month.

Start free — 200 EvoHub tokens every month. See pricing.

Last updated: · EvoHub is built and operated by EvoSync Teknoloji A.Ş.