ActionPipedriveUpdated September 2026

How do I list Pipedrive deals?

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

List Deals in Pipedrive — start free All 7 Pipedrive actions

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

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.

Triggered by

Apps that pair well as the trigger for List Deals.

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

Google Sheets → Pipedrive

2 Google Sheets triggers

HubSpot → Pipedrive

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Pipedrive returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Deals support batch operations?

Run List Deals inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Pipedrive's rate limits.

More actions