Send validated lead emails from Google Sheets via Hunter, Gmail and Telegram
Ready for 3.0What this workflow does
This workflow has 15 nodes and runs on a schedule (every day at 11:00). Along the way it connects Google Sheets, Hunter and Gmail. It also calls api.telegram.org over HTTP.
How it runs
Trigger: On a schedule (every day at 11:00).
- Fetch Lead Data from Google Sheets (Google Sheets): uses Google Sheets
- Check for Blank Email ID (If): checks a condition and branches into true / false
- Verify Email Addresses (Hunter): email verifier
- Validate Email - Deliverable (If): checks a condition and branches into true / false
- Send Valid Lead Emails (Gmail): uses Gmail
- Check Email Status for Action (If): checks a condition and branches into true / false
- Set Email Status - sent (Edit Fields (Set)): sets or maps fields
- Set Email Status - skipped (Edit Fields (Set)): sets 1 field: status
- Set Email Status - invalid (Edit Fields (Set)): sets 1 field: status
- Merge: merges the data from its input branches
…plus 3 more steps. See the full node list below.
Services it uses
HTTP calls to: api.telegram.org
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 (10)
- Google Sheets
n8n-nodes-base.googleSheets - Hunter
n8n-nodes-base.hunter - No Operation, do nothing
n8n-nodes-base.noOp - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Gmail
n8n-nodes-base.gmail - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
Quick overview This workflow runs on a schedule to fetch leads from Google Sheets, verify email deliverability with Hunter, send messages via Gmail, update each lead’s send status back in Google Sheets, and post a run summary to Telegram. How it works 1. Runs…