Zoho logo

Search Leads (Zoho CRM)

Zoho CRM → Search Leads (Zoho CRM)

POST/v1/zoho-search-leads
texau__zoho-search-leadscrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/zoho-search-leads
{
  "email": "[email protected]",
  "mobile_number": "sample-value",
  "word": "sample-value",
  "criteria": "sample-value",
  "limit": 1
}
200 Accepted
{
  "ok": true,
  "data": {
    "lead_id": "rec_4f3a91",
    "full_name": "sample",
    "first_name": "sample",
    "last_name": "sample",
    "company": "sample",
    "email": "[email protected]",
    "mobile_number": "sample",
    "lead_status": "valid",
    "lead_source": "sample",
    "industry": "sample",
    "rating": "sample",
    "website": "https://acme.com",
    "address": "sample",
    "city": "sample",
    "state": "sample",
    "country": 1,
    "description": "sample",
    "is_converted": "sample",
    "owner": "sample",
    "created_by_name": "sample",
    "modified_by_name": "sample",
    "created_time": "sample",
    "modified_time": "sample",
    "last_activity_time": "sample",
    "record_status": "valid"
  }
}

Search for lead records using an email, phone number, a generic word, or specific criteria.

Install

Add search leads (zoho crm) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__zoho-search-leads

When to use this.

The "Search Leads (Zoho CRM)" action enables users to efficiently locate lead records within Zoho CRM by utilizing various search parameters such as email addresses, phone numbers, specific keywords, or advanced criteria. Key input parameters include an optional email and phone number for direct searches, a mandatory word for keyword searches, and an optional criteria string that allows for complex queries using logical operators. Users can also specify a limit on the number of results returned, which must be a multiple of 25. The action outputs comprehensive lead information, including lead ID, full name, contact details, lead status, source, industry, and timestamps for creation and modification, among others. This functionality is particularly useful for sales teams looking to quickly identify and manage leads based on specific attributes or conditions, making it an essential tool in the CRM category for enhancing lead management and sales efficiency.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Search Leads (Zoho CRM)

Try it

Search by email address.

Search by phone number.

Search by a specific word across indexed text fields.

Search using logical operators. Format: ((API_Name:operator:value)). Example: ((Company:equals:ABC)). Note: 'equals' behaves like 'contains' for standard text fields. You can use a maximum of 10 criteria.

Enter the number of leads to search (must be multiple of 25)

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • lead_id
    Lead Id
    text
  • full_name
    Full Name
    nullabletext
  • first_name
    First Name
    text
  • last_name
    Last Name
    text
  • company
    Company
    text
  • email
    Email
    text
  • mobile_number
    Mobile Number
    text
  • lead_status
    Lead Status
    nullabletext
  • lead_source
    Lead Source
    nullabletext
  • industry
    Industry
    nullabletext
  • rating
    Rating
    nullabletext
  • website
    Website
    nullabletext
  • address
    Address
    nullabletext
  • city
    City
    nullabletext
  • state
    State
    nullabletext
  • country
    Country
    nullabletext
  • description
    Description
    nullabletext
  • is_converted
    Is Converted
    nullabletext
  • owner
    Owner
    nullabletext
  • created_by_name
    Created By Name
    nullabletext
  • modified_by_name
    Modified By Name
    nullabletext
  • created_time
    Created Time
    nullabletext
  • modified_time
    Modified Time
    nullabletext
  • last_activity_time
    Last Activity Time
    nullabletext
  • record_status
    Record Status
    nullabletext

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/zoho-search-leads. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/zoho-search-leads
curl -X POST 'https://v3-api.texau.com/api/v1/zoho-search-leads' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"email":"[email protected]","mobile_number":"sample-value","word":"sample-value","criteria":"sample-value","limit":1}'
200 Accepted
{
  "ok": true,
  "data": {
    "lead_id": "rec_4f3a91",
    "full_name": "sample",
    "first_name": "sample",
    "last_name": "sample",
    "company": "sample",
    "email": "[email protected]",
    "mobile_number": "sample",
    "lead_status": "valid",
    "lead_source": "sample",
    "industry": "sample",
    "rating": "sample",
    "website": "https://acme.com",
    "address": "sample",
    "city": "sample",
    "state": "sample",
    "country": 1,
    "description": "sample",
    "is_converted": "sample",
    "owner": "sample",
    "created_by_name": "sample",
    "modified_by_name": "sample",
    "created_time": "sample",
    "modified_time": "sample",
    "last_activity_time": "sample",
    "record_status": "valid"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Search Leads (Zoho CRM)→Get Account by ID (Zoho CRM)→Delete Account (Zoho CRM)

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → search leads (zoho crm) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Search Leads (Zoho CRM)Zoho CRM action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limit100 / min
  • Per-day limit2,000 / day
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Light tier

Pricing tier on /pricing. Per-action credit cost is private.

Related

More Zoho CRM actions.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__zoho crm-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Search Leads (Zoho CRM) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.

Start free →Read the API docs