Start free
ActionPipedriveUpdated June 2026

How do I list Pipedrive persons (contacts)?

Short answer: You can list persons in Pipedrive by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Pipedrive List Persons action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Persons in Pipedrive — start free All 7 Pipedrive actions
List Persons in Pipedrive — start free
Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Limit
limit
stringOptionalLimit. e.g. "100"
Sort
sort
optionsOptionalSort 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.

Triggered by

Apps that pair well as the trigger for List Persons.

Any of these apps can fire this action as part of a workflow.

Gmail → Pipedrive
1 Gmail triggers
Slack → Pipedrive
13 Slack triggers
Google Sheets → Pipedrive
2 Google Sheets triggers
HubSpot → Pipedrive
18 HubSpot triggers
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. TinyCommand handles Pipedrive's rate limits automatically so you don't have to throttle manually.
More actions

Other Pipedrive actions.

Action
Create Deal
Creates a new deal in the Pipedrive sales pipeline with title, value, currency, person, organization, stage, expected close date, and owner. The entry point for converting qualified leads into pipeline.
Action
Create Person
Creates a new person (contact) in Pipedrive with name, email, phone, organization, owner, and any custom fields. Used to push inbound leads into the CRM.
Action
Get Deal
Retrieves a Pipedrive deal by ID with title, value, stage, person, organization, owner, and custom fields. The standard read after a trigger fires with an ID.
Action
Get Person
Returns a Pipedrive person by ID with their emails, phones, organization, owner, and custom fields. Used to enrich trigger payloads or render contact UI.
Action
List Deals
Lists deals from Pipedrive with filters for owner, stage, status (open/won/lost), and update time. Used for pipeline reports, forecasting, and warehouse exports.
Action
Update Deal
Updates an existing Pipedrive deal: title, value, stage, status, expected close date, owner, or custom fields. Only the fields you pass are changed.
List Persons in Pipedrive — start free