Skip to main content
An inbound webhook brings the sale into Kampp. An outbound webhook goes the other way: when access is created, Kampp notifies a system of yours — n8n, Make, Zapier or any endpoint that can receive data. The most common use: sending the buyer’s login and password over WhatsApp, on top of the email.

​
Create an outbound webhook

1

Open Integrations → Webhooks

In the Integrations menu, click the Webhooks card.
2

Create the webhook

Click New webhook and give it a name (e.g. “n8n — welcome”).
3

Paste the destination URL

Under Destination URL, paste the https://... address that will receive the event.
4

Choose what triggers it

Under Fire when access is delivered by, tick the sales integrations (Kiwify, Hotmart, Sellyo) that should trigger this webhook.
5

Save and test

After saving, use Test on the webhook detail page. Kampp sends a sample event right away and shows your system’s response.

​
What Kampp sends

An access.created event, with:
  • the buyer’s details (name, email, phone)
  • the login and password for their access
  • the name of the integration the sale came from
The request is signed (X-Kampp-Signature header) so your system can verify where it came from — verifying is optional.

​
Tracking deliveries

On the webhook detail page, the Logs block shows each attempt with date and status. If your system is down, Kampp retries automatically.
The outbound webhook is secondary: if it fails, Kampp’s own delivery still happens. The buyer never loses access because of an external automation.
With no integration ticked, the webhook never fires. The dashboard warns you when that’s the case — just click Edit and pick one.