Search Leads: Close 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	Close lead-query syntax. Leave blank to return all leads.
Limit _limit	string	Optional	Limit. e.g. "10"

Sample request

{
  "query": "company:\"Acme\"",
  "_limit": "10"
}

Returns

{
  "data": [
    {
      "id": "lead_abc123",
      "display_name": "Acme Inc"
    }
  ],
  "total_results": 5
}

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

FAQ

Questions about Search Leads.

What does the Search Leads action do in Close?

Search by Close's query language (status:active company:"Acme" etc.). Returns matching leads with relevance ranking. The standard "find before update" pattern and the workhorse for ad-hoc rep lookups.

What inputs does Search Leads require?

Search Leads 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 Close 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 Leads support batch operations?

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

More actions