Crunchbase to Gmail, personalized outreach at scale
Copying Crunchbase details into Gmail sounds simple until you’ve done it 40 times in a row. Names get misspelled, “quick tweaks” turn into rewrites, and follow-ups quietly slip through the cracks.
This is where Crunchbase Gmail outreach automation helps. SDRs feel it first, but startup founders doing founder-led sales and partnership folks chasing warm intros run into the same wall. You end up spending about 2 hours a day on prep work instead of sending better emails.
This workflow pulls company and founder data, summarizes it with AI, and drafts a personalized outreach email in Gmail. You’ll see how it works, what you need, and what to watch out for before you turn it on.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Crunchbase to Gmail, personalized outreach at scale
flowchart LR
subgraph sg0["When clicking ‘Test workflow’ Flow"]
direction LR
n0@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser", pos: "b", h: 48 }
n1@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Updated profiles List"]
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Founder Profiles by UUID"]
n4@{ icon: "mdi:swap-vertical", form: "rounded", label: "Extract Key Profile Fields", pos: "b", h: 48 }
n5@{ icon: "mdi:robot", form: "rounded", label: "Summarizer Agent", pos: "b", h: 48 }
n6@{ icon: "mdi:message-outline", form: "rounded", label: "Send email for outreach", pos: "b", h: 48 }
n7@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Test workflow’", pos: "b", h: 48 }
n5 --> n6
n1 -.-> n5
n2 --> n3
n3 --> n4
n0 -.-> n5
n4 --> n5
n7 --> n2
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n7 trigger
class n0,n5 ai
class n1 aiModel
class n2,n3 api
classDef customIcon fill:none,stroke:none
class n2,n3 customIcon
The Problem: Crunchbase Research Turns Into Inbox Busywork
You already know the “right” outbound motion: research the company, find the founder or decision-maker, write a relevant opener, and keep the tone consistent across the sequence. The reality is messier. Crunchbase tabs pile up, you copy fields into a doc, then into Gmail, then you rewrite the same lines because you can’t remember what you sent to the last five companies. One skipped follow-up can kill a deal. One sloppy merge can burn a brand impression.
It adds up fast. And it’s rarely one big failure, it’s a dozen small ones.
- You spend maybe 10 minutes just gathering founder and company context for a single email.
- Personalization gets inconsistent because you’re rushing and reusing the last draft.
- Copy-paste mistakes happen at the worst time, like mixing up company names mid-thread.
- Follow-ups become a “later” task, which means they often don’t happen.
The Solution: Crunchbase Data → AI Summary → Gmail Outreach Draft
This n8n workflow turns Crunchbase research into ready-to-send outreach drafts in Gmail. You kick it off manually when you’re ready to process a batch. n8n pulls updated company profiles via an HTTP request, then fetches founder details as a second pass so you have both the org-level context and the person-level specifics. Next, it maps the fields you actually care about (company name, role, key facts) into a clean structure. Then an AI agent reads that structured data, creates a short profile summary, and uses it to write a personalized email that still matches your messaging. Finally, the workflow dispatches the outreach email through Gmail, so the draft becomes an actual send (or a send-ready message, depending on how you configure Gmail).
The workflow starts with a manual trigger, then it collects Crunchbase data in two steps. After that, OpenAI generates a concise summary and a tailored email based on the mapped fields. Gmail handles the final mile: sending the outreach message with the personalized content already filled in.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you’re doing founder outreach to 25 companies a week. Manually, you might spend about 10 minutes pulling Crunchbase company info and another 10 minutes finding and writing about the founder, so roughly 20 minutes per lead (about 8 hours weekly). With this workflow, you trigger the run, let it fetch and summarize in the background for a few minutes, then review and send. Even if you spend 2 minutes per email on a quick human edit, you’re back to about 1 hour of hands-on work.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Crunchbase API access to retrieve company and founder data.
- Gmail to send outreach emails from your account.
- OpenAI API key (get it from your OpenAI dashboard’s API keys page).
Skill level: Intermediate. You’ll connect accounts, paste API keys, and adjust prompts and fields to match your offer.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
You start the run when you’re ready. The workflow uses a manual trigger, which is handy for outbound because you usually want control over timing and volume.
Crunchbase profiles are pulled in and refreshed. An HTTP request retrieves updated company profiles first, then a second HTTP request fetches founder details so the outreach has real person-specific context, not generic company blurbs.
The data gets cleaned up into a reliable format. A “set fields” mapping step takes the messy payload and turns it into consistent fields (think: names, roles, highlights), which means your AI prompt doesn’t have to guess what’s missing.
AI summarizes and writes the outreach email, then Gmail sends it. The OpenAI chat engine plus the profile summary agent generate a short, relevant summary and a personalized message. The Gmail step dispatches the email so it lands where your outbound actually happens.
You can easily modify the email structure to match your template and positioning based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Set up the manual trigger to start the workflow on demand.
- Add the Manual Execution Start node as the trigger.
- Leave all default settings as-is for manual execution.
- Connect Manual Execution Start to Retrieve Updated Profiles to follow the execution flow.
Step 2: Connect Crunchbase Data Retrieval
Configure the HTTP requests to pull founder profiles and details from Crunchbase.
- In Retrieve Updated Profiles, set URL to
https://api.crunchbase.com/api/v4/relationships/organizations/1234abcd-5678-efgh-ijkl-9012mnop3456/people. - Enable Send Query and set the query parameter page to
1. - Enable Send Headers and set header X-Cb-User-Key to
[CONFIGURE_YOUR_API_KEY]. - In Fetch Founder Details, set URL to
=https://api.crunchbase.com/api/v4/entities/people/{{ $json.data.items[0].uuid }}. - Enable Send Headers and set header X-Cb-User-Key to
[CONFIGURE_YOUR_API_KEY]. - Connect Retrieve Updated Profiles → Fetch Founder Details to match the workflow sequence.
[CONFIGURE_YOUR_API_KEY] is not replaced with a valid Crunchbase API key, both HTTP requests will fail with authorization errors.Step 3: Set Up Profile Field Mapping
Map the Crunchbase response into structured fields used by the AI agent.
- In Map Core Profile Fields, add assignments for the following fields and values:
- Set Full name to
={{ $json.data.properties.full_name }}. - Set Title to
={{ $json.data.properties.title }}. - Set biography to
={{ $json.data.properties.biography }}. - Set Education to
={{ $json.data.properties.education }}. - Set Social Links to
={{ $json.data.properties.social_links }}. - Set Associated companies to
={{ $json.data.properties.associated_companies }}. - Connect Fetch Founder Details → Map Core Profile Fields.
Step 4: Set Up AI Summarization
Configure the AI agent to generate a concise outreach summary using the OpenAI model and structured output parser.
- Open OpenAI Chat Engine and select model
gpt-4o-mini. - Credential Required: Connect your openAiApi credentials in OpenAI Chat Engine.
- In Structured Result Decoder, keep the provided JSON Schema Example to enforce structured output.
- In Profile Summary Agent, set Text to
=Full name: {{ $json['Full name'] }} Title: {{ $json.Title }} biography: {{ $json.biography }} Education: {{ $json.Education }} Social Links: {{ $json['Social Links'] }} Associated companies: {{ $json['Associated companies'] }}. - Enable Has Output Parser in Profile Summary Agent so it uses Structured Result Decoder.
- Connect Map Core Profile Fields → Profile Summary Agent.
Step 5: Configure the Email Output
Send the AI-generated outreach summary to your email inbox via Gmail.
- In Dispatch Outreach Email, set Send To to
[YOUR_EMAIL]. - Set Subject to
=CrunchBase profile for outreach. - Set Message to
={{ $json.output.body }}. - Credential Required: Connect your gmailOAuth2 credentials in Dispatch Outreach Email.
- Connect Profile Summary Agent → Dispatch Outreach Email.
Step 6: Test and Activate Your Workflow
Validate the end-to-end flow and then enable the workflow for production use.
- Click Execute Workflow on Manual Execution Start to run a manual test.
- Confirm that Retrieve Updated Profiles and Fetch Founder Details return valid Crunchbase data.
- Verify that Profile Summary Agent outputs a structured
subjectandbodyfrom Structured Result Decoder. - Check your inbox for the message from Dispatch Outreach Email containing the AI-generated summary.
- Toggle the workflow Active to enable it for ongoing use.
Common Gotchas
- Crunchbase credentials can expire or need specific permissions. If things break, check your Crunchbase API key status and plan access in your Crunchbase developer settings first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30 minutes if your API keys and Gmail access are ready.
No. You’ll mostly connect accounts and adjust a few fields and prompts.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API usage (often a few cents per batch, depending on prompt size) and any Crunchbase API plan costs.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should. Most teams customize the “Map Core Profile Fields” step to match what they care about (industry, funding stage, headcount, location), then adjust the “OpenAI Chat Engine” and “Profile Summary Agent” instructions so the email uses their tone and offer. You can also change the Gmail step to create drafts instead of sending immediately if you want a review queue.
Usually it’s an expired OAuth session or the wrong Google account connected in n8n. Reconnect Gmail in n8n’s credentials, then confirm the workflow has permission to send mail. If it fails only on bigger batches, you may also be hitting provider limits or sending too fast, so slow the run down and test with a smaller set.
On n8n Cloud, it depends on your execution limits, but most small teams comfortably run hundreds of leads a week; if you self-host, the practical limit is your server plus your API rate limits.
Often, yes, if you care about control. This workflow benefits from structured data mapping, conditional logic, and AI steps that are easier to manage in n8n without hitting premium “task” pricing every time you add complexity. Zapier and Make can still work, but multi-step enrichment plus AI plus email sending tends to get expensive fast, and debugging is not as pleasant. The bigger factor is safety: with n8n you can choose to create drafts, add checks, and self-host if you want data to stay on your infrastructure. Talk to an automation expert if you want help choosing the right stack.
Once this is running, your outreach stops depending on copy-paste stamina. You get consistent personalization, faster follow-ups, and a process you can actually scale.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
