Guide · Make
Make Webhook: Receive Every Attributed Conversion
Subtraq knows where every conversion came from. Your Make scenarios know what to do with it. Between the two: one address, nothing else.
The whole guide fits right here
Subtraq
Settings → Connect other tools → Outgoing webhooks
Make
Webhooks > Custom webhook → Add → Save
The address is Make's: the module generates it as soon as you save the webhook and starts listening. Paste it into Subtraq, and every lead or every sale fires the scenario.
In Make, 3 steps
Three steps and one address
In Subtraq, you choose what the webhook sends — leads, sales, or both — and whether it applies to a single client workspace or the whole account. The signing secret is shown once: copy it if your scenario needs to verify the sender.
"API Key authentication" is optional in Make's module. Subtraq does not send an x-make-apikey header: leave that option empty, and verify the sender via Subtraq's signature if you need to.
In the Scenario Builder, search for the “Webhooks > Custom webhook” module.
Next to the “Webhook” menu, click “Add”; in “Webhook name”, give it a name, then “Save”. Make generates the address and starts listening.
Copy the address (hook.make.com/…), then paste it into Subtraq, under “Outbound webhooks”.
Path checked in Make's documentation on September 11, 2026 — the original page. Interfaces change: if what you see no longer matches, the source wins.
What the scenario receives
A JSON recognized on the first send
According to its documentation, Make recommends determining the data structure from a first request: send one conversion while the module is waiting, and the fields become mappable in subsequent modules. If new fields arrive later, "Detect new values" in the module settings recalculates them.
A null placement is not an oversight: it's a conversion Subtraq couldn't attribute, and it says so rather than inventing a source.
The fields, as the code writes them
event (lead or sale) · at · space (slug and name of the space) · person (email, external identifier) · placement (slug and label of the source link, or null if the conversion is unattributed) · amountMinor and currency for a sale · eventId.
Before counting on it
Three things to know
No queue
Two attempts per send, then the failure is logged in the app, next to the webhook, with its date and message. A destination that's down for several minutes loses the sends from that window — the conversion itself is recorded regardless.
The scenario must be running
The module generates the address and listens as soon as the webhook is saved; what the scenario does next with the data — and at what pace — is configured in Make's scenario settings.
A signature, if you want to verify the sender
Each send carries the X-Subtraq-Signature header: "t=TIMESTAMP,v1=SIGNATURE," where SIGNATURE is the HMAC-SHA256 of "TIMESTAMP.BODY" computed with the secret shown at webhook creation.
Frequently asked questions
Do I need to install a Subtraq app in Make?
No. The "Custom webhook" module expects an address and a JSON — that's what Subtraq sends. Nothing to install in Make, nothing to publish.
How do I test without waiting for a real sale?
Trigger a lead on the workspace — submitting a connected form is enough — while the module is waiting for its first request: that's how Make determines the data structure, according to its documentation.
What if Make is down when a conversion happens?
The conversion is recorded regardless; it's the send that fails. Two attempts, then the failure is logged in the app, next to the webhook.
Do I need to fill in "API Key authentication"?
No: it's optional in Make, and Subtraq doesn't send the x-make-apikey header. To verify the sender, use Subtraq's signature.
Zapier, n8n — same thing?
Yes: the same JSON, to the address of a "receive a webhook" trigger. The Zapier guide gives the path in its interface; n8n has its own guide too.
You work in Zapier instead?
Same move, same JSON: Zapier's "Catch Hook" trigger has its own guide, recorded the same day from its help page.
The Zapier guidePaste the address into your scenario
Create the account, add the webhook, paste Make's address. The first attributed lead fires the first scenario.
Create a free account