Connect Pipedrive deal outcomes to GA4 & Google Ads via Measurement Protocol
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 13 nodes and runs on Pipedrive events. Along the way it connects Pipedrive.
How it runs
Trigger: On Pipedrive events.
- Assign Variables (Edit Fields (Set)): sets or maps fields
- Get a deal (Pipedrive): uses Pipedrive
- get stages for pipeline (HTTP Request): calls an HTTP API
- Split Out: splits a list into separate items
- Filter: keeps only the items that match a condition
- If: checks a condition and branches into true / false
- Get a person (Pipedrive): uses Pipedrive
- get personFields (HTTP Request): calls an HTTP API
- Get client_id and consent_granted (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
…plus 2 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Pipedrive Trigger
n8n-nodes-base.pipedriveTrigger - Pipedrive
n8n-nodes-base.pipedrive - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Split Out
n8n-nodes-base.splitOut - Filter
n8n-nodes-base.filter
From the author
Who’s it for Problem: Your ads and GA4 often optimize to shallow web events (form fills), while the real value sits in Pipedrive (Qualified, Closed Won). That gap means bidding chases cheap leads instead of revenue. Solution: This template turns Pipedrive…