Advanced HTTP (optional)

Core LeadLock automations and AI follow-ups run inside the product — no external automation platform is required. If you use Zapier, n8n, Make, or custom code, you send data to LeadLock using the inbound HTTP webhook (same endpoint for advanced tools).

1. In LeadLock: CRM → Integrations → Advanced automations. Copy your inbound webhook URL and optional secret (e.g. x-make-secret). 2. In your tool: 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 → Integrations (optional Advanced section). You’ll see the inbound webhook URL (e.g. https://your-domain/api/inbound/make/lead or similar). Copy it into your HTTP client or your automation tool’s HTTP module. If you use a secret, add it as a header (e.g. x-make-secret).

In your automation scenario, use an HTTP POST step: • 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 automation must be turned on and run (trigger fires). • The HTTP request must succeed (200). Check your tool’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: CRM → Integrations → Advanced automations. Copy the inbound webhook URL and optional secret (e.g. x-make-secret). 2. In your automation tool: Add an HTTP module (POST). 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 flow; the lead should appear in Leads. 5. If not: check execution logs for 200; confirm URL and secret; ensure JSON and required fields are correct.

Inbound HTTP, Leads, Integrations, Advanced/Developers.