Configuration
Notification preferences
Understand how Zapat communicates job status via GitHub and the dashboard.
Updated March 3, 2026
Zapat communicates job status in several ways. Here is what to expect and how each channel works.
GitHub notifications
Zapat interacts directly with GitHub, which triggers GitHub's native notification system:
- When Zapat starts working on an issue, it adds an 👀 reaction to confirm receipt.
- When triage completes, a comment is posted on the issue with the triage summary and implementation plan.
- When a PR is opened, GitHub notifies repo subscribers and anyone assigned to the issue.
- When Zapat leaves a review, you receive a standard GitHub review notification.
- When a PR is merged, GitHub notifies PR subscribers.
You control who gets notified through GitHub's standard subscription settings — watch the repo, get notified on mentions, or subscribe to specific issues.
Dashboard notifications
The Zapat dashboard shows real-time job status in the Pipeline view. Jobs transition through states (queued → running → completed) and the dashboard auto-refreshes while you have active jobs.
Email and Slack (coming soon)
Email and Slack webhook notifications for job events (completed, failed, PR merged) are on the roadmap. Until they are available, GitHub notifications and the dashboard are the primary monitoring tools.
Note
If you want to be notified when a specific issue is worked on, "subscribe" to that issue on GitHub. You will receive all Zapat comments and PR activity via your GitHub notification settings.
Was this article helpful?