Works with
- GitHub
- Telegram
Requirements
- GitHub token allowed to manage the repository's webhooks
- Telegram bot (from @BotFather), for Telegram notifications (optional)
- SMTP account of your mail provider, for email notifications (optional)
You connect your own accounts inside your n8n. Jervis never sees or stores your credentials.
Settings you'll fill in
- Channels
- Where to send notifications: "telegram", "email", or "telegram, email".
- Telegram chat id (optional)
- Chat, group or channel that receives notifications. Needed for the telegram channel.
- Email recipients (optional)
- Up to 10 addresses, separated by commas. Needed for the email channel.
- Sender address (optional)
- An address your SMTP account may send from, optionally with a name: "GitHub alerts <alerts@example.com>".
- Actions to report (optional)
- Comma-separated: opened, reopened, closed, edited, labeled, assigned, deleted.
- Only these labels (optional)
- Optional. Report only issues carrying one of these labels (comma-separated). Empty reports all.
- Message language (optional)
- Language of the notifications: "en" or "ar".
Supported runtime
n8n >=2.42.0 <3.0.0
Jervis Runtime support for catalog flows is planned.
Documentation
Installation, configuration, troubleshooting and architecture guides are included in the package.
What's new in 1.0.0
Released October 7, 2026
Added
• GitHub issue events through the n8n GitHub Trigger, which registers a signed webhook on activation and
• refuses unsigned deliveries.
• Notifications to Telegram, email, or both, in English or Arabic.
• Filters for issue actions and labels.
• Each delivery is notified once per channel; a redelivery from GitHub sends only the channels that failed.
• Import-tested in a clean n8n 2.42.3 against fake GitHub, Telegram and SMTP services.