When should you use it?
- Leads arrive in Airtable from forms or ads with only a name and email
- Your team researches each lead by hand
- You already use Make.com
Not for: Enriching people who haven't engaged with you, where privacy law limits it; High volumes on paid APIs without a budget cap
What do you need, and what do you get?
You need
- An Airtable base of leads
- A Serper.dev key for Google results
- An enrichment API through RapidAPI or similar
You get
- Lead records updated with title, company, size, industry and profile URL
- Cleaner data for segmenting
- Better inputs for personalized emails
How does it work, step by step?
- Watch for new recordsTrigger the scenario whenever Airtable gets a new lead row.
- Search for contextQuery Google through Serper with the person's name or email address to locate profiles and the company site.
- Pick the best resultLoop through results and keep the most relevant link or title.
- Enrich the companyCall an enrichment API for size, industry and role.
- Update the recordWrite the new fields back so the CRM is ready for outreach.
The prompt
Our own prompt, inspired by u/rusticmarketer on r/coldemail and written to work in ChatGPT, Make and n8n. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
New lead: name {name}, email {email}. Search results: {search_results}. Pick the profile and company site that belong to this person; accept a match only if the company domain matches the email domain or the profile clearly names the same company. Return JSON: title, company, company_domain, size, industry, profile_url, confidence (high, medium, low) and the reason. If nothing matches, return low confidence and empty fields.
Inspired by u/rusticmarketer on r/coldemail: Using a simple lead enrichement automation for personalized cold outreach. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Name-based searches match the wrong person; check uncommon matches before emailing.
- Each lead costs API calls; set limits so a bulk import doesn't run up a bill.
Our take
This is a tidy, inexpensive enrichment pipeline and a good first project for anyone using Make and Airtable. Its weak point is identity matching. Searching a person's name will happily return a namesake, and a cold email that references the wrong company is worse than a generic one. Add a check that the found profile's company domain matches the lead's email domain, and mark low-confidence matches for review. Think about privacy too: enriching people who filled in your form is usually fine with a clear privacy notice, while enriching scraped lists can run into GDPR and similar rules. Cap spending on the paid API so a big import doesn't surprise you. Once the data is reliable, the personalization step can be done by an assistant that writes a short opener from the enriched fields, but keep a human reading those emails until you trust them. Re-enrich old leads periodically, since job titles go stale quickly.
Where the time goes back: Lead research that took minutes per record happens as soon as the lead arrives.
FAQ
Where does AI come in?
Will he share the blueprint?
Source and credit
Inspired by u/rusticmarketer on r/coldemail. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Using a simple lead enrichement automation for personalized cold outreach
- Creator
- u/rusticmarketer on r/coldemail
- Published on
- Original date
- Oct 23, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- ChatGPT
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.