# Pipedrive (/integrations/pipedrive)

<Callout title="Beta">
  The Pipedrive integration is in beta. Ask the Sendable team to turn it on for your workspace.
</Callout>

Once Pipedrive is connected, each lead you send becomes a person in Pipedrive, linked to its organization, with its whole history in notes: the signal that found it, the campaigns it joined, each invitation and profile visit, and its LinkedIn conversation.

## Before you start [#before-you-start]

- You are an **owner** of your Sendable workspace.
- You can install apps in your Pipedrive company. Sendable works with what this Pipedrive user can see: the people it adds belong to them.
- Any Pipedrive plan works. Pipedrive limits how many API calls a company makes each day: see [Pipedrive's daily API limit](#pipedrives-daily-api-limit).

## Connect Pipedrive [#connect-pipedrive]

<Steps>
<Step>

### Open the Pipedrive integration [#open-the-pipedrive-integration]

Go to **Settings > Integrations > Pipedrive** and click **Connect**. Pipedrive only shows in the settings once the beta is on for your workspace.

</Step>
<Step>

### Allow Sendable in Pipedrive [#allow-sendable-in-pipedrive]

Pipedrive shows the access Sendable needs (see [Permissions](#permissions)). Click **Allow and install**.

</Step>
<Step>

### Back in Sendable [#back-in-sendable]

You land on the Pipedrive page with the message **Pipedrive connected**. Nothing is sent to Pipedrive yet: you choose the leads first, then start the import.

</Step>
</Steps>

Only an owner can connect Pipedrive. Other members see the page but can't change anything.

## Start the import [#start-the-import]

Pick the leads to send. Each choice shows how many leads it sends:

| Choice          | Leads sent                                                      |
| --------------- | --------------------------------------------------------------- |
| Every lead      | Every lead, as soon as it is in Sendable                        |
| Once contacted  | Leads your team contacted on LinkedIn or talked to in the inbox |
| Once they reply | Leads who replied                                               |
| Once interested | Leads marked Interested                                         |

Then click the button, for example **Import 1,250 leads**. Nothing reaches Pipedrive before that, not even new activity.

**Leads in Pipedrive** shows the progress, for example **400 / 1,250**, and updates on its own. Then the card reads **Up to date**: new leads and new activity reach Pipedrive within minutes.

- **Stop** pauses the import. People already in Pipedrive and new activity keep syncing.
- **Import 300 leads** (or **Resume**) starts it again.
- **Resync**, once up to date, sends the leads missing from Pipedrive right away, including the ones Pipedrive refused.

A Sendable workspace connects one Pipedrive company, and every team sends its leads to it. It can connect Attio or HubSpot at the same time: each CRM syncs on its own.

## Change the leads to send [#change-the-leads-to-send]

Click **Stop** first if an import is running. Changing **Leads to send** or **Teams** sends nothing right away: if the new choice adds leads, the card shows **120 leads to import** with an **Import 120 leads** button. Leads already in Pipedrive stay and keep syncing, whatever you choose.

With several teams, **Teams** limits Pipedrive to the teams you pick. Leave it empty for every team. Leads of a team you remove stay in Pipedrive but stop syncing.

## What Sendable sends [#what-sendable-sends]

### People and organizations [#people-and-organizations]

Every lead you chose to send is sent, except rejected ones (see below).

- Sendable looks for the person in Pipedrive by email, then by LinkedIn profile, and creates it if none is found.
- It looks for the organization by name and creates it if none is found, with the company's website. Among several organizations of the same name, it picks the one with the company's website.
- It fills the name, email, job title, LinkedIn profile, phone number and organization **only when they are empty in Pipedrive**. Values already filled in Pipedrive are never overwritten. A phone number is sent only with its country code, for example **+33 6 12 34 56 78**.
- A new email or phone becomes the person's primary one; the other emails and phones you added in Pipedrive stay.
- When you edit one of these values in Sendable, Sendable updates it in Pipedrive too, as long as it was Sendable that wrote it and nobody changed it in Pipedrive since. A value someone changed in Pipedrive stays as it is.
- Renaming or archiving a campaign or a signal, renaming an inbox label or removing a lead from a campaign updates the Sendable fields below within minutes.

Pipedrive has no LinkedIn field on people: Sendable writes the profile to your **LinkedIn** person field when you have one (also **LinkedIn URL** or **LinkedIn profile**), and adds a **LinkedIn** field otherwise. The job title goes to Pipedrive's own **Job title** when your company uses contact sync, otherwise to a **Job title** field that Sendable adds.

Each Sendable custom field with a value becomes a person field, named after it with **(Sendable)** at the end, for example **Industry (Sendable)**. It follows the value in Sendable. If you rename the custom field in Sendable, a new field with the new name is added in Pipedrive.

The **Notes** of a lead are added as a note on the person, updated when you edit them in Sendable.

### Sendable fields [#sendable-fields]

Sendable adds these person fields in Pipedrive, so you can filter and segment on them. They are kept up to date.

| Field                     | What it holds                                                                    |
| ------------------------- | -------------------------------------------------------------------------------- |
| Sendable status           | New, Contacted, Replied or Interested                                            |
| Last LinkedIn interaction | The day of the last LinkedIn action, message or reply between your team and them |
| Sendable lead             | A link that opens this person in Sendable                                        |
| Sendable labels           | The inbox labels of this person's LinkedIn conversations                         |
| Sendable campaigns        | The Sendable campaigns this person is in                                         |
| Sendable signals          | The Sendable signals that found this person                                      |

**Sendable labels**, **Sendable campaigns** and **Sendable signals** appear in Pipedrive with the first lead that has one.

If you rename one of these fields or change its type in Pipedrive, Sendable stops writing to it and adds a new one with the original name.

### Activity [#activity]

Activity is added as notes on the person, also shown on its organization, at the date it happened. Notes don't appear in your Activities list or in your activity goals.

| Note          | What it contains                                                                                          |
| ------------- | --------------------------------------------------------------------------------------------------------- |
| Conversation  | One note per LinkedIn conversation, with every message sent or received, updated as the conversation goes |
| Campaign step | Invitation sent (with its note), invitation accepted, profile visited, post liked, invitation withdrawn   |
| Lead update   | Found by a signal (with why it matches), added to a campaign, marked Interested or no longer Interested   |

Images, voice messages, videos and attachments are mentioned in the conversation but not uploaded. Group conversations are not sent.

When a lead is sent for the first time, its whole history comes with it.

<Callout type="warn" title="Every conversation is sent">
  Pipedrive receives the LinkedIn conversations of every account in the workspace, whatever the
  **Inbox access** of each member in Sendable. Anyone who can see these people in Pipedrive can read
  them.
</Callout>

### Rejected and deleted leads [#rejected-and-deleted-leads]

A lead is rejected when it has been excluded or blacklisted everywhere it appears and has no conversation. Rejected leads are not sent.

When a lead already in Pipedrive becomes rejected, or is deleted in Sendable:

- if Sendable created the person, the person is **deleted** from Pipedrive, with anything added to it there;
- if the person was already in Pipedrive, it stays, with its notes, and is no longer updated.

## Skip people already in Pipedrive [#skip-people-already-in-pipedrive]

A signal can skip the people you already have in Pipedrive, so you don't prospect your customers or your open deals again. In the signal's **Agent** step, under **Exclude**, in the **CRM** section, turn on **Already in Pipedrive**. The switch shows once Pipedrive is connected.

- Sendable compares the LinkedIn profile of each person found with the LinkedIn field of the people in your Pipedrive company. People without a LinkedIn profile in Pipedrive can't be matched.
- People Sendable itself added to Pipedrive are not skipped: the other rules, like **Already contacted**, take care of them.
- Skipped people count as **Already in your CRM** in the signal's **Not matched** details and use no credit.

The first time a signal uses it, Sendable reads the people of your Pipedrive company, which takes a few minutes for a large company. People added in Pipedrive, or whose LinkedIn profile changes, are picked up within minutes.

## Open a lead in Pipedrive [#open-a-lead-in-pipedrive]

In Sendable, the lead sheet shows a Pipedrive button once the lead is in Pipedrive: **Open in Pipedrive** opens the person in a new tab.

If Pipedrive refused the lead, the button is orange and reads **Not in Pipedrive**, with the reason. It opens the Pipedrive settings.

From Pipedrive, the **Sendable lead** field of the person and the **Open in Sendable** link of each note open the lead in Sendable.

## Pipedrive's daily API limit [#pipedrives-daily-api-limit]

Pipedrive limits how many API calls a company makes each day, depending on its plan and number of seats. Every tool connected to your Pipedrive shares this budget. Sendable never uses all of it: once a quarter of the day's budget is left, it pauses and leaves the rest to your other tools.

During the pause, the Pipedrive page reads **Pipedrive's daily API limit is reached** and the import **Sync paused**. Sendable tries again every hour and resumes on its own once Pipedrive renews the budget. New leads and activity wait, nothing is lost.

A large import can take several days on a small plan: about 300 leads a day for one seat of the Lite plan, more with each seat or a higher plan. Pipedrive emails your admins when the company's budget runs low.

## Leads Pipedrive refused [#leads-pipedrive-refused]

Pipedrive sometimes refuses a lead, for example when a value doesn't match a rule of your Pipedrive company. The **Leads in Pipedrive** card then shows how many leads are **not in Pipedrive**, and owners see each lead with the reason Pipedrive gave.

Fix the value in Sendable and the lead is sent again on its own. If the problem was on the Pipedrive side, an owner clicks **Resync** once it is solved.

## Disconnect Pipedrive [#disconnect-pipedrive]

An owner can click **Disconnect** on the Pipedrive page. Sendable stops sending leads and activity and uninstalls itself from Pipedrive. What is already in Pipedrive stays there.

If you connect the same Pipedrive company again later, Sendable first checks what is still there. People still in Pipedrive stay linked to their leads, so nothing is sent twice. Leads whose person was deleted in Pipedrive while Sendable was disconnected are sent again. As after a first connection, you choose the leads and start the import yourself.

If you reconnect while Sendable is still deleting the people it added, the deletion stops.

To also remove what Sendable added, tick **Also delete the people and companies Sendable added to Pipedrive** before you click **Disconnect and delete**. Sendable deletes every person it created in Pipedrive, then the organizations it created, unless a person or a deal is still linked to them, and uninstalls itself last. What you already had in Pipedrive stays.

## Changes made in Pipedrive [#changes-made-in-pipedrive]

- When you delete a person in Pipedrive, Sendable doesn't add it back, even if the lead changes in Sendable. Reconnecting Pipedrive is the only exception: it sends again the leads whose person is gone.
- When you merge two people in Pipedrive, Sendable keeps syncing the merged person. If one of them was yours, the merged person stays yours: Sendable never deletes it, not even with **Disconnect and delete**.

Pipedrive tells Sendable about the people that the Pipedrive user who connected Sendable can see.

Sendable doesn't bring values edited in Pipedrive back into Sendable.

## Permissions [#permissions]

Sendable asks Pipedrive for access to:

- contacts (people and organizations), to find, create and update them, and to add notes;
- contact fields, to add the Sendable fields;
- webhooks, to be told when a person is deleted, merged or changes LinkedIn profile.

## Troubleshooting [#troubleshooting]

| You see                                               | What to do                                                                                                                                                         |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Sendable lost access to your Pipedrive company        | Someone uninstalled Sendable from Pipedrive, or it went unused for 60 days. Owners also get an email. An owner clicks **Reconnect**, then starts the import again. |
| Pipedrive's daily API limit is reached                | Nothing to do: Sendable resumes on its own. See [Pipedrive's daily API limit](#pipedrives-daily-api-limit).                                                        |
| Pipedrive sync is failing                             | Sendable couldn't reach Pipedrive for a while. It retries on its own every few minutes; contact the Sendable team if it lasts.                                     |
| Only an owner of your workspace can connect Pipedrive | Ask an owner of your Sendable workspace to connect it.                                                                                                             |
| Pipedrive could not be connected                      | Start again. If it keeps failing, contact the Sendable team.                                                                                                       |
| Pipedrive connection cancelled                        | You clicked **Cancel** in Pipedrive. Start again.                                                                                                                  |
| Pipedrive is not available for your workspace yet     | The beta is not on for your workspace. Ask the Sendable team.                                                                                                      |
| A value is missing on a person                        | Pipedrive refused it, for example an invalid email. Sendable sends the person without it.                                                                          |

Reconnecting with a **different** Pipedrive company starts from scratch: nothing is carried over from the previous one.