List Freshsales Deals: Freshsales 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
Page page	string	Optional	Page number (starts at 1)
Sort By sort	options	Optional	Sort By. Options: Updated At, Created At, Amount
Sort Order sort_type	options	Optional	Sort Order. Options: Descending, Ascending

Sample request

{
  "page": "1",
  "sort": "{{trigger.sort}}",
  "sort_type": "{{trigger.sort_type}}"
}

Returns

{
  "meta": {
    "total": 45,
    "total_pages": 3
  },
  "deals": [
    {
      "id": 1,
      "name": "Enterprise Contract",
      "amount": 10000,
      "deal_stage_id": 2
    }
  ]
}

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

FAQ

Questions about List Freshsales Deals.

What does the List Freshsales Deals action do in Freshsales?

Paginated deals with filters by stage, owner, value, recently updated. For pipeline-reporting workflows that aggregate by stage or by owner.

What inputs does List Freshsales Deals require?

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

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

More actions