Zoho logo

Search Deals (Zoho CRM)

Zoho CRM → Search Deals (Zoho CRM)

POST/v1/zoho-search-deals
texau__zoho-search-dealscrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/zoho-search-deals
{
  "word": "sample-value",
  "criteria": "sample-value",
  "email": "[email protected]",
  "mobile_number": "sample-value",
  "limit": 1
}
200 Accepted
{
  "ok": true,
  "data": {
    "deal_id": "rec_4f3a91",
    "deal_name": "sample",
    "stage": "sample",
    "amount": "sample",
    "probability": "sample",
    "expected_revenue": "sample",
    "closing_date": "sample",
    "contact_id": "rec_4f3a91",
    "contact_name": "sample",
    "account_id": 1,
    "account_name": 1,
    "deal_type": "sample",
    "next_step": "sample",
    "lead_source": "sample",
    "campaign_source": "sample",
    "description": "sample",
    "pipeline": "sample",
    "owner_id": "rec_4f3a91",
    "owner": "sample",
    "created_by_id": "rec_4f3a91",
    "created_by_name": "sample",
    "modified_by_id": "rec_4f3a91",
    "modified_by_name": "sample",
    "created_time": "sample",
    "modified_time": "sample"
  }
}

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

Install

Add search deals (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-deals

When to use this.

The "zoho-search-deals" action enables users to efficiently search for deal records within Zoho CRM using a variety of criteria, including generic keywords, specific logical conditions, associated email addresses, or phone numbers. Key input parameters include "word" for broad searches, "criteria" for advanced filtering, and optional "email" and "phone" fields to pinpoint deals linked to specific contacts. Users can also set a "limit" to control the number of results returned, ensuring manageable output. The action outputs a comprehensive set of deal-related data, including deal ID, name, stage, amount, probability, expected revenue, and associated contact and account details. This functionality is particularly useful for sales teams seeking to track and manage deals effectively, making it a vital tool in customer relationship management (CRM) workflows.

Try it

Run a sample request.

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

Search Deals (Zoho CRM)

Try it

Search by a specific word across indexed text fields.

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

Search by associated email address.

Search by associated phone number.

Enter the number of deals 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
  • deal_id
    Deal Id
    nullabletext
  • deal_name
    Deal Name
    text
  • stage
    Stage
    text
  • amount
    Amount
    text
  • probability
    Probability
    nullabletext
  • expected_revenue
    Expected Revenue
    nullabletext
  • closing_date
    Closing Date
    text
  • contact_id
    Contact Id
    nullabletext
  • contact_name
    Contact Name
    nullabletext
  • account_id
    Account Id
    nullabletext
  • account_name
    Account Name
    nullabletext
  • deal_type
    Deal Type
    nullabletext
  • next_step
    Next Step
    nullabletext
  • lead_source
    Lead Source
    nullabletext
  • campaign_source
    Campaign Source
    nullabletext
  • description
    Description
    nullabletext
  • pipeline
    Pipeline
    nullabletext
  • owner_id
    Owner Id
    nullabletext
  • owner
    Owner
    nullabletext
  • created_by_id
    Created By Id
    nullabletext
  • created_by_name
    Created By Name
    nullabletext
  • modified_by_id
    Modified By Id
    nullabletext
  • modified_by_name
    Modified By Name
    nullabletext
  • created_time
    Created Time
    nullabletext
  • modified_time
    Modified Time
    nullabletext

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/zoho-search-deals
curl -X POST 'https://v3-api.texau.com/api/v1/zoho-search-deals' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"word":"sample-value","criteria":"sample-value","email":"[email protected]","mobile_number":"sample-value","limit":1}'
200 Accepted
{
  "ok": true,
  "data": {
    "deal_id": "rec_4f3a91",
    "deal_name": "sample",
    "stage": "sample",
    "amount": "sample",
    "probability": "sample",
    "expected_revenue": "sample",
    "closing_date": "sample",
    "contact_id": "rec_4f3a91",
    "contact_name": "sample",
    "account_id": 1,
    "account_name": 1,
    "deal_type": "sample",
    "next_step": "sample",
    "lead_source": "sample",
    "campaign_source": "sample",
    "description": "sample",
    "pipeline": "sample",
    "owner_id": "rec_4f3a91",
    "owner": "sample",
    "created_by_id": "rec_4f3a91",
    "created_by_name": "sample",
    "modified_by_id": "rec_4f3a91",
    "modified_by_name": "sample",
    "created_time": "sample",
    "modified_time": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Search Deals (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 deals (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 Deals (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 Deals (Zoho CRM) in 60 seconds.

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

Start free →Read the API docs