Zoho logo

Delete Contact (Zoho CRM)

Zoho CRM → Delete Contact (Zoho CRM)

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

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

Install

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

When to use this.

The "Delete Contact (Zoho CRM)" action enables users to efficiently remove an existing contact record from Zoho CRM by utilizing its unique Record ID. This action is categorized under CRM and is essential for maintaining accurate and up-to-date contact information. The primary input parameter, "contact_id," is a string that specifies the unique Zoho Record ID of the contact to be deleted. Upon execution, the action provides output fields that include "status" (text) indicating the operation's success, "message" (text) offering a detailed response, and "deleted_id" (id) confirming the Record ID of the deleted contact. This functionality is particularly useful for organizations looking to streamline their contact management processes, ensuring that outdated or incorrect records are efficiently handled and moved to the Recycle Bin for potential recovery.

Try it

Run a sample request.

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

Delete Contact (Zoho CRM)

Try it

The unique Zoho Record ID of the contact 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-contact. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/zoho-delete-contact
curl -X POST 'https://v3-api.texau.com/api/v1/zoho-delete-contact' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"contact_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 Contact (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 contact (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 Contact (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 Contact (Zoho CRM) in 60 seconds.

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

Start free →Read the API docs