Update Note
pipedrive.update_note
ActionCRM & salesconnection required
Calls the Pipedrive API with the connection's credentials.
Change one note with PUT /api/v1/notes/{id}. Notes are still a v1 resource, so this is a PUT rather than the v2 PATCH.
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
9 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 |
|---|---|---|---|---|---|
note_id Pipedrive id of the note to update. | string | Yes | — | — | — |
content New body for the note, as HTML. | string | No | — | — | — |
deal_id Id of the deal to pin the note to. | string | No | — | — | — |
person_id Id of the person to pin the note to. | string | No | — | — | — |
org_id Id of the organization to pin the note to. | string | No | — | — | — |
lead_id UUID of the lead to pin the note to. | string | No | — | — | — |
project_id Id of the project to pin the note to. | string | No | — | — | — |
user_id Id of the user the note is attributed to. | 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} |
- At least one of content, user_id, deal_id, person_id, org_id, lead_id, project_id, fields must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"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 Note 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.