List Persons: Pipedrive action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Limit limit	string	Optional	Limit. e.g. "100"
Sort sort	options	Optional	Sort order. Pipedrive expects 'field ASC' or 'field DESC' — free-form values like 'DES' are rejected.

Sample request

{
  "limit": "100",
  "sort": "{{trigger.sort}}"
}

Returns

{
  "data": [
    {
      "id": 123,
      "name": "John Doe",
      "email": [
        {
          "value": "john@example.com"
        }
      ]
    }
  ],
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Persons.

What does the List Persons action do in Pipedrive?

Lists persons (contacts) from Pipedrive with filters for owner and update time. Used for CRM sync into your ESP or for cohort exports.

What inputs does List Persons require?

List Persons has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Pipedrive returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Persons support batch operations?

Yes. Run List Persons inside a Loop node to process arrays. Tiny Command handles Pipedrive's rate limits automatically so you don't have to throttle manually.

More actions