List Freshsales Contacts: 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, Last Name
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": 120,
    "total_pages": 5
  },
  "contacts": [
    {
      "id": 1,
      "email": "john@example.com",
      "last_name": "Doe",
      "first_name": "John"
    }
  ]
}

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

FAQ

Questions about List Freshsales Contacts.

What does the List Freshsales Contacts action do in Freshsales?

Paginated contacts with filters. For warehouse-sync workflows, use the updated-since filter for incremental pulls.

What inputs does List Freshsales Contacts require?

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

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