Quickstart

1. Get an address

Your tool gives you an https:// address that receives requests: a Webhook node in n8n, a Custom webhook in Make, a Catch Hook trigger in Zapier, a Webhook source in Clay, or a route of your own code. The guides show where to find it in each tool.

To look at a test event without any tool, you can use a public request inspector. Don’t point a destination that receives real leads to it: it would keep personal data on someone else’s servers.

2. Create the destination

In the console, open Settings › Integrations, then Add destination.

Where — pick your tool. All of them receive the same signed request; the tool only sets the right defaults. Slack has its own button, Connect Slack (see the Slack guide).
What — give it a name, paste the address, and pick the events: All events (including the ones added later), or only some. lead.created and lead.engaged_again are checked by default. Under More options: one request per event or batches, up to three headers of your own, and past events to send right away (none, the last 24 hours, 7 days or 31 days).
Create destination.

3. Copy the signing secret

The next screen shows the destination’s signing secret (whsec_…) once. Copy it into your tool’s secret store: it signs every request TIKT sends you. You can rotate it later.

4. Send a test

Click Send test. TIKT sends a webhook.test event right away and shows the answer: Delivered · 200 OK in 312 ms, or what went wrong. A test can also be sent later from the destination. Any answer with a 2xx status within 15 seconds counts as delivered. The request body looks like this:

{
  "id": "1d6e5f3a-2b4c-4d8e-9f10-112233445566",
  "type": "webhook.test",
  "created_at": "2026-10-06T22:31:04Z",
  "api_version": "2026-10-01",
  "workspace_id": "6c1f0e2a-9b8d-4e7f-8a6b-5c4d3e2f1a0b",
  "data": {
    "destination": { "id": "…", "name": "n8n — hot leads", "tool": "n8n", "…": "…" },
    "message": "This is a test event from TIKT. Your endpoint is reachable and the signature can be verified."
  }
}

5. Verify the signature

Every request carries three headers — webhook-id, webhook-timestamp, webhook-signature — that prove it comes from TIKT and was not changed on the way. The official Standard Webhooks library checks them in one call:

Node

import { Webhook } from "standardwebhooks";

const event = new Webhook(process.env.TIKT_SIGNING_SECRET).verify(rawBody, headers);
// throws if the signature, the timestamp or the body is wrong

Use the raw body, exactly as received: parsed and re-serialized JSON won’t match. Verify signatures has complete examples in Node and Python.

From now on, each new lead arrives within minutes. See what each event carries in Events.
Want only some leads? Create a workflow on the Leads page.

Get started

Webhooks

Events

1. Get an address

2. Create the destination

3. Copy the signing secret

4. Send a test

5. Verify the signature

Next

​1. Get an address

​2. Create the destination

​3. Copy the signing secret

​4. Send a test

​5. Verify the signature

​Next

1. Get an address

2. Create the destination

3. Copy the signing secret

4. Send a test

5. Verify the signature

Next