Zoho logo

Update Contact (Zoho CRM)

Zoho CRM → Update Contact (Zoho CRM)

POST/v1/zoho-update-contact
texau__zoho-update-contactcrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/zoho-update-contact
{
  "contact_id": "sample-value",
  "account_name": "Acme, Inc.",
  "first_name": "Jane",
  "last_name": "Doe",
  "email": "[email protected]",
  "mobile_number": "sample-value",
  "title": "sample-value",
  "department": "sample-value",
  "mailing_street": "sample-value",
  "mailing_city": "sample-value",
  "mailing_state": "sample-value",
  "mailing_zip": "sample-value",
  "mailing_country": "sample-value",
  "description": "sample-value",
  "lead_source": "sample-value",
  "other_mobile_number": "sample-value",
  "fax": "sample-value",
  "home_mobile_number": "sample-value",
  "skype_id": "sample-value",
  "twitter": "sample-value",
  "secondary_email": "[email protected]",
  "assistant": "sample-value",
  "asst_mobile_number": "sample-value",
  "reporting_to": "sample-value",
  "date_of_birth": "sample-value",
  "other_street": "sample-value",
  "other_city": "sample-value",
  "other_state": "sample-value",
  "other_zip": "sample-value",
  "other_country": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "status": "valid",
    "message": "sample",
    "modified_time": "sample",
    "record_id": "rec_4f3a91"
  }
}

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

Install

Add update 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-update-contact

When to use this.

The "zoho-update-contact" action enables users to efficiently update existing contact records within Zoho CRM by utilizing the unique Record ID associated with each contact. This action supports a variety of input parameters, including optional fields such as first name, last name, email, mobile number, job title, and address details, allowing for comprehensive updates to contact information. Upon execution, the action returns key output data, including the status of the update, a message detailing the operation's success or failure, the modified time of the record, and the updated record ID. This functionality is essential for businesses looking to maintain accurate and up-to-date contact information in their CRM systems, facilitating improved communication and relationship management. Use cases include updating client details after meetings, correcting contact information, and managing lead sources effectively within the CRM category.

Try it

Run a sample request.

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

Update Contact (Zoho CRM)

Try it

The unique Zoho Record ID of the contact to update.

Account Name

Updated first name.

Updated last name.

Updated email address.

Updated mobile number.

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
    nullablestring
  • modified_time
    Modified Time
    nullablestring
  • record_id
    Record Id
    string

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/zoho-update-contact
curl -X POST 'https://v3-api.texau.com/api/v1/zoho-update-contact' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"contact_id":"sample-value","account_name":"Acme, Inc.","first_name":"Jane","last_name":"Doe","email":"[email protected]","mobile_number":"sample-value","title":"sample-value","department":"sample-value","mailing_street":"sample-value","mailing_city":"sample-value","mailing_state":"sample-value","mailing_zip":"sample-value","mailing_country":"sample-value","description":"sample-value","lead_source":"sample-value","other_mobile_number":"sample-value","fax":"sample-value","home_mobile_number":"sample-value","skype_id":"sample-value","twitter":"sample-value","secondary_email":"[email protected]","assistant":"sample-value","asst_mobile_number":"sample-value","reporting_to":"sample-value","date_of_birth":"sample-value","other_street":"sample-value","other_city":"sample-value","other_state":"sample-value","other_zip":"sample-value","other_country":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "status": "valid",
    "message": "sample",
    "modified_time": "sample",
    "record_id": "rec_4f3a91"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Update 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 → update 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 2Update 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 Update Contact (Zoho CRM) in 60 seconds.

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

Start free →Read the API docs