# Create Pipedrive people and leads from qualified leads URL: https://useembers.com/help/integrations/pipedrive/ Category: Integrations Plan: Solo and above Updated: 2026-10-28 Last verified: 2026-10-28 > Connect one Pipedrive company with the Embers app or an API token, map your own Person fields, and get a Person, a Lead, and a note when a lead qualifies. Embers can keep Pipedrive in step with your LinkedIn pipeline. When a lead qualifies, Embers creates a Person (linked to their organization), adds a Lead to your Leads Inbox, and attaches one note on why the lead matters. A person you already have is updated instead. > **Warning: Solo and above, administrators only** > > Integrations require Solo or above, and only a workspace admin can connect Pipedrive or change what it receives. One Pipedrive company per Embers workspace. ## Before you start - A Pipedrive user in the company you want leads in. Embers acts as that user, whichever way you connect. - Pipedrive Persons have no LinkedIn field, and the built-in job title only exists when the company has contact sync turned on. Create **Person custom fields** in Pipedrive for what you want filled, such as the LinkedIn profile URL and the job title, before you map. Embers never creates fields for you, which matters on Pipedrive Lite, where a company gets 30 custom fields in all. ## Connect Pipedrive ### Open the Pipedrive page Open **Integrations** in the sidebar (`/integrations`) and choose **Pipedrive**. ### Connect with the app or an API token **Pipedrive app** Choose **Connect Pipedrive**. Pipedrive's consent screen opens and installs the Embers app for you, with access to contacts (people, organizations, their notes and fields) and leads (leads and lead labels), nothing else. If you cancel there, nothing is connected. When you approve, you return to Embers. The app button appears only when Embers has it configured. An API token always works. **API token** In Pipedrive, open **Settings**, then **Personal preferences**, then **API**, and copy your personal API token. If you do not see **API** there, your Pipedrive permission set does not include it; ask a Pipedrive admin. Paste the token into Embers. Embers checks it with Pipedrive before storing it, so a token Pipedrive refuses fails here and nothing is saved. It is stored encrypted and never shown again. A token belongs to one user in one company, and generating a new one in Pipedrive retires the old one. Either way, Embers reads your user, your company, your Person fields, and your lead labels. Pipedrive search then runs as you, so Embers only finds people your Pipedrive user can see. ### Map fields Embers pre-selects any Person field whose name says LinkedIn for the LinkedIn profile URL, and any field whose name matches another Embers field, such as "Job title". Review the matches, change any of them, and save the mapping. Details are below. ### Choose what to create and send Set the four options in the next section, then choose which events to send. New leads are sent by default; a known lead engaging again, changing status, or having a [company change](/help/leads/company-changes/) can update the same Person too. ### Send a test A test checks the connection and re-reads your Person fields. It writes nothing to Pipedrive. If a field you mapped has been deleted or changed type, the test fails and the install pauses until you re-map. ## Map Embers fields to your Person fields Embers writes the name, email, phone, and organization to Pipedrive's own Person fields. Everything else goes into your company's **custom** Person fields, and only the ones you map. A field left unmapped is not sent. | An Embers value that is | Fills a Pipedrive field of type | | --- | --- | | Text or a URL, such as the LinkedIn profile URL or job title | Text (cut to 255 characters), Autocomplete, or Large text | | A number, such as the score | Numerical | | A date | Date | | A choice or a yes/no | Single option or Multiple options, using only an option the field already has (matched by name), or a text field | Each Embers field fills one Pipedrive field, and each Pipedrive field takes one Embers field. > **Tip: Map the LinkedIn profile URL** > > It is not required, but it is how Embers recognises a person it has not linked yet and who has no email. Without it, such a lead can only be found again through Embers' own link. Reconnecting the same Pipedrive company keeps your mapping and settings. Connecting a different company resets them. ## What Embers writes **A new Person** gets: | Pipedrive | Where it comes from | | --- | --- | | Name | The lead's full name. A lead with no name fails on its own. | | Email | The stored email, marked work and primary, when Embers already has one | | Phone | The stored phone, marked work and primary, when Embers already has one | | Organization | The organization named exactly as the lead's company, created when there is none | | Your custom fields | The mapping | **A Person you already have**, found by any of the ways below, gets only the mapped custom fields. Its name, emails, phones, organization, and owner are left alone. Empty values are never sent, so nothing you filled in is wiped. Email and phone are sent only on a paid plan, and never looked up for Pipedrive: [contact details](/help/outreach/lead-enrichment-and-contact-info/) are not part of the [free trial](/help/account-and-billing/free-trial/). Four settings control the rest: - **Create a lead** (on): a Person Embers creates also gets a Lead in your Leads Inbox, titled with their name and company, linked to the Person and organization, and owned by the connected user. A person who was already in Pipedrive gets no Lead. Each person gets a Lead once. - **Lead label** (none): one of your Pipedrive lead labels to put on that Lead. - **Link organization** (on): find or create the organization and link the new Person to it. - **Add a note** (on): the first time Embers sends a person, it adds one note with the score, the ICP verdict, the top signals, the reason for the match, the LinkedIn profile, the headline, the company's size and industry, and a link to the lead in Embers. The note goes on the Lead when there is one, otherwise on the Person. A note Pipedrive refuses does not stop the delivery. > **Warning: Leads over your plan limit are discarded** > > Pipedrive caps leads plus deals per company by plan. A Lead created over that limit is discarded by Pipedrive without an error, so Embers cannot tell and records the delivery as sent. The Person and note are still written. If your Leads Inbox stops filling, check your company's limit in Pipedrive, or turn off **Create a lead**. Embers does not create deals, write organization fields beyond the name, or read anything back from Pipedrive, such as a Lead converted or a deal won. ## How an existing person is found In this order, the first match wins: 1. **The Person Embers linked before** in this company. If it was deleted or merged away, Embers drops the link and keeps looking. 2. **A Person with the lead's email**, when Embers has one. 3. **A Person with the lead's LinkedIn profile URL** in the field you mapped it to. 4. **Nobody**: Embers creates the Person and remembers it, so every later send and retry updates that same record. Two limits come from Pipedrive. A person your Pipedrive user cannot see is not found and is created again. And Pipedrive's search can take a few seconds to show a person just created elsewhere. If you end up with two records, merge them in Pipedrive. ## Who gets delivered Pipedrive has its own [delivery rules](/help/integrations/delivery-rules/): a minimum lead score, ICP matches only, the sources that count, and titles and industries to exclude. A lead the rules hold back writes nothing to Pipedrive and is listed in the delivery log as held back, where you can send it anyway. To send leads now rather than wait for the next qualifying event, push them with [Send to](/help/leads/send-to-destination/). ## Send the leads you already have Pipedrive gets a lead when it first qualifies, so leads Embers found before you connected never reach it on their own. **Send existing leads** sends every qualified lead that is not linked to a Person in this company yet, best score first. Your rules apply, anyone already sent is skipped, so running it again only sends what is missing, and each lead is written exactly like a new one. It is paced to Pipedrive's request limits, so a large backlog takes a while. It cannot start while delivery is off or paused, or while a run is going. ## Pipedrive's API budget Pipedrive gives each company a daily budget of API tokens, shared by every tool the company has connected. Embers spends it too, and keeps to 8 requests every 2 seconds per connection. A new lead costs about 45 tokens: the email search 20, the Person 5, the Lead 10, and the note 10, plus 20 for an organization search the first time a company name comes up. Pipedrive emails your admins as the budget runs low. When it runs out, Pipedrive refuses requests until it resets and Embers retries them. ## Delivery log, retries, and pauses The delivery log keeps 30 days of deliveries, each linking to the Person and, when one was made, the Lead. Failed, blocked, and held-back rows can be retried. Rate limits, Pipedrive outages, and network errors are retried: the first attempt plus seven retries, from 30 seconds out to about 6.3 days. A lead Pipedrive refuses for its own values, a lead with no name, or a Pipedrive plan limit fails on its own, and Embers keeps sending the others. These pause the install. Pipedrive pauses send no email, so check the page: - **Reconnect Pipedrive**: Pipedrive no longer accepts the connection. The token was regenerated or the app was revoked. Embers renews an app connection on its own and tries once more before pausing. - **The Pipedrive account is inactive**: the company's Pipedrive subscription ended. - **A missing permission**: the connected user lost a permission Embers needs. - **Re-map Pipedrive fields**: a mapped Person field was deleted or changed type. Saving a valid mapping clears the pause. - **"Pipedrive paused after 5 leads in a row were rejected"**: five leads failed with none delivered in between, counted from the last resume, so something is turning every lead away. The message names the last reason. Fix the cause, then resume. [Pipedrive delivery is paused](/help/troubleshooting/pipedrive-delivery-paused/) walks through each one. **Uninstalling the Embers app in Pipedrive** disconnects it in Embers too, and the page offers **Connect Pipedrive** again. **Disconnecting from Embers** stops all writes, forgets the token, and for an app connection also uninstalls the app for that user in Pipedrive. Everything already in Pipedrive stays. ## Troubleshooting **The API token is refused.** It was copied incompletely or regenerated since. Copy it again from **Personal preferences**, **API**. **No field is offered for the LinkedIn URL or job title.** Your company has no custom Person field of a compatible type. Create one in Pipedrive, then reopen the mapping. **A choice field stays empty.** The Pipedrive field has no option with that name. Add the option in Pipedrive. **The same person appears twice.** Embers could not see the first record (visibility or search lag), or the lead had no email and the LinkedIn URL was not mapped. Merge them in Pipedrive and map the LinkedIn URL. **People arrive but no Lead.** The person was already in Pipedrive, **Create a lead** is off, or the company is over its leads-plus-deals limit. ## Related - [Fix Pipedrive delivery when it is paused](/help/troubleshooting/pipedrive-delivery-paused/): What each pause means and how to resume. - [Control which leads reach each destination](/help/integrations/delivery-rules/): Decide which leads are worth a Pipedrive record. - [Send a lead to a destination](/help/leads/send-to-destination/): Push the leads you pick, now. - [Reveal a lead's email and phone](/help/outreach/lead-enrichment-and-contact-info/): Where email and phone come from. ## Frequently asked questions **Does Embers create deals in Pipedrive?** No. Embers creates or updates a Person, can add a Lead to the Leads Inbox for a person it creates, and adds one note. Convert the Lead to a deal in Pipedrive when you are ready. **Does Embers add custom fields to my Pipedrive company?** No. Embers never creates, edits, or deletes a Pipedrive field. You create the Person fields you want filled and map Embers fields to them. **Will a test create anything in Pipedrive?** No. A test checks the connection and re-reads your Person fields. It writes nothing. **Why did a Lead not appear in the Leads Inbox?** Either the person was already in Pipedrive, and Embers only adds a Lead for a person it creates, or your company is over its leads-plus-deals limit, where Pipedrive discards new leads without an error. **Can I connect two Pipedrive companies?** No. One Pipedrive company per Embers workspace. An agency connects each client workspace to that client's company separately.