GitHub gives you a list of workflow runs, one repository at a time. What it cannot tell you is whether the alert that fired this afternoon followed a deploy from a different service. Kollaber records each workflow deploy as an event on one timeline, so the deploy and the alert that followed it sit next to each other.
Find the environment UUID on the dashboard under your environment settings, then add it to the repository as a secret named KOLLABER_ENV_ID.
The webhook endpoint takes a plain JSON body and needs no authentication, so a single curl step is the whole integration.
- name: Notify Kollaber
run: |
curl -sS -X POST https://kollaber.io/webhooks/events \
-H "Content-Type: application/json" \
-d '{
"type": "deploy",
"service": "${{ github.repository }}",
"environment_id": "${{ secrets.KOLLABER_ENV_ID }}",
"metadata": {
"version": "${{ github.sha }}",
"author": "${{ github.actor }}",
"ref": "${{ github.ref }}"
}
}'The deploy appears on the environment timeline immediately over SSE — no refresh, no polling.
No. The endpoint accepts a plain JSON POST, so a curl step is enough. There is nothing to install and no OAuth flow to approve.
Yes. The environment is chosen by the environment_id in the body, so pass a different secret per job or per matrix leg to split staging from production.
Yes. Events of type deploy feed deployment frequency and lead time, and failed deploys feed change failure rate.
The free plan covers two environments and five members. The full reference for this integration lives in the docs.