Pipedrive
Every lead from your landing pages, waiting in Pipedrive's Leads Inbox
Connect Pipedrive and each lead from a published Baker Form becomes a person, a lead and, when the Form asks for a company, an organization in your Pipedrive Leads Inbox, with the fields you choose, including campaign tracking. Baker also reads your pipelines, deals and custom fields to answer whether leads arrive, carry their tracking and get worked. It never edits or deletes an existing record.
- Leads into Pipedrive
- Campaign tracking on every lead
- Is the pipeline moving?
- Did my lead arrive?
- Lead ads into Pipedrive too
- Built by
- Baker
- Category
- CRM and email
- Plan
- Every plan
- Connects by
- Signing in
- Updated
- November 21, 2026
How it works
From connecting to publishing, in three steps
- 1
Connect Pipedrive
In Brain → Integrations, press Connect on the Pipedrive card, sign in to Pipedrive and allow Baker. A client can do it from a setup link.
- 2
Ask for the Form you need
In a chat, ask Baker for a Form that sends its leads to Pipedrive. Baker maps the fields and shows you the Form before anything goes live.
- 3
Publish
Press Publish. From then on each lead lands in your Leads Inbox, and each submission in Baker says whether Pipedrive received it.
What Baker does
Everything Baker does with Pipedrive
-
Leads into Pipedrive
Each Form submission creates a person, a lead and, when the Form asks for a company, an organization in Pipedrive, linked together, with the Form's answers in the fields you choose.
-
Campaign tracking on every lead
Baker finds the custom fields that hold click ids and UTM values, so each lead says which campaign and ad brought it.
-
Is the pipeline moving?
Ask Baker how many deals sit in each stage, for how long, and how many have no owner, using your team's own stage names.
-
Did my lead arrive?
Ask Baker whether a named lead reached Pipedrive, or which leads came in today with their tracking.
-
Lead ads into Pipedrive too
Leads from Meta, LinkedIn and Google Ads lead forms can be sent to Pipedrive the same way, checked every few minutes once you publish.
You approve
Nothing changes in Pipedrive until you press Publish
Baker prepares every change in a chat and shows it to you. It applies only when someone on your team who may publish presses Publish, and if you discard the chat, nothing applies.
Data and permissions
What Baker reads and what it can change
Exactly what Baker uses from your account, when and why. Baker asks only for the permissions this needs.
| What | Baker | When | Why |
|---|---|---|---|
| People and organizations | Changes | All the time | Each lead from a published Form creates a new person and, when mapped, an organization. Baker never edits or deletes existing ones. |
| Leads in your Leads Inbox | Changes | All the time | Each lead from a published Form creates a lead linked to its person and organization. |
| Deals, pipelines and stages | Reads | When you ask | To report how many deals sit in each stage and for how long. |
| Custom fields on deals, leads, people and organizations | Reads | When you ask | To map your Form into the right fields and find the ones that hold campaign tracking. Pipedrive's permission also allows adding fields; Baker does not. |
| Activities, users and recent changes | Reads | When you ask | To tell you whether leads have an owner and how deals moved. |
| Searching people and leads by their details | Reads | When you ask | To answer whether one lead reached Pipedrive. |
What you need
- A Pipedrive account, and a Pipedrive user in it who can install apps.
- An admin or member role in Baker to connect it. A client can connect it from a setup link instead.
- For campaign tracking on leads, custom fields in Pipedrive to hold it. Baker tells you when there are none.
What Baker's team switches on
- Sending leads from Meta lead ads into Pipedrive needs lead access, which Baker's team switches on for your company.
- Ask in Requests in Baker, or write to support@withbaker.com.
Frequently asked questions
Why don't my Form leads appear as deals?
Baker creates leads, which Pipedrive keeps in its Leads Inbox. A lead becomes a deal when someone on your team converts it.
What if the lead's email is already in Pipedrive?
Baker creates a new person for every lead, so a visitor who fills the Form in twice appears twice.
Can Baker read my Pipedrive automations?
No. Pipedrive offers no way for apps to read its automations, so Baker cannot tell you what they do.
What happens to my data if I disconnect?
People, organizations and leads Baker created stay in Pipedrive. Baker deletes its sign-in and keeps the Form answers it collected for 90 days.
Keep learning
- Connect Pipedrive to Baker Connect your Pipedrive account, send your Forms' leads to its Leads Inbox, and disconnect it, with what happens to your data on each side.
- Add a form that sends leads to your CRM Create a Form with Baker, choose where its leads go, from HubSpot to a Google Sheet or your inbox, and put it live on your landing pages.
- Send a test lead and check it arrived Prove a Form works end to end, from your live landing page to your CRM, sheet or inbox, and read what Baker says about each submission.
Used together with
- HubSpotBaker's Forms send every lead to the HubSpot form you pick, put your HubSpot forms and calendars on landing pages, and read the deals your ads bring.
- GoHighLevelBaker's Forms turn each lead into a GoHighLevel contact, business and opportunity, and put your GoHighLevel calendars and forms on landing pages.
- ActiveCampaignBaker's Forms send each lead to ActiveCampaign as a tagged contact, and Baker reads your campaigns, automations and deals to report on them.
- Zapier and webhooksSend each lead from a Baker Form to a Zapier Zap, to any web address as a webhook, or to an email inbox. No account to connect.