Extract email addresses from websites with EmailListVerify API and Google Sheets
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 12 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Google Sheets. It also calls api.emaillistverify.com over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Get input Data (Google Sheets): uses Google Sheets
- Add http to url if missing (Code): runs custom JavaScript code
- Merge: merges the data from its input branches
- Get the website data (HTTP Request): calls an HTTP API
- Email found? (If): checks a condition and branches into true / false
- Extract the emails found (Edit Fields (Set)): sets 1 field: Email
- Split Out: splits a list into separate items
- Transform website into domain name (Code): runs custom JavaScript code
- Add result to google (Google Sheets): append or update
- Use EmailListVerify API to find generic emails (HTTP Request): calls api.emaillistverify.com (POST)
…plus 1 more step. See the full node list below.
Services it uses
HTTP calls to: api.emaillistverify.com
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 (8)
- HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - Manual Trigger
n8n-nodes-base.manualTrigger - Code
n8n-nodes-base.code - Merge
n8n-nodes-base.merge - Google Sheets
n8n-nodes-base.googleSheets - If
n8n-nodes-base.if - Split Out
n8n-nodes-base.splitOut
From the author
How to scrape emails from websites This workflow will : - Try to find emails by scraping the website via http request - If no result is found, it will use EmailListVerify email finder API to guess an email address Scraping email via http request is a…