Zoho logo

Update Account (Zoho CRM)

Zoho CRM → Update Account (Zoho CRM)

POST/v1/zoho-update-account
texau__zoho-update-accountcrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/zoho-update-account
{
  "account_id": "Acme, Inc.",
  "account_name": "Acme, Inc.",
  "account_number": "Acme, Inc.",
  "account_site": "Acme, Inc.",
  "account_type": "Acme, Inc.",
  "parent_account": "Acme, Inc.",
  "mobile_number": "sample-value",
  "fax": "sample-value",
  "website": "https://acme.com",
  "ticker_symbol": "sample-value",
  "industry": "sample-value",
  "employee": 1,
  "annual_revenue": 1,
  "ownership": "sample-value",
  "rating": "sample-value",
  "sic_code": "sample-value",
  "billing_street": "sample-value",
  "billing_city": "sample-value",
  "billing_state": "sample-value",
  "billing_code": "sample-value",
  "billing_country": "sample-value",
  "shipping_street": "sample-value",
  "shipping_city": "sample-value",
  "shipping_state": "sample-value",
  "shipping_code": "sample-value",
  "shipping_country": "sample-value",
  "description": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "status": "valid",
    "message": "sample",
    "modified_time": "sample",
    "record_id": "rec_4f3a91"
  }
}

Update an existing account record in Zoho CRM using its unique record ID

Install

Add update account (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-account

When to use this.

The "Update Account (Zoho CRM)" action allows users to modify existing account records in Zoho CRM by utilizing the unique record ID of the account. This action supports various optional input parameters, including account name, account number, phone, website, and industry classification, enabling users to update specific fields as needed. The output includes a status message, a response message detailing the operation's success, the modified time of the record, and the updated record ID. This action is particularly useful for businesses looking to maintain accurate and up-to-date account information, streamline customer relationship management, and ensure data integrity within their CRM systems. It falls under the CRM category and is essential for organizations that require dynamic updates to their account records.

Try it

Run a sample request.

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

Update Account (Zoho CRM)

Try it

The unique Zoho Record ID of the account to update.

Updated name for the account.

Updated account number.

Updated account site location or division.

Updated type of the account.

The unique Zoho Record ID of the parent account.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • status
    Status
    string
  • message
    Message
    nullablestring
  • modified_time
    Modified Time
    nullablestring
  • record_id
    Record Id
    nullablestring

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/zoho-update-account
curl -X POST 'https://v3-api.texau.com/api/v1/zoho-update-account' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"account_id":"Acme, Inc.","account_name":"Acme, Inc.","account_number":"Acme, Inc.","account_site":"Acme, Inc.","account_type":"Acme, Inc.","parent_account":"Acme, Inc.","mobile_number":"sample-value","fax":"sample-value","website":"https://acme.com","ticker_symbol":"sample-value","industry":"sample-value","employee":1,"annual_revenue":1,"ownership":"sample-value","rating":"sample-value","sic_code":"sample-value","billing_street":"sample-value","billing_city":"sample-value","billing_state":"sample-value","billing_code":"sample-value","billing_country":"sample-value","shipping_street":"sample-value","shipping_city":"sample-value","shipping_state":"sample-value","shipping_code":"sample-value","shipping_country":"sample-value","description":"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 Account (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 account (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 Account (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 limitNo public cap
  • Per-day limitPlan-defined
  • 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 Account (Zoho CRM) in 60 seconds.

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

Start free →Read the API docs