# Pipedrive

Nimbata's Pipedrive integration automatically sends call data to Pipedrive, so you can track leads, update deals, and keep your sales pipeline accurate. When a caller is not in Pipedrive yet, Nimbata creates the records you choose, such as a Person and a Note. When the caller already exists, it updates the fields you map. A workflow decides which calls are sent.

**Before you start**

- Permissions: Pipedrive, under Integrations, in your Nimbata role
- A Pipedrive account you can sign in to.
- The Nimbata project whose calls you want to send: the integration is set up per project.

## Connect Pipedrive

1. (1) **Open the Pipedrive integration**

   Go to **Integrations** and click **Go to integration** on the **Pipedrive** tile (1), or go straight to [Integrations > Pipedrive](https://app.nimbata.com/integrations/service/pipedrive).

   [The Pipedrive tile on the Integrations page, with Go to integration marked 1]

   *Open the Pipedrive tile (1).*

2. (1) **Connect your Pipedrive account**

   - Click **Connect** (1).
   - In the authorization pop-up, click **Allow and Install**.

   [The Pipedrive integration page before it is connected, with the Connect button marked 1]

   *Click Connect (1).*

## Configure Pipedrive

Each setup, such as **Pipedrive Settings 1**, has two sections: **Caller not found**, what Nimbata creates when the caller is not in Pipedrive, and **Caller found**, what it updates when they are. To send different calls to Pipedrive in different ways, click **Set up Pipedrive** to add another setup; each workflow picks the setup it sends.

1. **Map your fields**

   Map Nimbata fields to Pipedrive fields for two scenarios:

   - One for when the caller **is not found** in your CRM (**Caller not found**)
   - One for when they **already exist** (**Caller found**)

   Click **+ Add object** to add each record, or **Use Default Config** to fill in the recommended mapping.

   [The Pipedrive Caller not found section: Create a Person with Name and Phone mapped, and Create a Note with Add time and Content]

   *Caller not found: a new Person with its Name and Phone, then a Note.*

2. (1) **Choose how existing callers are matched**

   In the **Caller found** section, answer the two matching questions first:

   1. **Which entity to enrich** (1), when the Caller ID is found in more than one object: **Person**, **Lead** or **All**.
   2. **How to handle duplicates** (2), when the same Caller ID is found more than once in one object: **Handle first**, **Handle all** or **Ignore all**.

   [The Pipedrive Caller found section: the entity question with Person chosen, marked 1, and the duplicates question with Handle first chosen, marked 2]

   *Choose the entity to enrich (1) and how to handle duplicates (2).*

## Test the integration

1. **Send a test event**

   Click **Send Test and Save**, fill in the test values, including a **Caller ID**, and click **Send event**. If the Caller ID is already in Pipedrive, Nimbata runs your **Caller found** actions, otherwise your **Caller not found** actions. Review the test event in Pipedrive.

2. **Save the setup**

   Click **Save**. Calls start reaching Pipedrive once a workflow sends them (below).

## Send calls with a workflow

Which calls are sent is decided by a workflow with a Pipedrive action: a workflow that runs when a call ends, with no filter, sends every call, and its filters (for example call outcome or tracking number) narrow it down.

1. **Create a workflow**

   Go to **Workflows**, click **Create** and choose **From Scratch**. Keep the **Inbound Call** trigger with **Call Ends**, and add any filters you need.

2. (1) **Add the Pipedrive action**

   Click the **+** plus sign, select **Perform action**, and choose **Pipedrive** under **Integrations**. Pick your setup under **Select configuration** (1), then click **OK**.

   [The Pipedrive pop-up of the workflow builder, with the Pipedrive Settings 1 setup selected and marked 1]

   *Pick the Pipedrive setup to send (1), then click OK.*

3. (1) **Enable the workflow**

   Click **Enable** (1).

   [A workflow firing on Inbound Call, Call Ends, with a Pipedrive action sending Pipedrive Settings 1, and the Enable button marked 1]

   *The workflow sends every inbound call to Pipedrive when it ends. Click Enable (1).*

Detailed guide: [Create a workflow](https://help.nimbata.com/workflows/workflows#create-a-workflow)

## Check it worked

The Pipedrive page now shows the workflow that uses the integration. Place a test call to one of your tracking numbers: once it ends, the record appears in Pipedrive.

[The connected Pipedrive integration, used in 1 workflow, with Pipedrive Settings 1 used by the Pipedrive calls workflow]

*The page shows Used in 1 workflow, and the setup lists the workflow that sends it.*

🎉 Done! All calls that match your workflow criteria are automatically logged in Pipedrive.

## Troubleshooting

### The Pipedrive tile says Disconnected

Nimbata has lost its connection to Pipedrive. Your Pipedrive settings are saved, but nothing is sent until you reconnect: open the integration and click **Reconnect** in the red **Disconnected.** banner.

[The Pipedrive tile on the Integrations page with a red Disconnected badge]

*A disconnected integration shows a red Disconnected badge on its tile.*

### Send Test and Save is greyed out

- Connect Pipedrive first: the button stays off until the integration is connected.
- Map at least one field under **Caller not found** or **Caller found**.
- If the test answers "Please provide a valid caller id", fill in the **Caller ID** box in the test panel.

### Calls are not reaching Pipedrive

- Check that a workflow with a **Pipedrive** action is enabled, and that its filters let the call through.
- Check that the workflow's Pipedrive action uses the setup you configured, under **Select configuration**.
- Check that the Pipedrive tile does not say **Disconnected**.
- Send a test from **Send Test and Save** to see the error Pipedrive returns.