Update Activity
pipedrive.update_activity
ActionCRM & salesconnection required
Calls the Pipedrive API with the connection's credentials.
Change one activity with PATCH /api/v2/activities/{id} — this is also how an activity is marked done.
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
16 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 |
|---|---|---|---|---|---|
activity_id Pipedrive id of the activity to update. | string | Yes | — | — | — |
subject Title shown on the activity. | string | No | — | — | — |
type Key of the activity type, e.g. call, meeting, task. Read the keys from Pipedrive: List Activity Fields. | string | No | — | — | — |
due_date Day the activity is due, as YYYY-MM-DD. | string | No | — | matches \d{4}-\d{2}-\d{2} | 2026-01-31 |
due_time Time the activity is due, as HH:MM. | string | No | — | — | — |
duration How long the activity runs, as HH:MM. | string | No | — | — | — |
done Whether the activity is already completed. | boolean | No | — | — | — |
note Free-text note stored on the activity. | string | No | — | — | — |
location Where the activity happens. | string | No | — | — | — |
deal_id Id of the deal to book the activity against. | string | No | — | — | — |
lead_id UUID of the lead to book the activity against. | string | No | — | — | — |
person_id Id of the person the activity is with. | string | No | — | — | — |
org_id Id of the organization the activity is with. | string | No | — | — | — |
owner_id Id of the user who owns the record. | string | 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. Read the hashes with the matching Pipedrive: List * Fields node. | object | No | — | — | {"1a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d":"Enterprise"} |
- At least one of subject, type, due_date, due_time, duration, note, location, done, deal_id, lead_id, person_id, org_id, owner_id, fields, custom_fields must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"custom_fields": {
"1a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d": "Enterprise"
},
"due_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.
{}See Update Activity 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.