- Integrations
- /
- Close
- /
- Actions
- /
- Search Leads
ActionCloseUpdated May 2026
How do I search Close leads?
Short answer: Drop the "Close → Search Leads" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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.
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
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.
ActionCreate 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.
ActionCreate 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.
ActionDelete 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.
ActionGet 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.
ActionList 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.
Send search leads from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.