Start free
ActionCloseUpdated June 2026

How do I search Close leads?

Short answer: You can search leads in Close by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Close Search Leads action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 9 Close actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Search Query
query
stringOptionalClose lead-query syntax. Leave blank to return all leads.
Limit
_limit
stringOptionalLimit. 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.

Triggered by

Apps that pair well as the trigger for Search Leads.

Any of these apps can fire this action as part of a workflow.

Gmail → Close
1 Gmail triggers
Slack → Close
13 Slack triggers
Google Sheets → Close
2 Google Sheets triggers
HubSpot → Close
18 HubSpot triggers
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. TinyCommand handles Close's rate limits automatically so you don't have to throttle manually.
More actions

Other Close actions.

Action
Create Lead
Creates a new lead (company-level record) in Close CRM with contacts, addresses, custom fields. Close's lead-first model means each company is one lead, with multiple contacts nested. The standard hook for "B2B form submission → push to Close" sync workflows.
Action
Create Opportunity
Creates a sales opportunity tied to a lead with value, expected close date, status, pipeline. Useful for "auto-create opportunity when lead reaches qualification score" workflows.
Action
Create Task
Creates a follow-up task for a sales rep tied to a lead with due date and notes. Useful for "deal stagnant for N days → create follow-up task for the AE" hygiene automation.
Action
Delete Lead
Hard-deletes a lead and all associated contacts, activities, opportunities. Irreversible. For GDPR right-to-erasure compliance workflows; for soft removal that preserves activity history, change the lead status to "Archived" instead.
Action
Get Lead
Returns a lead by ID with contacts, custom fields, opportunities, and recent activities. The standard lookup for enrichment workflows or for round-trip operations that need the current lead state.
Action
List Leads
Paginated leads with filters by status, custom fields, recently updated. For sync workflows that mirror Close into a warehouse or BI dashboard, paginate with the date_updated filter for incremental pulls.