Make.com

You don’t “connect” Make like a traditional integration. You send data from Make to LeadLock using the inbound webhook.

1. In LeadLock: Settings → Integrations (or Webhooks). Copy your inbound webhook URL and optional secret (e.g. x-make-secret). 2. In Make: Add an HTTP module (POST) to your scenario. Use the LeadLock webhook URL. Add the secret as a header if required. 3. Send a JSON body with at least name; include email, phone, company, source, message as needed.

CRM → Settings → Integrations or Webhooks. You’ll see the inbound webhook URL (e.g. https://your-domain/api/inbound/make/lead or similar). Copy it into Make’s HTTP module. If you use a secret, add it as a header (e.g. x-make-secret).

In your Make scenario, use an HTTP “Make a request” module: • Method: POST • URL: your LeadLock inbound webhook URL • Headers: Content-Type: application/json; add x-make-secret if your account uses it • Body: JSON with name, email, phone, company, source, message, etc. as needed

Run the scenario; the lead appears in Leads and Pipeline.

• The scenario must be turned on and run (trigger fires). • The HTTP request must succeed (200). Check Make’s execution history for errors. • URL and secret must match LeadLock. Wrong secret often returns 401. • Body must be valid JSON; required fields (e.g. name) must be present or you may get 400.

1. In LeadLock: Settings then Integrations or Webhooks. Copy the inbound webhook URL and optional secret (e.g. x-make-secret). 2. In Make: Add an HTTP module (POST) to your scenario. Use the LeadLock webhook URL. Add the secret as a header if required. 3. Set body to JSON with at least name; include email, phone, company, source, message as needed. 4. Run the scenario; the lead should appear in Leads. 5. If not: check Make execution history for 200; confirm URL and secret; ensure JSON and required fields are correct.

Webhooks, Leads, Integrations, Advanced/Developers.