Zoho logo

Delete Deal (Zoho CRM)

Zoho CRM → Delete Deal (Zoho CRM)

POST/v1/zoho-delete-deal
texau__zoho-delete-dealcrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/zoho-delete-deal
{
  "deal_id": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "status": "valid",
    "message": "sample",
    "deleted_id": "rec_4f3a91"
  }
}

Delete an existing deal record in Zoho CRM using its unique Record ID.

Install

Add delete deal (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-delete-deal

When to use this.

The "Delete Deal (Zoho CRM)" action enables users to remove an existing deal record from Zoho CRM by utilizing its unique Record ID. This action requires a single input parameter, "deal_id," which is a string representing the unique identifier of the deal to be deleted. Upon execution, the action returns three output fields: "status," indicating the success or failure of the operation; "message," providing a detailed response regarding the deletion process; and "deleted_id," confirming the Record ID of the deal that has been successfully removed. This action is particularly useful for CRM administrators and sales teams looking to maintain accurate and up-to-date records by eliminating obsolete or erroneous deal entries. As part of the CRM category, it streamlines deal management and enhances data integrity within Zoho CRM environments.

Try it

Run a sample request.

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

Delete Deal (Zoho CRM)

Try it

The unique Zoho Record ID of the deal to delete.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • status
    Status
    nullablestring
  • message
    Message
    string
  • deleted_id
    Deleted Id
    nullablestring

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/zoho-delete-deal
curl -X POST 'https://v3-api.texau.com/api/v1/zoho-delete-deal' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"deal_id":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "status": "valid",
    "message": "sample",
    "deleted_id": "rec_4f3a91"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

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

Step 1TriggerNew row, webhook, or schedule.
Step 2Delete Deal (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 Delete Deal (Zoho CRM) in 60 seconds.

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

Start free →Read the API docs