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.

Connect Pipedrive

1. 1Open the Pipedrive integration

   Go to Integrations and click Go to integration on the Pipedrive tile (1), or go straight to Integrations > Pipedrive.

   Integrations

   Pipedrive

   Sync your call activity automatically and view all information directly within the CRM.

   Go to integration1

2. 1Connect your Pipedrive account

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

   Pipedrive

   Sync your call activity automatically and view all information directly within the CRM.

   Connect1

   Set up Pipedrive

   Pipedrive Settings 1

   Caller not found

   0 actions configured

   Caller found

   0 actions configured

   Send Test and Save

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.

   Caller not found

   Choose what to create when the caller is not already in Pipedrive.

   Create

   Person✕

   Name

   Nimbata Lead✕✕

   Phone

   nCaller ID✕✕

   Create

   Note✕

   Add time

   nCall Start Time✕✕

   Content

   Tracking Source:✕nConfigured Tracking Source✕✕

   Add objectUse Default Config

2. 1Choose 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.

   Caller found

   Choose what to update when the caller already exists in Pipedrive.

   If a Caller ID is found in multiple objects, which entity should be enriched?

   PersonLeadAll

   1

   When the same Caller ID is found multiple times within the same object, how would you like our app to handle the call event?

   Handle firstHandle allIgnore all

   2

   Add objectUse Default Config

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. 1Add 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.

   PipedriveConfigure

   ✕

   Pipedrive Settings 1×✕1

   OK

3. 1Enable the workflow

   Click Enable (1).

   Pipedrive callsWorkflow is valid.

   Enable1

   Trigger Enrollment

   Inbound CallOutbound CallForm SubmissionSMS Received

   A customer calls your tracking number

   Fires whenCall StartsCall EndsUser Updates Property

   Action group1

   PipedrivePipedrive Settings 1✕

   Add another action

   Finish

Detailed guide: 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.

🎉 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.

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.