- Integrations
- /
- Freshdesk
- /
- Actions
- /
- List Contacts
ActionFreshdeskUpdated May 2026
How do I list Freshdesk contacts?
Short answer: Drop the "Freshdesk → List Contacts" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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. e.g. "1" |
Per Page per_page | string | Optional | Per Page. e.g. "30" |
Filter by Email email | string | Optional | Exact email match |
Sample request
{"page": "1","per_page": "30","email": "e.g. user@example.com"}
Returns
[{"id": 1001,"name": "John Doe","email": "john@example.com","active": true}]
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Contacts.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Contacts.
What does the List Contacts action do in Freshdesk?
Lists Freshdesk contacts (first page). For full sync use the search endpoint with pagination or filters; this action is best for spot-checks and pickers.
What inputs does List Contacts require?
List 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 Freshdesk 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 Contacts support batch operations?
Yes. Run List Contacts inside a Loop node to process arrays. Tiny Command handles Freshdesk's rate limits automatically so you don't have to throttle manually.
More actions
Other Freshdesk actions.
Action
Add Note to Ticket
Adds a note (private or public) or a reply to an existing Freshdesk ticket. Used for AI-summary notes, automated status updates, or piping context from external systems.
ActionCreate Company
Creates a new company (B2B customer account) in Freshdesk. Used to mirror your CRM accounts into the helpdesk so contacts auto-link.
ActionCreate Contact
Creates a new contact (end-customer) in Freshdesk with name, email, phone, company, and tags. Used to provision contacts before ticket creation.
ActionCreate Ticket
Creates a new support ticket in Freshdesk with requester, subject, description, source, priority, status, group, and agent. The entry point for converting external alerts or forms into trackable tickets.
ActionDelete Contact
Deletes a Freshdesk contact by ID. Note that this hides the contact rather than permanently removing them, so their tickets are preserved.
ActionDelete Ticket
Deletes a Freshdesk ticket by ID. Tickets move to trash for 30 days before permanent deletion, so this is recoverable in the short term.
Send list contacts from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.