Create leads in Bitrix24 CRM. Connect your native Framer forms to Bitrix24 in 30 seconds with zero client-side API key leaks.
Bitrix24 bundles CRM, tasks and chat for a lot of sales teams, and leads are where new enquiries start. FramerSend creates a Bitrix24 lead for every Framer form submission through an inbound webhook, so a contact or quote request from your Framer site appears in the CRM's lead list, ready for your usual assignment and follow-up rules.
The lead carries a title that starts with "Form:" and the visitor's name, the first and last name, the email and phone as work contacts, the company name and the message as comments. Every answer also stays in FramerSend's log for that submission. Setup takes one inbound webhook with CRM permission, and the Test button checks that permission for you.
What gets created: A new CRM lead, created with crm.lead.add through your inbound webhook. The title is "Form: " followed by the visitor's name, the email when there is no name, or "submission" when there is neither. Existing leads and contacts are not matched or updated.
| Framer form field | Bitrix24 |
|---|---|
| name or full_name | NAME and the lead TITLENAME gets the first word; the full name follows "Form: " in the title. A separate first name field is used for NAME when present. |
| Rest of the name, or a last name field | LAST_NAME |
| email (also Email, E-mail, correo…) | EMAIL, type WORKTrimmed and typo-corrected. Also used in the title when the form has no name. Not required; when it is empty no EMAIL is sent. |
| phone, mobile, tel… | PHONE, type WORKSent as typed. |
| company or organization | COMPANY_TITLE |
| message, notes, comments… | COMMENTSAngle brackets are escaped so the text shows as typed. |
| Every other field | Not sentRead them on the submission in Dashboard → 4. Logs. |
Create an inbound webhook in Bitrix24
In your Bitrix24 portal, open the developer resources, add an inbound webhook and tick the CRM permission. Save it and copy the webhook URL, which looks like https://yourportal.bitrix24.com/rest/1/abc123xyz/.
Paste the whole URL into Base URL
FramerSend reads the user ID (the number after /rest/) and the token from it, and those values win over the separate fields. You can also type the portal address and fill User ID and Webhook Token yourself. A missing https:// is added.
Connect Bitrix24 in the plugin or dashboard
Search for Bitrix24 in the FramerSend plugin inside Framer, or use Dashboard → 2. Connect CRM, then click Test. Test calls profile with the webhook, then lists the lead fields to confirm CRM access. On success it says which Bitrix24 user it connected as.
Paste the webhook URL into Framer
In Framer, select the form, open Form → Send to → Add… → Webhook, paste the FramerSend webhook URL (https://www.framersend.com/api/submit/ followed by your form ID) and publish the site.
Check the first lead
Submit the form once and open the leads list in Bitrix24. The new lead's title starts with "Form:", which makes Framer leads easy to filter.
Missing Bitrix24 Base URL
Cause: Shown by Test when Base URL is empty.
Fix: Paste the full inbound webhook URL.
Could not reach your Bitrix24 portal. Check the Base URL (e.g. https://company.bitrix24.com).
Cause: The address does not resolve or the portal did not answer.
Fix: Copy the portal address from your browser's address bar, or the full webhook URL.
Bitrix24 rejected the User ID / Webhook Token. Copy both from your inbound webhook (Developer resources → Other → Inbound webhook), or paste the full webhook URL into Base URL.
Cause: The user ID and token do not belong to an active inbound webhook.
Fix: Paste the whole webhook URL into Base URL so both values come from the same webhook.
Bitrix24 REST API not found at this Base URL (HTTP …). Use your portal address, e.g. https://company.bitrix24.com.
Cause: The address answered, but not with the Bitrix24 REST API.
Fix: Use the portal address, not a marketing site or a page path.
Webhook works, but it has no CRM permission. Edit the inbound webhook in Bitrix24 and tick "CRM (crm)".
Cause: The webhook is valid but cannot create leads.
Fix: Edit the webhook, add the CRM permission, save, and click Test again.
Bitrix24: …
Cause: Bitrix24 refused the lead during a real submission and its own error description follows, even when the portal answered with HTTP 200. A deleted webhook or removed CRM permission is the usual reason.
Fix: Run Test on the connection, fix what it reports, then click Retry on the failed row in Dashboard → 4. Logs.
A webhook instead of an app login. FramerSend needs only an inbound webhook URL, which you can revoke in Bitrix24 at any time.
No tasks per lead. Each Zapier action uses a task. FramerSend has no submission limit.
The usual lead fields, no mapping screen. Name, email, phone, company and the message land on the lead without any setup. Other custom lead fields need an automation inside Bitrix24 or another tool.
Built for routing, not enrichment. Once the lead exists, Bitrix24's own automation can assign it, notify a manager or convert it. FramerSend's job ends at creating the lead.
Full comparison: FramerSend vs Zapier
Zero code or third-party plugins required
Authenticate Bitrix24 credentials in the FramerSend dashboard. We encrypt and store them securely.
Map your Framer form fields to Bitrix24 properties using our visual dropdown UI.
Paste your webhook URL into your Framer form under Send to → Webhook and publish. Submissions flow automatically.
Every plan includes Bitrix24 and 100+ other connectors. Pay monthly, yearly, or once. Try it free for 14 days, no card needed.
For one Framer site
For freelancers and small studios
For agencies with many client sites
14-day free trial of every connector, no card needed. Form fields and FramerSend file uploads stay free forever with a free account.
Start freeEncrypted API vault, real-time delivery, and unlimited submissions
Automatically capture and route leads from your Framer forms.
Trigger automated workflows when form submissions arrive.
Keep all your form data in one place, synced in real-time.
A lead, through crm.lead.add. Contacts, companies and deals are not created; convert the lead in Bitrix24.
Yes. The phone goes to PHONE, the company to COMPANY_TITLE and the message to COMMENTS, next to the title, name and email. Other answers are kept on the submission in FramerSend's Logs.
Yes. A URL in the form https://portal/rest/1/token/ is accepted in Base URL, and its user ID and token are used instead of the separate fields.
Yes, as long as the portal's REST API is reachable from the internet at the address you enter.
Yes. Each submission creates a new lead. Use Bitrix24's duplicate control if you want them merged.
It calls the webhook's profile method to confirm the user ID and token, then reads the lead field list to confirm CRM permission. Nothing is created, and on success it names the Bitrix24 user the webhook belongs to.
Sign up for a FramerSend account (or log in). Go to Connections → Add Connection → Bitrix24 and add your credentials. They are stored server-side and never exposed in your Framer site, which only gets a public form URL.
Yes, all API credentials are encrypted at rest. The client-side code in Framer only exposes a public Form ID, keeping your private keys entirely secure.
No. FramerSend provides unlimited form submissions across all license tiers so your live website forms never get blocked during high-traffic spikes.