Skip to main content

​
1. Create the webhook in Make

  1. In a new scenario, add the Webhooks app and choose Custom webhook as the trigger.
  2. Click Add, name the webhook, and save. Make shows its address: copy it.
  3. Leave the module waiting for data.

​
2. Add the destination in TIKT

  1. In TIKT, Settings › Integrations › Add destination › Make.
  2. Paste the address. The events checked by default are lead.created and lead.engaged_again; keep One request per event.
  3. Create destination, copy the signing secret, then Send test.
Make receives the test event and learns the data structure. To teach it the structure of a real lead, run the scenario once and wait for a lead.created, or use Redetermine data structure in the webhook module.

​
3. Use the lead

The event’s fields appear in the modules that follow: type, then data › lead › person › full_name, data › lead › score, and so on (see Objects). To act on some events only, put a filter after the webhook: type — Equal to — lead.created.

​
4. Check where requests come from

In TIKT, under More options › Headers, add a header of your own — for example X-Tikt-Key with a long random value. In Make, open the webhook’s advanced settings and turn on Get request headers, then add a filter that keeps only the requests carrying this header and value.

​
Only some leads

Create a workflow on the Leads page with a Send webhook action to this destination: Make receives one lead.matched per lead that matches your filters.