Send purchase conversions from Bitrix24 deals to Google Ads using offline click tracking
Ready for 3.0What this workflow does
This workflow has 18 nodes and runs when an HTTP POST request hits its webhook URL. It uses only n8n's built-in nodes.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Settings (Edit Fields (Set)): sets 11 fields: bitrixWebhookBase, googleAdsCustomerId, googleAdsLoginCustomerId…
- Extract Deal ID (Code): runs custom JavaScript code
- Get Deal from Bitrix (HTTP Request): calls an HTTP API
- Check Eligibility (Code): runs custom JavaScript code
- Eligible for Upload? (Filter): keeps only the items that match a condition
- Get Contact from Bitrix (HTTP Request): calls an HTTP API
- Normalize Customer Data (Code): runs custom JavaScript code
- Hash Email (Crypto): hashes or encrypts values
- Hash Phone (Crypto): hashes or encrypts values
- Hash First Name (Crypto): hashes or encrypts values
…plus 7 more steps. See the full node list below.
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 (6)
- Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Filter
n8n-nodes-base.filter - Crypto
n8n-nodes-base.crypto
From the author
Quick overview This workflow receives Bitrix24 deal updates via a webhook, fetches the deal and contact details, and uploads an offline Purchase conversion to the Google Ads Click Conversion API using the deal’s GCLID and value, then writes success or error…