Skip to main content
Lancer has no marketplace app for n8n or Make. You don’t need one: the REST API and webhooks cover the common flows, and the templates below are ready to import.
Not running n8n or Make? Many of these flows exist as built-in rules under Automations (“אוטומציות”) in the app, with nothing to host.

​
Templates

​
API and webhooks

​
Lead intake through a lead form

Facebook / Instagram Lead Ads, Google Ads lead forms and Webflow can also connect directly, with no n8n or Make in between. See Lead sources.

​
Import into n8n

1

Import the file

Workflows → Import from File, then pick the JSON.
2

Add your API key as a credential

Create a Header Auth credential named Lancer API key: name Authorization, value Bearer lk_…. Select it on every HTTP Request node. Give the key only the scopes the flow needs.
3

Set the webhook secret

In the signature-check Code node, the secret comes from the LANCER_WEBHOOK_SECRET environment variable. Self-hosted n8n must also allow the crypto module: NODE_FUNCTION_ALLOW_BUILTIN=crypto.
4

Point Lancer at the flow

Copy the Webhook node’s production URL into a new webhook in Settings → “API ו-Webhooks”, activate the workflow and click Test in Lancer.
The n8n Code node checks the signature against the re-serialised body. That works because Lancer sends compact JSON.stringify output, so the bytes match.

​
Import into Make

1

Import the blueprint

Scenarios → Create → ⋯ → Import Blueprint, then pick the JSON.
2

Reconnect the modules

Open each module and choose your own connections (Google Sheets, Facebook) or webhook.
3

Add your key

On the HTTP modules, replace lk_YOUR_KEY with a key that has the right scopes. Better: keep it in a Make data store or scenario variable.
Make’s custom webhooks can’t verify HMAC signatures. Give the webhook URL only to Lancer, and turn on IP restrictions if your Make plan has them.

​
Lead forms: a URL per form

The lead intake templates post to a lead form rather than to the API. Every lead form (Settings → Sales → Lead forms) has its own webhook URL, and the token in it is the only credential:
  • It accepts JSON or a form post. Without format, Lancer detects the shape.
  • The lead gets the form’s stage and owner; its source is meta_ads, google_ads or website.
  • Fields are matched by key in Hebrew or English (full_name, שם מלא, your-email, טלפון, company, …). Anything unrecognised lands in the lead’s notes as label: value.
  • Replies: 201 { ok, leadId }; 404 for an unknown or disabled form; 422 when there is no name, email or phone; 400 for an unknown format.
Use this instead of the API when the sender can’t keep a secret header, for example a site builder’s built-in webhook: