Pipedrive + Datagma: enriched leads, fewer bad fits
Your CRM fills up fast. And then your team spends hours chasing companies that were never a fit in the first place, because the “new org” record is basically just a name and a domain.
This is where Pipedrive lead enrichment helps. Sales Ops feels it when reps complain about lead quality. A founder feels it when pipeline reviews turn into guesswork. And a growth marketer feels it when targeting gets muddy. You will enrich every new company automatically and flag bad fits early.
This workflow connects Pipedrive and Datagma, checks each company against your ICP, then pulls the right contacts and adds them back into Pipedrive. No manual research marathons.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Pipedrive + Datagma: enriched leads, fewer bad fits
flowchart LR
subgraph sg0["Pipedrive Trigger - New Company Created Flow"]
direction LR
n0["<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/itemLists.svg' width='40' height='40' /></div><br/>list people"]
n1["<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/pipedrive.svg' width='40' height='40' /></div><br/>Pipedrive - Enrich Organizat.."]
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/pipedrive.svg' width='40' height='40' /></div><br/>Pipedrive - Add Person"]
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/>Datagma - Enrich Company"]
n4["<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/merge.svg' width='40' height='40' /></div><br/>Merge"]
n5@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If lead is Ideal Buyer", pos: "b", h: 48 }
n6["<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/>Datagma - Find Emails"]
n7@{ icon: "mdi:swap-vertical", form: "rounded", label: "Prepare Data Before Merge", pos: "b", h: 48 }
n8["<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/pipedrive.svg' width='40' height='40' /></div><br/>Pipedrive Trigger - New Comp.."]
n4 --> n2
n0 --> n5
n0 --> n4
n6 --> n7
n5 --> n6
n3 --> n0
n3 --> n1
n7 --> n4
n8 --> n3
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 n8 trigger
class n5 decision
class n3,n6 api
classDef customIcon fill:none,stroke:none
class n0,n1,n2,n3,n4,n6,n8 customIcon
The Problem: New companies arrive with zero context
A new company gets created in Pipedrive and it looks “complete,” but it’s not. It’s a shell record. Someone still has to figure out what the company does, whether it matches your ideal customer profile, and who the right people are (heads of sales, business development, revenue, whatever matters for your offer). That work is slow, and worse, it’s inconsistent. One rep goes deep, another skims LinkedIn, and suddenly your pipeline quality depends on who had coffee that morning. It adds up to a lot of wasted time and a lot of noisy deals.
The friction compounds. Here’s where it breaks down.
- Reps spend about 10–20 minutes researching a single company before they can even decide if it’s worth a first touch.
- Bad-fit accounts sit in your CRM for months, which means forecasts, segments, and “top of funnel” reporting quietly rot.
- Contact discovery becomes a scavenger hunt, so follow-up gets delayed and good leads cool off.
- Manual enrichment creates messy fields and one-off notes that nobody trusts later.
The Solution: Enrich new Pipedrive companies with Datagma and validate ICP
This workflow kicks in the moment a new company is created in Pipedrive. n8n sends that company’s identifying info to Datagma through an HTTP request, then receives enrichment data back (company details plus structured lists you can actually use). Next, the workflow cleans and reshapes Datagma’s response so it’s easy to work with, even if the data comes back as arrays or nested fields. Then it checks the enriched company against your ICP rules using an IF step, so you can separate “good fit” from “nope” automatically. If it’s a match, the workflow searches Datagma for emails, merges the useful pieces, and creates the right Person record inside Pipedrive. Cleaner company record. Correct contacts. Faster handoff.
The workflow starts with a “new organization” trigger in Pipedrive. Datagma enrichment runs next, then an ICP check decides what happens. Finally, matching accounts get contacts added back into Pipedrive so reps can act immediately.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your team adds 20 new companies to Pipedrive each week from forms, lists, and referrals. Manually, even a “quick” process takes about 15 minutes to research the company plus another 10 minutes to find a real decision-maker and email, so you’re looking at roughly 8 hours a week of busywork. With this workflow, creating the company is the only manual step, then enrichment and ICP checking happens in the background and the matching accounts get a Person added automatically. Most weeks, you get an afternoon back.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Pipedrive for the company and person records.
- Datagma to enrich companies and find emails.
- Datagma API key (get it from your Datagma dashboard).
Skill level: Intermediate. You’ll connect accounts, map a few fields, and tweak ICP rules in an IF condition.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A new company triggers the run. When an Organization is created in Pipedrive, n8n picks it up right away (no manual “enrich now” button).
Datagma enrichment fills in the blanks. An HTTP request sends the company identifier (often domain or name) to Datagma and receives enriched attributes back. Then an Item Lists step restructures list-heavy fields so you can map them cleanly without custom code.
ICP filtering decides what happens next. The IF logic checks for fit based on the fields you care about (industry, size, location, keywords, or custom scoring). If you want a heads-of-sales targeting motion, this is where you enforce it.
Contacts and emails get added to Pipedrive. For ICP matches, the workflow searches Datagma for emails, merges the best data, and creates a new Person tied to the Organization. You can also push a heads-up to Slack or log to Google Sheets if you want visibility.
You can easily modify the ICP rules to match your market and swap the final destination from “create a person” to “notify the team” based on your needs. See the full implementation guide below for customization options.
Common Gotchas
- Pipedrive credentials can expire or need specific permissions. If things break, check your n8n Credentials panel and confirm the connection can list Organizations.
- 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–60 minutes if your Datagma and Pipedrive access is ready.
No. You’ll mostly map fields and adjust the ICP check. The only “technical” part is pasting API keys into the right credential fields.
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 Datagma API costs, which depend on your enrichment and email lookups.
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 it’s usually just a logic change. Update the IF condition to match your ICP fields (industry, size, geography, keywords), then adjust the “search emails” request so it prefers the titles or departments you care about. Common tweaks include routing non-ICP accounts to a “do not prospect” stage, writing enrichment fields into custom Pipedrive fields, and sending Slack alerts only for top-tier matches.
Most of the time it’s an invalid or expired API key. Regenerate the key in Datagma and update the HTTP Request credentials in n8n. Also check that your request is sending the identifier Datagma expects (domain vs. company name), because a mismatched input can look like a “failure” when it’s really just an empty response. If you’re enriching lots of companies at once, rate limiting can show up too, so add a small delay or process items in smaller batches.
On n8n Cloud, it depends on your monthly execution limit, while self-hosting is mainly limited by your server. In practice, most small teams run hundreds of new-company enrichments per month without thinking about it.
Often, yes. n8n is more comfortable with multi-step logic like “enrich, normalize arrays, check ICP, then search emails, then merge, then create a person,” and you don’t pay extra just because the flow branches. Self-hosting is also a big deal if you expect lots of runs and don’t want to meter every task. Zapier or Make can still be a fine choice for very simple two-step enrichments, especially if you want a guided UI and fewer knobs. If you’re on the fence, Talk to an automation expert and you’ll get a straight recommendation.
Once this is running, new companies stop being mystery boxes in your CRM. The workflow handles the repetitive research so your team can spend that time talking to real prospects.
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.
