How to connect any payment tool to NEMO

AT A GLANCE

With Webhook de ventas, NEMO tracks which link brings each sale with no pixels and no Google Analytics. Count and attribute sales from ANY tool that can send a POST — GoHighLevel, Zapier, Make, n8n or your own code. NEMO gives you a secret URL of your own. Your tool sends it a simple JSON when a sale comes in, and NEMO attributes it: by nm_id if it travels, by the buyer's email if they're already one of your leads, and failing that it's recorded “no source” — it is never lost. The method is “Direct notice from the platform” (server-side · highest reliability): The platform itself notifies NEMO of every sale — and every refund — with a direct server-to-server message (no dependence on anyone's browser). Stripe, Hotmart, ThriveCart, SamCart, Gumroad and Lemon Squeezy ship with it (native connection); the “Sales webhook” opens it to any tool that can send a POST. The email is used ONLY to match the sale with your leads (it becomes an irreversible code on arrival — NEMO never stores emails from events). The full connection is 4 steps and you verify it with a single test click.

How is each Webhook de ventas sale attributed?

Direct notice from the platform · Server-side · highest reliability

NEMO gives you a secret URL of your own. Your tool sends it a simple JSON when a sale comes in, and NEMO attributes it: by nm_id if it travels, by the buyer's email if they're already one of your leads, and failing that it's recorded “no source” — it is never lost.

1. Click “Connect” on this card: NEMO generates YOUR URL (it carries your secret token — don't publish it; you can regenerate it whenever you want).
2. In your tool, create a webhook/POST action to that URL for when a sale comes in (in Zapier: “Webhooks by Zapier → POST”; in Make: the HTTP module; in GoHighLevel: the workflow's “Custom Webhook” action).
3. The body is this JSON (Content-Type: application/json). Only “event” is required; the more fields you send, the better the attribution:

   {
     "event": "sale",
     "email": "customer@example.com",
     "amount_cents": 4900,
     "currency": "eur",
     "nm_id": "the-nm-id-if-you-have-it",
     "external_id": "order-id"
   }

4. Refunds? Send another POST with event “refund”: with “external_id” it finds the exact order (without it, that email's latest sale); “amount_cents” is what's refunded in THIS notice (several partials add up; without it, it counts as a full refund):

   {
     "event": "refund",
     "external_id": "order-id",
     "amount_cents": 2500
   }

Note: The email is used ONLY to match the sale with your leads (it becomes an irreversible code on arrival — NEMO never stores emails from events).

Note: “external_id” (the order id) makes the notice idempotent: if your tool retries, the sale counts ONCE.

Note: An extra or misspelled field → NEMO responds 400 and records nothing (better a visible error than corrupt data).

Check it in one minute

1. Send a test POST from your tool (or its test button) with the sample JSON.
2. The sale shows up in your dashboard instantly and the card switches to “last notice a moment ago”.

Frequently asked questions

What do I do if it responds 401?

The URL isn't yours (or you regenerated the token and your tool is still using the old one). Copy the current URL from this card.

What do I do if it responds 400?

The JSON doesn't fit: check that “event” is exactly "sale", that there are no extra fields and that amount_cents is a whole number (cents).

What do I do if the sale arrives “no source”?

No nm_id traveled and the email doesn't match any of your leads. If your tool knows the email that person subscribed with, send it — NEMO does the rest.

ALSO INTEGRATES WITH

• Gumroad
• Hotmart
• Lemon Squeezy