Search Everything
pipedrive.search_items
ActionCRM & salesconnection required
Calls the Pipedrive API with the connection's credentials.
Search across several record types at once with GET /api/v2/itemSearch. Each match is {result_score, item}, and `item.type` says what was found.
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
8 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 |
|---|---|---|---|---|---|
term What to search for. Pipedrive needs at least two characters, or one with exact_match on. | string | Yes | — | ≥ 1 characters | — |
item_types Comma-separated types to search: deal, person, organization, product, lead, file, mail_attachment or project. Defaults to all of them. | string | No | — | — | — |
fields Comma-separated fields to search in, e.g. name,email. Defaults to every searchable field for the type. | string | No | — | — | — |
exact_match Only return records whose field matches the term exactly. | boolean | No | — | — | — |
search_for_related_items Also return the deals and people related to each match. | boolean | No | — | — | — |
include_fields Comma-separated extra fields to add, e.g. deal.cc_email, person.picture, product.price. | string | No | — | — | — |
limit How many matches to return in this page. Item search caps a page at 100. | number | No | 100 | 1–100 | — |
cursor Paging marker from the previous call's `next_cursor` output. Leave empty for the first page. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"limit": 100
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The matches on this page. | array | — |
items[].result_score Pipedrive's relevance score for this match. | number | — |
items[].item The matched record itself. | object | — |
count How many matches this page carried. | number | — |
next_cursor Feed back as the next call's `cursor`; null on the last page. | string | — |
more_items True when another page of matches exists. | boolean | — |
{
"count": 0,
"items": [
{
"item": {},
"result_score": 0
}
],
"more_items": false,
"next_cursor": ""
}Notes
- Item search caps a page at 100 records rather than the usual 500.
See Search Everything 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.