> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Pipedrive Voice AI Integration Guide

> Connect DialNexa voice AI with Pipedrive to qualify callers, update people and deals, log calls, and schedule the next sales activity.

The **Pipedrive voice AI integration** keeps every sales call tied to a person, deal, and next activity. It is a good fit for teams that manage daily work from the pipeline and want fewer calls to end without a clear follow-up.

<Warning>
  A catalog page describes a possible workflow. It does not confirm that a native Pipedrive connector is enabled in your workspace. Check **Integrations** in the DialNexa dashboard first. If Pipedrive is not listed, use a custom function, agent webhook, or external automation service.
</Warning>

## When to use the Pipedrive voice AI integration

Use Pipedrive when:

* Sales representatives use activities to manage their day.
* The agent needs the current person, organization, deal, or owner before routing.
* A completed call should add a note, disposition, or next activity.
* Pipeline stage changes follow clear, confirmed customer outcomes.

<Tip>
  **Best first workflow:** Match the caller to a person, log the call against the open deal, and schedule the next activity with the current owner.
</Tip>

## Before you begin

Prepare the following:

* A published DialNexa agent that has already passed a basic test call.
* Access to the DialNexa workspace **Integrations** page.
* A Pipedrive account with permission to read or update the required records.
* One test record that does not affect a live customer.
* A list of actions that can run automatically and actions that require human review.

## Choose how to connect Pipedrive

| Connection method                                   | Use it when                                                 | Important limit                                                             |
| --------------------------------------------------- | ----------------------------------------------------------- | --------------------------------------------------------------------------- |
| Workspace connector                                 | Pipedrive appears in your DialNexa **Integrations** page    | Available actions and authentication depend on your workspace               |
| [Custom function](/docs/agent-settings/custom-functions) | The agent needs Pipedrive data during the live conversation | Keep the request fast and return only the fields the agent needs            |
| [Agent webhook](/docs/api-access/agent-webhooks)         | Pipedrive should receive a result after the call            | Your endpoint must authenticate, retry safely, and prevent duplicate writes |
| External automation                                 | The workflow spans Pipedrive and several other systems      | Monitor the external workflow separately from the DialNexa call             |

## Build the Pipedrive voice AI workflow

1. Define the exact event that starts the action, such as a confirmed booking, qualified lead, support escalation, or completed call.
2. Choose the connection method from the table above.
3. Map caller identity, the DialNexa call ID, the verified outcome, and the destination record ID.
4. Add a condition so uncertain, sensitive, destructive, or high-value changes go to a human-owned queue.
5. Store the destination record URL or ID with the call result so your team can trace the handoff.
6. Test success, no-match, duplicate, permission-error, and timeout cases before using live traffic.

## Data to map between DialNexa and Pipedrive

* Person, organization, and deal IDs plus the current owner
* Normalized phone number, email, pipeline, stage, and open activity status
* Call ID, disposition, summary, qualification fields, and next step
* Activity type, subject, due date, due time, and assigned user

## High-value Pipedrive voice AI workflows

| Call outcome                         | Pipedrive result                                            | Human control                                    |
| ------------------------------------ | ----------------------------------------------------------- | ------------------------------------------------ |
| Inbound lead is qualified            | Create or update the person and add a deal when rules allow | Review duplicate people and organizations        |
| Prospect agrees to a follow-up       | Log the call and create the next activity                   | Let the owner adjust priority and timing         |
| Existing deal needs specialist help  | Add a note and assign an activity to the right user         | Keep deal ownership changes human-owned          |
| Prospect clearly accepts or declines | Suggest a stage update with the reason                      | Require review before marking a deal won or lost |

## Verify the Pipedrive integration

Run a test call and confirm that:

1. The workflow finds the intended Pipedrive record instead of creating a duplicate.
2. Only the approved fields change.
3. The DialNexa call ID is stored for traceability and retry protection.
4. A failed request creates a visible error or human-owned task.
5. The receiving owner can open the Pipedrive record and understand the next step without reading the full transcript.

## Troubleshoot Pipedrive integration issues

| Problem                                 | What to check                                                                                                                                     |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Pipedrive is not shown in the dashboard | Use a custom function, webhook, or external automation service, or [request the integration](/docs/dashboard-integrations/requesting-new-integrations) |
| Authentication fails                    | Reconnect the account and verify scopes, workspace ownership, and token expiry                                                                    |
| No matching record is found             | Normalize phone numbers and email addresses, then define a clear create-versus-review rule                                                        |
| Duplicate updates appear                | Use the DialNexa call ID as an idempotency key and make retries safe                                                                              |
| The live call becomes slow              | Move nonessential writes to a post-call webhook and keep live lookups small                                                                       |

## Related pages

* [DialNexa integrations overview](/docs/integrations/overview)
* [Connect dashboard integrations](/docs/dashboard-integrations/connecting-integrations)
* [Use integrations in agents](/docs/dashboard-integrations/using-integrations-in-agents)
* [Use integrations in workflows](/docs/dashboard-integrations/using-integrations-in-workflows)
* [Integration workflow tutorials](/docs/tutorials/integration-workflows)