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 to replace before upgrading
| 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
What it does
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 - Pipedrive account and Pipedrive credentials How it works 1. Pipedrive trigger node starts the workflow when a new company is created. 2. HTTP Request node queries data from Datagma. 3. Pipedrive node updates Pipedrive contact with new data from Datagma. 4. The Item Lists node simplifies returned data from Datagma that contain lists (arrays), enabling you to easily modify the structure for further processing without the need to use Function nodes and write custom JavaScript. 5. IF node identifies if the lead corresponds ICP. 6. HTTP Request node searches for emails in Datagma. 7. Set node prepares data for further merging. 8. Merge node combines data from multiple streams. 9. Pipedrive node adds a new person in Pipedrive.