Webhook not triggering

If you added a label but no job appeared in the Zapat dashboard within 30 seconds, something in the webhook chain is broken. Work through this checklist to find the problem.

Step 1: Verify the GitHub App is installed

• Go to GitHub.com > Settings > Installed GitHub Apps (for personal repos) or your GitHub organization settings > Installed GitHub Apps.
• Verify "Zapat" is in the list.
• Click "Configure" next to Zapat.
• Under "Repository access", verify the repository where you added the label is listed. If you selected "Only select repositories", the specific repo must be in the list.

Step 2: Check GitHub webhook delivery logs

• Go to your GitHub organization settings (or user settings) > GitHub Apps.
• Click "Edit" next to Zapat.
• Click "Advanced" to see recent webhook deliveries.
• Find the delivery for the "issues" event that should have triggered.
• Check the response code — it should be 200 or 201. A 4xx means the webhook was rejected; a 5xx or timeout means Zapat had a server error.

Step 3: Verify the label name

Zapat only triggers on specific label names. The exact labels that trigger jobs are:

• Issue triggers: "zapat:triage", "zapat:implement", "zapat:research", "zapat:write-tests"
• PR triggers: "zapat:review", "zapat:test", "zapat:rework"

Label names are case-sensitive. "Zapat:implement" (capital Z) will not trigger. Create labels with the exact casing shown above.

Step 4: Check for an existing active job

Zapat prevents duplicate jobs. If there is already a "queued" or "running" job for the same issue, a new job will not be dispatched. Check the Pipeline view in the dashboard — there may already be a job running for that issue.

Step 5: Check your monthly quota

If your monthly issue limit is exhausted, no new jobs will be dispatched. Go to Billing > Usage to check your remaining limit.