Zapier, Make, and n8n

Two webhooks connect Konektor to other tools:

  • An incoming webhook brings leads into Konektor. The other tool posts to a Konektor address.
  • An outgoing webhook sends Konektor events out. Konektor posts to an address of the other tool.

You can use one, or both in a loop.

Send leads into Konektor

First create an incoming webhook and copy its address. See Incoming webhooks. The steps below use that address.

Zapier

  1. Make a Zap. Choose your trigger, for example a new form answer.
  2. Add the action Webhooks by Zapier, then choose POST.
  3. In URL, paste the Konektor address.
  4. Set Payload Type to json.
  5. Add the data to send. Use a name for each, for example name, phone, and email, and pick the value from your trigger.
  6. Select Test. Konektor keeps this post as the example. Make sure you selected Wait for a test post in Konektor first.
  7. Go back to Konektor, choose the fields, and select Save.
  8. Turn the Zap on.

Make

  1. Make a scenario. Add your trigger module.
  2. Add the module HTTP, then Make a request.
  3. In URL, paste the Konektor address. Set Method to POST.
  4. Set Body type to Raw, Content type to JSON (application/json), and write the body, for example {"name": "...", "phone": "...", "email": "..."}. Pick the values from your trigger.
  5. In Konektor, select Wait for a test post. In Make, select Run once.
  6. In Konektor, choose the fields and select Save. Turn the scenario on.

n8n

  1. Make a workflow. Add your trigger node.
  2. Add the node HTTP Request. Set Method to POST and paste the Konektor address in URL.
  3. Turn on Send Body, set Body Content Type to JSON, and add the fields to send.
  4. In Konektor, select Wait for a test post. In n8n, select Execute step.
  5. In Konektor, choose the fields and select Save. Activate the workflow.

Tips

  • Send the same shape every time. If you rename a field later, run a new test post and choose the fields again.
  • Send a stable ID from the other tool and choose Reference from the other tool as the match. A retry then updates the lead and does not make a double.
  • A 422 answer means the post had no name, phone, or email. A 429 answer means the daily lead limit is full.

Send Konektor events out

Use an outgoing webhook to start a Zap, a scenario, or a workflow when a lead is created or changed.

  1. In Zapier, choose the trigger Webhooks by Zapier and Catch Hook. In Make, add the module Webhooks and Custom webhook. In n8n, add the node Webhook with method POST. Each tool gives you an address.
  2. In Konektor, open API & Webhooks and add a webhook. Paste the address and choose the events, for example lead.created.
  3. Select Test on the webhook. The test event arrives in your tool.
  4. Build the rest of your flow with the data of the event.

Konektor signs each event. To check the signature, read Webhooks.

Loop both ways

You can add leads from a form with an incoming webhook, then send lead.updated out when a sales person changes the status. Do not send the same lead back into the same incoming webhook from an outgoing flow, because it can start a loop. If you must, map a Reference from the other tool and set the match to it.

Need More Help?

Our team is ready to help you maximize ad tracking and business attribution.

Wulan answers your questions and sends tutorial videos. Session scheduling is available through Wulan if you still need it.

© 2026 Konektor. All rights reserved.