List Notes
pipedrive.list_notes
ActionCRM & salesconnection required
Calls the Pipedrive API with the connection's credentials.
Page through notes with GET /api/v1/notes, optionally only those on one deal, person, organization or lead.
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
11 fields, none 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 |
|---|---|---|---|---|---|
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 Only notes written by this user. | string | No | — | — | — |
start_date Only notes added on or after this date, as YYYY-MM-DD. | string | No | — | matches \d{4}-\d{2}-\d{2} | 2026-01-31 |
end_date Only notes added on or before this date, as YYYY-MM-DD. | string | No | — | matches \d{4}-\d{2}-\d{2} | 2026-01-31 |
sort Comma-separated ordering, e.g. add_time DESC. Sortable fields are id, user_id, deal_id, person_id, org_id, content, add_time and update_time. | string | No | — | — | — |
limit How many records to return in this page. Pipedrive caps a page at 500. | number | No | 100 | 1–500 | — |
start Offset of the first record to return. Feed the previous call's `next_start` output back in to walk the whole collection. | number | No | — | 0–1000000 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"end_date": "2026-01-31",
"limit": 100,
"start_date": "2026-01-31"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The records on this page, exactly as Pipedrive returned them. | array | — |
count How many records this page carried. | number | — |
next_cursor Feed back as the next call's `cursor`. Null on the last page, and always null on a v1 collection, which pages with `next_start` instead. | string | — |
next_start Feed back as the next call's `start`. Null on the last page, and always null on a v2 collection, which pages with `next_cursor` instead. | number | — |
more_items True when Pipedrive says another page exists. | boolean | — |
{
"count": 0,
"items": [],
"more_items": false,
"next_cursor": "",
"next_start": 0
}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.
- Pipedrive caps a page at 500 records and defaults to 100.
See List Notes 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.