Automation library · Integrations

Deduplicate and send server-side conversions

Started by another system calling it, and works across n8n data table. 15 steps: a working afternoon to understand properly.

Medium

15 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 4Service 10

The steps in the order they run, from what starts it.

  1. 1Conversion WebhookWebhookStarts it
  2. 2SettingsSetLogic
  3. 3Parse and NormalizeCodeLogic
  4. 4Skip If Already SentData TableService
  5. 5Record Event KeyData TableService
  6. 6Hash EmailCryptoService
  7. 7Hash PhoneCryptoService
  8. 8Hash First NameCryptoService
  9. 9Hash Last NameCryptoService
  10. 10Hash CityCryptoService
  11. 11Hash ZipCryptoService
  12. 12Hash CountryCryptoService
  13. 13Build Meta PayloadCodeLogic
  14. 14Send Event to Meta CAPIHttp RequestService
  15. 15Validate Meta ResponseCodeLogic

How it's built

Starts on
Another system calling it
Steps
15
Size
Medium: a working afternoon
Connects to
n8n data table
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 15 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 15 steps before you point it at anything that matters.