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

# Pipedrive overview

> Keep Pipedrive leads current from OpenCX workflows, and trigger AI phone calls when new leads land in your pipeline.

OpenCX connects to Pipedrive through workflows. Update a <Tooltip tip="A sales record in Pipedrive that tracks a potential deal before it becomes a won or lost deal.">lead</Tooltip> as an AI conversation progresses, or have Pipedrive kick off an OpenCX workflow — most commonly an outbound AI phone call — the moment a new lead appears.

<Info>
  Pipedrive is currently in **beta**. Reach out to your OpenCX contact to enable the workflow action on your organization. There is no self-service connect screen today — [**Settings → Integrations**](https://platform.open.cx/settings/integrations) shows Pipedrive as "coming soon" until support enables it.
</Info>

## What you get

<AccordionGroup>
  <Accordion title="Keep your pipeline current as conversations close" icon="user-pen">
    When an AI conversation confirms a budget, a move-in date, or any detail your reps need, a workflow writes the value straight back to the matching Pipedrive lead. No CSV exports, no manual data entry, no duplicate records.
  </Accordion>

  <Accordion title="Trigger AI outbound calls when a lead lands" icon="phone-arrow-up-right">
    Pipedrive automation sends the new lead's phone, name, and custom fields into an OpenCX workflow. The workflow places an AI phone call with the lead's context already loaded — the agent greets them by name and works your script.
  </Accordion>

  <Accordion title="Reach leads by phone, email, person, or org name" icon="magnifying-glass">
    When you already have a <Tooltip tip="Pipedrive's UUID for a lead. Visible in the lead URL and returned by the Pipedrive API whenever a lead is created or updated.">Lead ID</Tooltip>, the workflow updates that lead directly. When you don't, OpenCX searches Pipedrive by phone number, email, person name, or org name.
  </Accordion>
</AccordionGroup>

## Pick your pattern

Most teams run both patterns side by side — Pipedrive drives the first touchpoint, OpenCX keeps the lead current from then on.

<Tabs>
  <Tab title="OpenCX updates Pipedrive">
    An AI workflow finishes a conversation and writes the outcome back to Pipedrive — stage, value, custom fields, or a fresh title. Use the `Update PipeDrive Lead` workflow action.

    <Card title="Update Lead Action" icon="user-round-pen" href="/integrations/pipedrive/update-lead-action">
      Configure the action, search by phone or email, update or create leads.
    </Card>
  </Tab>

  <Tab title="Pipedrive triggers OpenCX">
    A Pipedrive automation fires on "lead created" (or any other trigger) and POSTs the lead into an OpenCX <Tooltip tip="An OpenCX workflow trigger that receives an HTTP POST body against a predefined schema. Gives you typed suggestions inside the flow builder instead of a free-form blob.">Form Submit trigger</Tooltip>. The workflow then places an outbound AI phone call, runs a custom branch, or whatever else you need.

    <Card title="Trigger workflows from Pipedrive" icon="bolt" href="/integrations/pipedrive/webhook-trigger">
      Wire a Pipedrive automation into an OpenCX workflow with a typed payload.
    </Card>
  </Tab>
</Tabs>

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="Connect" icon="plug" href="/integrations/pipedrive/connect">
    Grab your Pipedrive API token and company domain.
  </Card>

  <Card title="Update Lead Action" icon="user-round-pen" href="/integrations/pipedrive/update-lead-action">
    Push conversation outcomes into Pipedrive leads.
  </Card>

  <Card title="Trigger workflows from Pipedrive" icon="bolt" href="/integrations/pipedrive/webhook-trigger">
    Start an OpenCX workflow from a Pipedrive automation.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/integrations/pipedrive/troubleshooting">
    Lead not found, phone-format errors, empty update fields.
  </Card>
</CardGroup>