Enrich new accounts in Pipedrive using Datagma API
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Item Lists (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 9 nodes and runs on Pipedrive events. Along the way it connects Pipedrive. It also calls gateway.datagma.net over HTTP.
How it runs
Trigger: On Pipedrive events.
- Datagma - Enrich Company (HTTP Request): calls gateway.datagma.net
- list people (Item Lists): reshapes item lists (legacy Item Lists node)
- Pipedrive: update (organization)
- If: checks a condition and branches into true / false
- Merge: merges the data from its input branches
- Datagma - Find Emails (HTTP Request): calls gateway.datagma.net
- Pipedrive: work with person
- Prepare Data Before Merge (Edit Fields (Set)): sets or maps fields
Services it uses
HTTP calls to: gateway.datagma.net
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Item Lists (legacy) in list people: replace with Split Out, Aggregate, Sort, Limit, Remove Duplicates or Summarize (match the operation used).
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Item Lists (legacy) list people | Split Out, Aggregate, Sort, Limit, Remove Duplicates or Summarize (match the operation used) |
Nodes used (7)
- Item Lists
n8n-nodes-base.itemLists - Pipedrive
n8n-nodes-base.pipedrive - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Pipedrive Trigger
n8n-nodes-base.pipedriveTrigger
From the author
This workflow enriches new accounts in Pipedrive using Datagma API by adding data about ICP (ideal customer profile). Instead of Pipedrive, you can use any other CRM. In this example, ideal buyers are heads of sales/business development. Prerequisites -…