Find & verify business emails automatically with OpenRouter, Serper & Prospeo
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: AI Agent v1 (old agent modes). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 10 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Google Sheets and OpenRouter Chat Model. It also calls google.serper.dev over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Get Rows (Google Sheets): uses Google Sheets
- Get Email Pattern (HTTP Request): calls google.serper.dev (POST)
- Has Snippet Results? (If): checks a condition and branches into true / false
- Loop Over Items (Loop Over Items (Split in Batches)): loops over the items in batches
- AI Agent: runs an AI agent, with model: OpenRouter Chat Model; output parser: Structured Output Parser
- Verify Email (HTTP Request): calls an HTTP API (POST)
- Update Rows (Google Sheets): append or update
Services it uses
HTTP calls to: google.serper.dev
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- AI Agent v1 (old agent modes) in AI Agent (v1.9): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| AI Agent v1 (old agent modes) AI Agent (v1.9) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (8)
- Manual Trigger
n8n-nodes-base.manualTrigger - Google Sheets
n8n-nodes-base.googleSheets - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenRouter Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenRouter - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - HTTP Request
n8n-nodes-base.httpRequest - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - If
n8n-nodes-base.if
From the author
Who is this template for? Growth teams, SDRs, recruiters, or anyone who routinely hunts for hard‑to‑find business emails and would rather spend time reaching out than guessing formats. What problem does this workflow solve? Manually piecing together email…