Add persons and deals to your Pipedrive pipeline. Connect your native Framer forms to Pipedrive in 30 seconds with zero client-side API key leaks.
For a small sales team on Pipedrive, the goal is simple: a contact form on the Framer site should put the person into Pipedrive without anyone copying and pasting. FramerSend creates a Pipedrive person for each submission, with the visitor's name, primary email and primary phone, using your personal API token from its server.
By default it creates a person only; switch on "Also create a Lead" and it adds a Pipedrive Lead linked to that person. It does not create deals or organizations. That keeps the setup to one token, and Pipedrive's own automations, where your plan has them, can take it from there. Because the token is stored on FramerSend's server, it never ends up in the published Framer site.
What gets created: A Pipedrive person created with POST /api/v2/persons (API v2; the v1 persons endpoint is out of support), owned by the user whose API token you use. Existing persons are not searched or updated.
| Framer form field | Pipedrive |
|---|---|
| name, or first + last name fields | Person nameIf the form has no name, the email is used as the name, then "New Lead". |
| email (or Email, E-mail, correo…) | Email (primary)Trimmed, with common domain typos corrected. |
| phone, mobile, tel or whatsapp | Phone (primary) |
| company, message and any other field | Not sentUse Pipedrive notes or another connector if you need the full message stored. |
Copy your personal API token
In Pipedrive open your profile menu → Personal preferences → API and copy the token. Persons will be created as this user.
Connect in the plugin or dashboard
In the FramerSend plugin inside Framer or Dashboard → 2. Connect CRM, choose Pipedrive, paste the token and click Test. Test reads /v1/users/me with the token in the x-api-token header, so it creates nothing.
Check the field names
Pipedrive only needs name, email and phone. If your inputs are named differently (for example "Full name" works, "Who are you" does not), rename them in Dashboard → 3. Field Mapping.
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.
Optional: also create a Lead
Set "Also create a Lead" to Yes on the connection. Each submission then adds a Lead in the Leads Inbox linked to the new person. The Lead title defaults to "{name} – Framer form"; change it in Lead title, using {name} and {email}. To open deals, use a Pipedrive automation on the new lead or person.
Invalid Pipedrive API Token.
Cause: Shown by Test when Pipedrive refuses the token, usually because it was regenerated.
Fix: Copy the current token from Personal preferences → API and update the connection.
Missing Pipedrive API Token
Cause: The token field was empty when Test was clicked.
Fix: Paste the token, then test again.
Pipedrive (…): …
Cause: Pipedrive refused the person; the HTTP status is in brackets and its JSON message follows the colon. A revoked token or a user without permission to add contacts are common causes.
Fix: Check the message on the failed row in Dashboard → 4. Logs, fix it in Pipedrive and click Retry.
Pipedrive: person saved, but creating the lead failed (…): …
Cause: "Also create a Lead" is on and Pipedrive refused the lead, for example because the token's user cannot use the Leads Inbox.
Fix: Check that the user behind the API token can create leads in Pipedrive, or set "Also create a Lead" back to No. Then use Retry on the failed row in Dashboard → 4. Logs.
Persons named after an email address
Cause: The form has no field FramerSend recognises as a name.
Fix: Name the input name or full_name, or map it to name in Field Mapping.
Domain not activated
Cause: With a paid plan, submissions from a custom domain must come from a domain listed on your license. Framer previews (framer.app, framer.website) always work.
Fix: Add the domain under Dashboard → 1. Setup Domains.
Less to configure. Zapier's Pipedrive templates usually create a person and then a deal in two actions. FramerSend creates the person with one token; you add the deal step in Pipedrive's own automations if you need it.
No per-lead tasks. Each Zapier action counts as a task. FramerSend has no submission limit.
Token in one place. Both approaches keep the token off your website. With FramerSend it sits next to the form's delivery log.
Where Zapier helps. If you need deals, organizations, custom fields or duplicate checks from the form itself, a Zap with several Pipedrive steps can do it today.
Full comparison: FramerSend vs Zapier
Zero code or third-party plugins required
Authenticate Pipedrive credentials in the FramerSend dashboard. We encrypt and store them securely.
Map your Framer form fields to Pipedrive 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 Pipedrive 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.
It always creates a person, and it can also create a Lead linked to that person when "Also create a Lead" is set to Yes. It does not create deals. Use a Pipedrive automation to turn leads into deals, or the Zapier or Make connector for a multi-step flow.
Yes. Each submission creates a new person because FramerSend does not search for an existing one. Merge duplicates in Pipedrive if they build up.
The user whose personal API token is on the connection.
Not with this connector. It sends name, email and phone only, and other answers such as company are not sent. If you need custom fields or an organization, use the Zapier or Make connector and add those steps there.
Yes. The Test button only reads /v1/users/me. The first real Framer submission creates the first person, which you can delete in Pipedrive afterwards.
No. Only name, email and phone are sent. If the message matters, a connector that keeps every answer, such as Salesforce (in Description) or Notion (in the page), is a better fit.
Sign up for a FramerSend account (or log in). Go to Connections → Add Connection → Pipedrive 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.