List Deals: 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
Status status	options	Optional	Status. Options: All (not deleted), Open, Won, Lost
Limit limit	string	Optional	Limit. e.g. "100"
Sort sort	string	Optional	Sort. Example: update_time DESC

Sample request

{
  "status": "{{trigger.status}}",
  "limit": "100",
  "sort": "e.g. update_time DESC"
}

Returns

{
  "data": [
    {
      "id": 1,
      "title": "Enterprise Deal",
      "value": 15000,
      "stage_id": 3
    }
  ],
  "success": true
}

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

FAQ

Questions about List Deals.

What does the List Deals action do in Pipedrive?

Lists deals from Pipedrive with filters for owner, stage, status (open/won/lost), and update time. Used for pipeline reports, forecasting, and warehouse exports.

What inputs does List Deals require?

List Deals 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 Deals support batch operations?

Yes. Run List Deals 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