Alert Telegram the moment a VIP account emails you
Checks every inbound email against a VIP domain list kept in a Google Sheet.
A Gmail Trigger watches the whole inbox. A Google Sheets read loads the VIP domain list — held in a spreadsheet so an account manager can add a key account without touching n8n — and a Code node running once for all items compares the sender's domain against every row, matching both exact domains and subdomains of them. An IF passes only the matches. The Telegram node sends the sender, subject and a 200-character preview with notifications deliberately not silenced, and a Gmail label step stars and marks the message important so the mailbox agrees with the alert when you next sit down. Every external call retries and routes failures to an error rail that posts to Discord — a different service from the alert channel, because an alert about a broken Telegram must not travel through Telegram.
Key benefits
- ✓Key-account mail reaches your phone in about a minute instead of waiting for the next inbox check
- ✓The VIP list is a spreadsheet, so account managers maintain it without touching the automation
- ✓Subdomains of a listed company match too, so regional offices are not missed
- ✓The message is starred in Gmail as well, so the inbox and the alert agree
- ✓Alert failures are announced on a different service, so a Telegram outage is still visible
Use cases
- →Account managers covering a handful of renewals worth more than the rest of the book
- →Founders who want to know when an investor or a large customer writes in
- →Support leads with contractual response times for named accounts
- →Anyone who has found a key customer's email four hours after it arrived
Integrations
Workflow preview (8 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (8 nodes)
A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.
From download to running in 3 steps
- 1Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
- 2Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
- 3Activate. Run it once to test, then toggle Active. The automation is live.
What you'll learn
Core levelA compact production shape: validation and error handling without extra machinery.
- •Moving data between Gmail, Google Sheets and Telegram in a single run
- •Adding retries and an explicit error path to external calls
- •Testing against pinned sample data before connecting anything real
Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.
Common questions
What exactly do I get?
The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.
How do I import it into n8n?
In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.
Do I need anything else for it to work?
You need your own n8n instance and accounts/credentials for the apps this workflow connects to (Gmail, Google Sheets, Telegram, Discord). No coding is required.
What if it doesn't work for me?
If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.
Can I modify or resell it?
You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.
Related templates
Turn inbound enquiry emails into HubSpot contacts without duplicates
Watches the public sales aliases, ignores free-mail senders, then asks HubSpot whether the address is already known. New business senders become contacts at lifecycle stage Lead; existing contacts are logged as repeat enquiries instead of overwriting fields a human curated.
Auto-reply to out-of-hours email with an SLA promise and log it
Answers email that arrives outside working hours with an in-thread reply carrying a stated deadline, and logs the promise to a sheet so the morning shift can honour it. Messages arriving during office hours are left alone on purpose.
Alert stakeholders on changes: Slack for real-time alerts
Real-time alerts on n8n: runs when a webhook arrives across Slack, Google Sheets and Telegram, starting at "Keep Valid Events". Routes each kind of record down its own branch. 12 documented nodes.
Notify the team on new events: Gmail
Real-time alerts on n8n: runs when a webhook arrives across Gmail, Slack and Google Sheets, starting at "Read Metrics from Gmail". Routes each kind of record down its own branch. 13 documented nodes.