Zoho logo

Get Deal by ID (Zoho CRM)

Zoho CRMGet Deal by ID (Zoho CRM)

POST/v1/zoho-get-deal-by-id
texau__zoho-get-deal-by-idcrm
cURL · api.texau.app
84ms
POST/v1/zoho-get-deal-by-id
{
  "deal_id": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "deal_id": "rec_4f3a91",
    "deal_name": "sample",
    "account_id": 1,
    "account_name": 1,
    "contact_id": "rec_4f3a91",
    "contact_name": "sample",
    "stage": "sample",
    "amount": 1,
    "expected_revenue": 1,
    "probability": 1,
    "closing_date": "sample",
    "type": "sample",
    "lead_source": "sample",
    "campaign_source": "sample",
    "next_step": "sample",
    "description": "sample",
    "owner_id": "rec_4f3a91",
    "owner_name": "sample",
    "owner_email": "[email protected]",
    "created_by_id": "rec_4f3a91",
    "created_by_name": "sample",
    "modified_by_id": "rec_4f3a91",
    "modified_by_name": "sample",
    "created_time": "sample",
    "modified_time": "sample",
    "stage_modified_time": "sample",
    "last_activity_time": "sample",
    "overall_sales_duration": 1,
    "sales_cycle_duration": 1,
    "reason_for_loss": "sample",
    "record_status": "valid",
    "is_locked": true
  }
}

Retrieve the full details of a specific deal using its unique Zoho Record ID.

Install

Add get deal by id (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-get-deal-by-id

When to use this.

The "Get Deal by ID" action in Zoho CRM allows users to retrieve comprehensive details of a specific deal using its unique Zoho Record ID. This action requires a single input parameter, the "deal_id" (string), which identifies the deal to be fetched. Upon execution, it returns a wealth of information, including the deal name, associated account and contact details, financial metrics like amount and expected revenue, and various timestamps related to creation and modification. The output fields encompass diverse semantic types such as id, text, number, date, and email, ensuring a robust data structure for integration. This action is particularly useful for sales teams and CRM administrators who need to access detailed deal information for reporting, analysis, or customer engagement strategies, making it an essential tool within the CRM category.

Try it

Run a sample request.

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

Get Deal by ID (Zoho CRM)

Try it

The unique Zoho Record ID of the deal to retrieve.

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
  • account_id
    Account Id
    nullabletext
  • account_name
    Account Name
    nullabletext
  • contact_id
    Contact Id
    nullabletext
  • contact_name
    Contact Name
    nullabletext
  • stage
    Stage
    text
  • amount
    Amount
    number
  • expected_revenue
    Expected Revenue
    nullablenumber
  • probability
    Probability
    nullablenumber
  • closing_date
    Closing Date
    text
  • type
    Type
    nullabletext
  • lead_source
    Lead Source
    nullabletext
  • campaign_source
    Campaign Source
    nullabletext
  • next_step
    Next Step
    nullabletext
  • description
    Description
    nullabletext
  • owner_id
    Owner Id
    nullabletext
  • owner_name
    Owner Name
    nullabletext
  • owner_email
    Owner Email
    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
  • stage_modified_time
    Stage Modified Time
    nullabletext
  • last_activity_time
    Last Activity Time
    nullabletext
  • overall_sales_duration
    Overall Sales Duration
    nullablenumber
  • sales_cycle_duration
    Sales Cycle Duration
    nullablenumber
  • reason_for_loss
    Reason For Loss
    nullabletext
  • record_status
    Record Status
    nullabletext
  • is_locked
    Is Locked
    nullableboolean

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/zoho-get-deal-by-id. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/zoho-get-deal-by-id
curl -X POST 'https://v3-api.texau.com/api/v1/zoho-get-deal-by-id' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"deal_id":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "deal_id": "rec_4f3a91",
    "deal_name": "sample",
    "account_id": 1,
    "account_name": 1,
    "contact_id": "rec_4f3a91",
    "contact_name": "sample",
    "stage": "sample",
    "amount": 1,
    "expected_revenue": 1,
    "probability": 1,
    "closing_date": "sample",
    "type": "sample",
    "lead_source": "sample",
    "campaign_source": "sample",
    "next_step": "sample",
    "description": "sample",
    "owner_id": "rec_4f3a91",
    "owner_name": "sample",
    "owner_email": "[email protected]",
    "created_by_id": "rec_4f3a91",
    "created_by_name": "sample",
    "modified_by_id": "rec_4f3a91",
    "modified_by_name": "sample",
    "created_time": "sample",
    "modified_time": "sample",
    "stage_modified_time": "sample",
    "last_activity_time": "sample",
    "overall_sales_duration": 1,
    "sales_cycle_duration": 1,
    "reason_for_loss": "sample",
    "record_status": "valid",
    "is_locked": true
  }
}

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 → get deal by id (zoho crm) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Get Deal by ID (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.

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 Get Deal by ID (Zoho CRM) in 60 seconds.

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