Audit Meta pixel deduplication risks with Graph API and Claude

by Nocode Expert ✓ · 21 views · created 2026-07-17 · Market Research, AI Summarization

What this workflow does

This workflow has 13 nodes and runs manually, when you click “Execute workflow”. It uses only n8n's built-in nodes. It also calls api.anthropic.com over HTTP.

How it runs

Trigger: Manually, when you click “Execute workflow”.

1. Set config (account & thresholds) (Edit Fields (Set)): sets 7 fields: META_AD_ACCOUNT_ID, META_API_VERSION, META_ACCESS_TOKEN…
2. List account pixels (HTTP Request): calls an HTTP API
3. List optimization targets (adsets) (HTTP Request): calls an HTTP API
4. Extract optimization targets (Code): runs custom JavaScript code
5. Select active pixels (Code): runs custom JavaScript code
6. Get browser vs server split (HTTP Request): calls an HTTP API
7. Carry pixel id + source split (Code): runs custom JavaScript code
8. Get per-event counts (HTTP Request): calls an HTTP API
9. Classify dedup risk per pixel (Code): runs custom JavaScript code
10. Build AI dedup summary prompt (Code): runs custom JavaScript code

…plus 2 more steps. See the full node list below.

HTTP calls to: api.anthropic.com

Before you upgrade to n8n 3.0

Nodes used (4)

• Manual Triggern8n-nodes-base.manualTrigger
• Edit Fields (Set)n8n-nodes-base.set
• HTTP Requestn8n-nodes-base.httpRequest
• Coden8n-nodes-base.code

From the author

Quick overview This workflow audits Meta (Facebook) Pixels for potential duplicate conversion counting by comparing browser Pixel vs Conversions API (server) activity and highlighting events active campaigns optimize for, then uses Anthropic Claude to…

View the original on n8n.io → Check your own copy