Send server-side conversions to the Meta Ads API (CAPI)
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 10 nodes and runs when an HTTP POST request hits its webhook URL. It uses only n8n's built-in nodes. It also calls graph.facebook.com over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Edit Normalize PII (Edit Fields (Set)): sets 4 fields: normalized_email, normalized_phone, firstName…
- Crypto: hashes or encrypts values
- Crypto: hashes or encrypts values
- Crypto: hashes or encrypts values
- Crypto: hashes or encrypts values
- Set - Compute Timestamps & Map Fields (Edit Fields (Set)): sets 10 fields: conversion_timestamp, event_name, hashed_em…
- Preparing for HTTP Request Payload (Code): runs custom JavaScript code
- Sending Events To Facebook Pixel (HTTP Request): calls graph.facebook.com (POST)
- Respond to Webhook: sends the response back to the webhook caller
HTTP calls to: graph.facebook.com
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)
- Edit Fields (Set)
n8n-nodes-base.set - Crypto
n8n-nodes-base.crypto - HTTP Request
n8n-nodes-base.httpRequest - Webhook
n8n-nodes-base.webhook - Respond to Webhook
n8n-nodes-base.respondToWebhook - Code
n8n-nodes-base.code
From the author
Struggling with inaccurate Meta Ads tracking due to iOS 14+ and ad blockers? 📉 This workflow is your solution. It provides a robust, server-side endpoint to reliably send conversion events directly to the Meta Conversions API (CAPI). By bypassing the…