Update Lead
pipedrive.update_lead
ActionCRM & salesconnection required
Calls the Pipedrive API with the connection's credentials.
Change one lead with PATCH /api/v1/leads/{id}, including archiving it by setting is_archived.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Pipedrive
- Secret shape
- the Pipedrive API token, or {"api_token": "…"}
- Config it needs
- company_domain
- Resolved by
- config.connection_id, else node.connection_id
Configuration
12 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
lead_id Pipedrive id of the lead to update — a UUID. | string | Yes | — | — | — |
title Name of the lead. | string | No | — | — | — |
owner_id Id of the user who owns the record. | string | No | — | — | — |
person_id Id of the person the lead is for. | string | No | — | — | — |
organization_id Id of the organization the lead is for. | string | No | — | — | — |
amount Value of the lead. Sent with `currency` as Pipedrive's {amount, currency} object, so both are needed together. | number | No | — | ≥ 0 | — |
currency ISO 4217 currency code for `amount`, e.g. USD. | string | Conditional | — | only with amount | — |
expected_close_date When the lead is expected to close, as YYYY-MM-DD. | string | No | — | matches \d{4}-\d{2}-\d{2} | 2026-01-31 |
was_seen Whether someone has already opened the lead. | boolean | No | — | — | — |
fields Any other Pipedrive body field, as a JSON object. Use this for anything the named fields above do not cover; the named fields win on a clash. | object | No | — | — | {"visible_to":3} |
custom_fields Custom fields to write, as a JSON object keyed by the field's 40-character hash. Leads are a v1 resource, so these are sent as top-level keys rather than nested under custom_fields. | object | No | — | — | {"1a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d":"Webinar"} |
is_archived Archive the lead when true, restore it to the inbox when false. | boolean | No | — | — | — |
- At least one of title, owner_id, person_id, organization_id, amount, currency, expected_close_date, was_seen, is_archived, fields, custom_fields must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"custom_fields": {
"1a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d": "Webinar"
},
"expected_close_date": "2026-01-31",
"fields": {
"visible_to": 3
}
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}Notes
- This resource has no API v2 endpoint yet, so the call goes to /api/v1 and pages with start/next_start rather than a cursor.
See Update Lead run in a workflow.
In a technical demo we add the Pipedrive connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.