Search GoHighLevel Contacts: GoHighLevel 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
Location ID locationId	string	Required	The GoHighLevel sub-account to search within.
Search Query query	string	Optional	Email, phone, or name to search by. Free-text match against contact fields.
Limit limit	number	Optional	Max number of contacts to return (1–100).

Sample request

{
  "locationId": "ve9EPM428h8vShlRW1KT",
  "query": "jane@example.com or +15551234567 or Jane Smith",
  "limit": "20"
}

Returns

{
  "total": 1,
  "contacts": [
    {
      "id": "ocQHyuzHvysMo5N5VsXc",
      "email": "jane@example.com",
      "phone": "+15551234567",
      "lastName": "Smith",
      "firstName": "Jane"
    }
  ]
}

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

FAQ

Questions about Search GoHighLevel Contacts.

What does the Search GoHighLevel Contacts action do in GoHighLevel?

Lookup by email, phone, name, or tag. The standard "find before update" dedupe pattern for upsert workflows.

What inputs does Search GoHighLevel Contacts require?

Required: Location ID. 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 GoHighLevel 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 GoHighLevel Contacts support batch operations?

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

More actions