Forward email & LinkedIn message notifications from Reply.io to Telegram
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 6 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Telegram. It also calls api.reply.io over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Get person info from Reply.io (HTTP Request): calls an HTTP API
- Send notification to Telegram (Telegram): uses Telegram
- Get subscriptions (HTTP Request): calls api.reply.io
- Create subscription (email) (HTTP Request): calls api.reply.io (POST)
- Create subscription (linkedin) (HTTP Request): calls api.reply.io (POST)
Services it uses
HTTP calls to: api.reply.io
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (3)
- HTTP Request
n8n-nodes-base.httpRequest - Webhook
n8n-nodes-base.webhook - Telegram
n8n-nodes-base.telegram
From the author
How this works: This workflow contains a webhook that receives updates from Reply.io when one of your connections sends you a message via either Email or LinkedIn. The workflow also includes utility nodes to create the necessary webhook subscriptions. Setup…