Works with
- RSS
- Telegram
Requirements
- Telegram bot (from @BotFather), for the Telegram digest (optional)
- SMTP account of your mail provider, for the email digest (optional)
You connect your own accounts inside your n8n. Jervis never sees or stores your credentials.
Settings you'll fill in
- Feeds
- RSS or Atom feed URLs, one per line (up to 20). Add " | Name" to name a feed.
- Channels
- Where to send the digest: "telegram", "email", or "telegram, email".
- Telegram chat id (optional)
- Chat, group or channel that receives the digest. 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: "Daily digest <digest@example.com>".
- Entries per feed (optional)
- How many new entries to list per feed, 1 to 20 (default 5). The rest are counted as "+ N more".
- Message language (optional)
- Language of the digest's headings: "en" or "ar". Entries keep their own language.
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
• A daily digest of up to 20 RSS or Atom feeds, sent at a chosen time.
• Delivery to Telegram, email, or both, with headings in English or Arabic.
• Each channel remembers delivered entries; a digest that failed is folded into the next one.
• Feeds that could not be read are reported in the digest.
• Telegram digests stay within Telegram's message size by listing fewer entries per feed.
• Import-tested in a clean n8n 2.42.3 against fake feeds, Telegram and SMTP.