Tilda CRM integration: get Tilda and Flexbe leads into your CRM

You built a Tilda landing page in one evening, but its leads end up in your email inbox. Without a Tilda CRM integration, a manager copies the leads into the CRM by hand, and meanwhile some clients go to competitors. Reviews and repeat submissions get mixed up with real leads.

Forms from any website builder — Tilda, WordPress, 1C-Bitrix and others — connect to the CRM without a developer. Usually the code on the website is enough: it catches form submissions by itself. For Tilda and Flexbe there's a second way — a direct webhook. A webhook is an address to which the builder itself sends every completed form. A Tilda CRM integration links your website forms to your account through such an address. The “Website builder integrations” section gives you this address and turns every submission into a lead (a client card in the CRM): in the right project, at the right funnel step, with the form fields in the card.

Watch the two-and-a-half-minute video, and below you'll find the step-by-step setup.

Why send Tilda leads straight to your CRM

• Repairs and on-site services. A request for a measurement visit from a Tilda landing page instantly becomes a lead at the “New lead” step. City, service and budget go into their own card fields — the manager calls already knowing the task.
• Landing page with reviews and a quiz. You add the review form to the exceptions. It doesn't create leads or clutter the funnel.
• Ad campaign. A client submitted the form twice within an hour. Duplicate protection won't create a second lead: the manager will see the repeat as a comment in the same card.
• Online store on Tilda. The whole order — items, quantity, price — goes into the lead comment.

Website code or webhook: which to choose for Tilda

The website code — the same one the widget uses — catches submissions from the forms of any builder by itself. You paste it into the builder's site settings, in the block for custom HTML code, as described in the article how to install the contact widget on your website. Special form fields (city, service, budget) are marked up with the mouse in the “Website integration” section — the article website form to CRM without a developer walks you through it step by step. The “My builder is not listed” button in the section header reminds you of this option: in the “Your builder is not listed?” window, the “Go to form capture” button takes you straight to the markup.

You need the builder's webhook when exact field mapping by Tilda keys, excluding specific forms, duplicate protection and delayed lead creation matter to you.

How to connect Tilda to your CRM: step-by-step setup

1. 1
   Create an integration

   In the account menu, open “Settings” → “Integrations” → “Integ. with site builders” (direct link — /land/lk/integrations/lead.php). Click “Create integration”, choose the “Tilda” card and click “Next”.
2. 2
   Choose the project and step

   The “Project” list already shows the account's current project (a project is a separate website or business line with its own funnel). In “Default funnel step”, choose the stage where a new lead will land, for example “New lead” (how to create your own stages is covered in the article CRM pipeline stages).
3. 3
   Paste the keys (optional)

   On the “Keys” step, paste the project address into “Tilda project link”. Click “Get keys in Tilda”, copy the “Public key” and “Secret key” and click “Check and find fields”. The account will scan up to 12 pages of the project and find the form fields.
4. 4
   Map the fields

   On the “Fields” step, choose a CRM field for each form field: “Phone”, “Name”, “Email”, “Custom field” or “Skip”. The account recognizes the phone, name and email by itself.
5. 5
   Add exceptions

   On the “Forms” step, enter in “Form exceptions” the forms that shouldn't create a lead: reviews, quizzes, calculators. Or click a form in the “Known forms” list.
6. 6
   Copy the webhook and save

   On the “Webhook” step, click “Copy” next to “Webhook URL”, then “Save”. The address starts working only after you save.
7. 7
   Connect the webhook in Tilda

   Site settings → Forms → “Data receiving services” → Webhook. Paste the address into “Webhook URL”, turn on the “Send Cookies” checkbox, click “Save” and “Connect service to all forms on the site”.
8. 8
   Test with a submission

   Republish the site and send a test submission. The lead will appear in the CRM in about two minutes, and the integration status will change to “Receiving leads”.

Form fields and visit history

Without keys, the form fields will appear on the “Fields” step after the first submission. The “Send Cookies” checkbox attaches the visit history to the lead — the ad source and the pages.

How to connect Flexbe to your CRM

For Flexbe, the wizard is shorter — three steps: “Builder”, “Project”, “Webhook”. No keys or mapping are needed: Flexbe sends the name, phone and email in the submission itself.

1. 1
   Create an integration

   “Create integration” → “Flexbe” → “Next”.
2. 2
   Choose the project and funnel step

   And click “Next”.
3. 3
   Copy the address and save

   “Copy” next to “Webhook URL”, then “Save”.
4. 4
   Paste the address into Flexbe

   Settings → API → “Webhook for new event notifications” → “Add webhook”. Save and send a test submission.

Flexbe doesn't pass the website cookies, so the source and visit history won't be attached to the lead.

How to avoid duplicate and unwanted leads

Duplicate protection is a phone number check that keeps one submission from turning into two leads. On the “Webhook” step, three toggles handle this and unwanted leads:

• “Don't create duplicate leads” — if the same phone already submitted a form within the last few hours (a window of 1 to 12 hours), no new lead is created, and the form data is added as a comment to the lead found. In a new integration, the toggle is on and the window is 4 hours.
• “Delayed lead creation” — a delay of up to 5 minutes. Useful while the code on the website also catches the forms.
• “Receive leads only via this integration” — form capture by the website code in this project is turned off, so there are no double leads. If you turn the toggle off or delete the integration, capture by the code comes back as before.

Integration status: “Receiving leads” or “Waiting for a lead”

In the “Integrations” block, each row shows the builder and the website domain, the project, the status and the number of leads. A green “Receiving leads” dot means leads have already come in via the webhook. A yellow “Waiting for a lead” dot means there haven't been any yet. The pencil opens the settings, and the trash can deletes the integration — after that, remove the webhook in the builder too.

Read also: Website form to CRM: connect your forms without a developer, CRM for small business: how to never lose a single lead, CRM user permissions: how to add an employee and set access rights