Search Contacts: HubSpot 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 query	string	Optional	Full-text search across default searchable properties
Limit limit	string	Optional	Max results to return (max 100)
Properties properties	string	Optional	Comma-separated property names to include in results

Sample request

{
  "query": "e.g. john@example.com",
  "limit": "10",
  "properties": "e.g. email,firstname,lastname,company"
}

Returns

{
  "total": 1,
  "results": [
    {
      "id": "501",
      "properties": {
        "email": "john@example.com",
        "firstname": "John"
      }
    }
  ]
}

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

FAQ

Questions about Search Contacts.

What does the Search Contacts action do in HubSpot?

Searches for contacts in HubSpot CRM using filters (groups of property + operator + value). The de-facto upsert lookup: search first, then create or update.

What inputs does Search Contacts require?

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

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

More actions