Search 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
Search Query q	string	Required	Search across name, email, phone
Entity Type entities	string	Optional	Entity Type. e.g. "contact"

Sample request

{
  "q": "e.g. john@example.com",
  "entities": "contact"
}

Returns

{
  "contacts": {
    "contacts": [
      {
        "id": 1,
        "email": "john@example.com",
        "display_name": "John Doe"
      }
    ]
  }
}

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

FAQ

Questions about Search Freshsales Contacts.

What does the Search Freshsales Contacts action do in Freshsales?

Lookup by partial name, email, or other criteria. The standard "find before update" pattern for upsert workflows.

What inputs does Search Freshsales Contacts require?

Required: Search Query. Every input accepts a static value or a variable from any upstream node in your workflow.

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

Yes. Run Search 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