n8n workflows,wired to ClickFlare both ways

ClickFlare sends events like conversions to n8n the moment they happen, and n8n can report conversions back and pull report data through the ClickFlare API. One workflow can catch an event, check a report and act on it, on servers you control.

n8n
n8n
Workflow automation platform

n8n integration at a glance

How it connects
ClickFlare webhook out; conversions and API calls back in
What syncs
ClickFlare events out; conversions and report data in
How fresh the data is
Real time for events, on demand for reports
What you can optimize
Campaigns below your ROI floor, flagged as soon as they slip
Works with
n8n cloud and self-hosted instances over HTTPS
Good to know
Point ClickFlare at the live workflow, not the test one.
Automation platform
Events in real time
Runs on your servers

Events in, conversions and reports out

Data on your own servers

n8n can run on your own infrastructure, so conversion data from ClickFlare stays on servers you control.

Partner payloads mapped inline

n8n reads nested fields and does math as it maps, so a partner reward turns into a ClickFlare conversion with no extra steps.

Only ClickFlare gets through

Protect the workflow with a shared secret that ClickFlare sends with every event, so nothing else can trigger it.
How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversionautomated actionyour dashboardsclosed revenue

01
Your ad
Visitor clicks
Ad on n8n
02
ClickFlare
Click recorded
Every click gets its own ID
03
Your offer
Conversion
Lead, sale or custom event
04
ClickFlare
Sent back to n8n
Through the Conversion API or postback
05
Cost API
Spend pulled in
n8n cost matched to each campaign
01
Your ad
n8n click
Placement, device and country come along
02
ClickFlare
Click recorded
Zone, site and device data stored
03
Offer or lander
Visitor converts
On your page or the offer
04
ClickFlare
Conversion logged
With payout and event type
05
Postback
Reported to n8n
So its optimization sees the result
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
Every click gets its own ID
03
Your article
Keyword block
Click ID passed to the feed
04
Results page
Paid click
Conversion fired to ClickFlare
05
n8n API
Revenue matched
Pulled on a schedule and reconciled
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
The click follows the visitor to the offer
03
n8n
Offer or call
The network tracks the action
04
n8n
Conversion
Lead, sale, call or rebill
05
Postback
Payout in ClickFlare
Matched to the original click
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
Every click gets its own ID
03
n8n
Store or funnel
Click ID kept through checkout
04
Events
View, cart, checkout
Each step tracked
05
ClickFlare
Purchase recorded
Order value matched to the ad
01
Your ad
Visitor clicks
Form, call or landing page
02
ClickFlare
Click recorded
Every click gets its own ID
03
n8n
Lead or call stored
The ad stays linked to the lead
04
n8n
Qualified or closed
Workflow or call rule fires
05
ClickFlare
Revenue recorded
Tied to the ad that drove it
01
ClickFlare
Event happens
Click, conversion or custom event
02
Webhook or API
Data goes out
Or comes back in
03
n8n
Your workflow
Rules, apps or an AI assistant
04
n8n
Action
Alert, update, pause or scale
05
ClickFlare
Back in reports
Changes show in your data
01
ClickFlare
Report data
Campaigns, sources, offers
02
ClickFlare API
Your numbers go out
Secured with your API key
03
Your setup
Scheduled refresh
A sheet, script or connector
04
n8n
Data lands
Tables refreshed on schedule
05
n8n
Dashboards
Blended with your other data
Automation platform

ClickFlare events in, conversions and reports out

ClickFlare sends each mapped event to your n8n workflow as it happens. Further down the same workflow, n8n can report a conversion to ClickFlare or pull a campaign report through the API with your key.
  • Up to 10 events per integration
  • Your API key stored once as a credential
  • Long reports pulled page by page
Today, one campaign
example
Spend pulled from n8n
cost
$412.30
Conversions recorded
today
38
Sent back to n8n
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
ROI per placement
example
Placement A · mobile
cost
$38.20
Placement A
revenue
$71.40
Placement A
ROI
+87%
Placement B · desktop
ROI
−42%
Example numbers. Keep the placements that pay and cut the ones that lose money.
Revenue for one click
example
Paid click
day 0
$0.00
First revenue pull
+1h
$0.41
Scheduled updates
next days
$0.58
Final pull
last sync
$0.62
Example amounts. Sync timing for n8n is in the facts above.
Events for one click
example
Lead
day 0
$0.00
Sale
day 0
+$40.00
Upsell
day 1
+$15.00
Refund
day 9
−$15.00
Example events. Each one arrives by postback and is matched to the click.
One visitor's path
example
Product view
step 1
—
Add to cart
step 2
—
Checkout
step 3
—
Purchase
step 4
$68.00
Example order. Each event is tied to the ad that brought the visitor.
One lead, followed to revenue
example
Lead created
day 0
$0.00
Qualified
day 2
+$25.00
Deal closed
day 14
+$480.00
Renewal
day 45
+$120.00
Example values. Each stage can be its own event type in ClickFlare.
A scheduled report refresh
example
Campaigns
in the report
1,240 rows
Cost, revenue, profit
per campaign
included
Refresh
your schedule
done
Dashboards fed
n8n
3
Example numbers. You choose the breakdowns, date range and schedule.
One event, end to end
example
Conversion recorded
event
sent
Event delivered
n8n
received
Workflow ran
n8n
done
Team notified
your apps
done
Example run. What happens after the event is up to your workflow.
10
Events per integration
16MB
n8n webhook payload max
2.3B
Events tracked
Setup

Connected in three steps

You need a ClickFlare account with your own tracking domain, an n8n instance reachable over HTTPS, and an API key for API calls.
  1. Catch ClickFlare events in n8n Start a workflow with a webhook trigger, publish it and add it to ClickFlare's webhook integration for the events you want.
  2. Report conversions back Add a step that sends the click ID, payout and conversion type to ClickFlare. Test it with a real click ID.
  3. Pull reports with your API key Store your ClickFlare API key in n8n once, then pull campaign data into any workflow you build.
app.clickflare.com/integrations
n8n
n8n
Automation platform
Connected
n8n account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
n8n template selected
Macros pre-filled
Tracking URL in n8n
Click ID captured
Conversions reported
Payout included where supported
n8n connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
n8n added
Offer URL carries the click ID
Postback set in n8n
Payout and event included
Conversions arriving
Matched to the click
n8n connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Click ID stored in n8n
Hidden field or call data
Workflow or rule set
Fires on the stage you choose
Conversions arriving
With payout and event type
API key created
Settings, then Security
Report pull scheduled
Dimensions and date range set
n8n dashboards live
Refreshed on schedule
Connection set up
Webhook, API key or MCP
Events chosen
Only what the workflow needs
Workflow running
Tested end to end
Ready to track
n8n's test address only works while you are building. Switch ClickFlare to the live workflow after you publish, or events are lost.
n8n setup guide
Open the guide
In your reports

What you see once it's connected

  • Conversions from any n8n trigger
  • Payout per conversion
  • Conversions by type
  • Report rows by any breakdown
  • Campaign lists via the API
  • ROI alerts by campaign
Use cases

How media buyers run it

Conversion → ClickFlare → n8n → your database

Self-hosted event pipeline

Keep every conversion with click ID and payout on infrastructure you control.
PartnerStack → n8n → ClickFlare

Partner rewards into ClickFlare

Each partner reward becomes a conversion on the click that earned it, with the right payout.

Hourly ROI alerts

Every hour, n8n pulls today's campaign report, keeps campaigns below your ROI floor and posts the list to Slack.
Frequently asked questions

n8n integration FAQ

Does ClickFlare integrate with n8n?

Yes, both ways. ClickFlare sends events to an n8n workflow through a webhook, and n8n can report conversions back or call the ClickFlare API.

Can I self-host it?

Yes. It works with n8n cloud and self-hosted instances reachable over HTTPS, so your conversion data can stay on your own servers.

How does n8n connect to the ClickFlare API?

With your ClickFlare API key, stored once as an n8n credential and sent with every request.

Why does a conversion I send record nothing?

Check that the click ID is filled in, that the conversion type matches a custom conversion exactly, and that you send it to your own tracking domain.

Can I keep several conversions on one click apart?

Yes. Send a unique transaction ID with each one. A new ID adds a conversion, and the same ID replaces the earlier one.

Can n8n use the ClickFlare MCP server instead?

The MCP server is meant for AI assistants. For fixed automations, the API is the simpler route.

No items found.
Setup guides
n8n setup guide
Custom webhook integration
{"@context": "https://schema.org", "@graph": [{"@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with n8n?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, both ways. ClickFlare sends events to an n8n workflow through a webhook, and n8n can report conversions back or call the ClickFlare API."}}, {"@type": "Question", "name": "Can I self-host it?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. It works with n8n cloud and self-hosted instances reachable over HTTPS, so your conversion data can stay on your own servers."}}, {"@type": "Question", "name": "How does n8n connect to the ClickFlare API?", "acceptedAnswer": {"@type": "Answer", "text": "With your ClickFlare API key, stored once as an n8n credential and sent with every request."}}, {"@type": "Question", "name": "Why does a conversion I send record nothing?", "acceptedAnswer": {"@type": "Answer", "text": "Check that the click ID is filled in, that the conversion type matches a custom conversion exactly, and that you send it to your own tracking domain."}}, {"@type": "Question", "name": "Can I keep several conversions on one click apart?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Send a unique transaction ID with each one. A new ID adds a conversion, and the same ID replaces the earlier one."}}, {"@type": "Question", "name": "Can n8n use the ClickFlare MCP server instead?", "acceptedAnswer": {"@type": "Answer", "text": "The MCP server is meant for AI assistants. For fixed automations, the API is the simpler route."}}], "dateModified": "2026-11-12"}, {"@type": "BreadcrumbList", "itemListElement": [{"@type": "ListItem", "position": 1, "name": "Integrations", "item": "https://www.clickflare.com/integrations"}, {"@type": "ListItem", "position": 2, "name": "Automation", "item": "https://www.clickflare.com/integrations/automation"}, {"@type": "ListItem", "position": 3, "name": "n8n"}]}]}