Skip to main content
OpenCX workflows authenticate to Pipedrive with two pieces of data: an and your . Both travel into the workflow action as inputs — there is no org-level connect screen today.
Pipedrive is in beta. Confirm with your OpenCX contact that the Update PipeDrive Lead action is enabled on your organization before you configure a workflow — otherwise the action will not appear in the flow builder’s node picker.

​
Generate credentials

1

Create a dedicated Pipedrive user (recommended)

Create a new Pipedrive user scoped to the pipelines OpenCX should touch. The API token inherits the user’s permissions — a narrowly-scoped user limits blast radius if the token leaks.
2

Generate an API token

Sign in as that user, open Personal preferences → API, and copy the token. Full URL: https://app.pipedrive.com/settings/api.
Anyone with the token can read and write every record the user can see. Treat it like a password.
3

Copy your company domain

Look at your Pipedrive URL. The first part — yourcompany in yourcompany.pipedrive.com — is the domain you need. Do not include .pipedrive.com or https://.
4

Store both somewhere safe

Drop both into your password manager or secret store. Every workflow node that touches Pipedrive expects them as inputs, so you will reuse them across flows.
OpenCX does not persist Pipedrive credentials at the organization level yet. Each workflow action reads the token and domain from its own configuration — rotating the token means updating every workflow that uses it.

​
Verify the connection

Before wiring credentials into a production workflow, smoke-test them:
1

Pick a throwaway lead

Open Pipedrive, create a test lead (or grab one you know is safe to touch), and copy its Lead ID from the URL.
2

Build a one-node workflow

In your OpenCX dashboard, create a workflow with a manual trigger and a single Update PipeDrive Lead node. Paste the API token, company domain, and the Lead ID.
3

Add one field update

Set fieldKey to title and value to anything (e.g. "OpenCX smoke test").
4

Run and confirm

Run the workflow. The action output should return success: true and the lead’s title should reflect the new value in Pipedrive. If it doesn’t, jump to Troubleshooting.

Update Lead Action

Full reference for the Update PipeDrive Lead workflow action.

Trigger workflows from Pipedrive

Wire Pipedrive automations into an OpenCX workflow.

Overview

Capabilities and patterns at a glance.

Troubleshooting

Credentials rejected, lead not found, field update errors.