Block 1 - Structured Output Parser
- Type / Role
- @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
AI Enriched Cold Outreach: Research → Draft → QA → Write back ============================================================ What this template does Automates cold email drafting from a lead list by:...
@n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.splitinbatches, n8n-nodes-base.if, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.lmchatgooglegemini, n8n-nodes-base.manualtrigger, n8n-nodes-base.datatable
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Johnny Rafael.
Original n8n.io sourceAutomates cold email drafting from a lead list by:
email_subject is empty (pending) company_url) → Wait → Results → Data Table update → linkedin_profile_scrape company_url) → Wait → Results → Data Table update → linkedin_company_scrape url_search) → Wait → Results → Data Table update → crunchbase_company_scrapecold-outreach-enrichment-scraper with a RapidAPI key.){
"email_subject": "text",
"email_content": "text"
}
email_subject, email_content, and email for the judge. APPROVED or REVISE (brief feedback allowed). APPROVED → Data Table “Update row(s)” writes email_subject + email_body (a.k.a. email_content) back to the row. REVISE → Skipped; loop continues.Data Table: “email_linkedin_list” (or your own) with at least:
email, First_name, Last_name, Title, Location, Company_Name, Company_site,Linkedin_URL, company_linkedin (if used), Crunchbase_URL,email_subject, email_body,linkedin_profile_scrape, linkedin_company_scrape, crunchbase_company_scrape (string fields for JSON).Credentials:
cold-outreach-enrichment-scraper (store securely as credential, not hardcoded) ABOUT ME block:
Replace the sample persona (James / CEO / Company Sample / AI Automations) with your own.
email_generated_at or processed boolean to prevent reprocessing. You are scraping and storing person/company data.
Ensure lawful basis, respect ToS, and minimize stored data.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 33 workflow blocks. Download the JSON for the full node graph.
| Workflow | Personalized email outreach with LinkedIn & Crunchbase data and Gemini AI review |
|---|---|
| Complexity | advanced |
| Nodes | 33 |
| Categories | Lead Nurturing, AI Chatbot |
| Author | Johnny Rafael |
| Published | 17 Oct 2025 |
Use the JSON export at /data/workflows/9814/9814.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
AI Enriched Cold Outreach: Research → Draft → QA → Write back ============================================================ What this template does Automates cold email drafting from a lead list by:...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Lead Nurturing, AI Chatbot use case.