Configure the action
Drop the node into your workflow
In the flow builder, add an
Update PipeDrive Lead node wherever you want the update to fire — usually after the AI has collected enough context.Paste your credentials
Fill PipeDrive API Token and Company Domain with the values you gathered in Connect.
Decide how to find the lead
If the workflow already has a Lead ID (from a Pipedrive webhook, for example), pass it in the Lead ID field. Otherwise fill Search Criteria with one or more
{ field, value } pairs.Declare your field updates
List the fields you want to write in Field Updates. Each entry is a
{ fieldKey, value } pair — use Pipedrive’s own field keys (title, value, expected_close_date) or the key of any custom field.Inputs reference
Lead ID
Lead ID
Optional. If set, the action skips the search entirely and PATCHes that lead. Use this when the Lead ID is already on your session or was passed in from a Pipedrive automation payload.
Search Criteria
Search Criteria
Optional, used only when Lead ID is empty. The first criterion’s value becomes the search term; is called with
exact_match=true on lead items. Stick to standard fields: phone, email, person_name, or org_name.Field Updates
Field Updates
Required. An array of
{ fieldKey, value } objects. Each fieldKey is Pipedrive’s exact field key — standard fields (title, value, expected_close_date) or the custom-field key you can see in Pipedrive’s field settings.Create If Not Found
Create If Not Found
Defaults to
false. When true and the search misses, the action creates a new lead using your Field Updates as its starting values. If you didn’t pass a title, OpenCX sets one from the first search criterion’s value (e.g. Lead - +15551234567).Skip Empty Values
Skip Empty Values
Defaults to
true. When true, fields whose value is null, undefined, or "" are dropped before the update — they never overwrite existing data in Pipedrive. Set to false only when you explicitly want to clear a field.Updating the deal value
Pipedrive stores thevalue field as an object with an amount and a currency. The action hides that detail when you pass a plain number — it auto-wraps 42 as { amount: 42, currency: "USD" }.
If your pipeline uses a different currency, pass the full object yourself:
3 and the API receives "3".
Output
| Key | Meaning |
|---|---|
success | true when the update or create landed; false if the action returned an error. |
leadId | The ID of the lead that was updated or created. |
wasCreated | true if the action created a new lead; false if it updated an existing one. |
updatedFields | Array of the fieldKeys that actually went into the request body. |
leadData | The full lead object returned by Pipedrive after the write. Use it to chain follow-up nodes. |
error | Error message if success is false. |
Good To Know
Per-call timeout
Per-call timeout
Each search, create, and update request has a hard 30-second timeout. Pipedrive is usually well under that, but flag slow runs if you see timeouts in your workflow run viewer.
Workflow-scoped credentials
Workflow-scoped credentials
The API token is read from the node’s own configuration every time the workflow runs — it is not stored at the organization level. Rotate a token and you will need to update every node that references it.
Errors surface as run failures
Errors surface as run failures
A bad token, a missing lead with
Create If Not Found disabled, or an all-empty update raises a runtime error. The workflow run fails on that node — handle it with a conditional branch if your flow needs to keep going.Related Documentation
Connect
Generate an API token and find your company domain.
Trigger workflows from Pipedrive
Pair this action with a Pipedrive automation that fires the workflow.
Overview
Capabilities and patterns at a glance.
Troubleshooting
Lead not found, empty updates, currency errors.