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.

Update Lead (Zoho CRM)

Zoho CRM → Update Lead (Zoho CRM)

POST/v1/zoho-update-lead

texau__zoho-update-leadcrm

Run in Studio →Open in MCP

cURL · api.texau.app

84ms

POST/v1/zoho-update-lead

{
  "lead_id": "sample-value",
  "company": "Acme, Inc.",
  "last_name": "Doe",
  "first_name": "Jane",
  "title": "sample-value",
  "email": "[email protected]",
  "secondary_email": "[email protected]",
  "mobile_number": "sample-value",
  "fax": "sample-value",
  "website": "https://acme.com",
  "lead_source": "sample-value",
  "lead_status": "sample-value",
  "industry": "sample-value",
  "number_of_employee": 1,
  "annual_revenue": 1,
  "rating": "sample-value",
  "skype_id": "sample-value",
  "twitter": "sample-value",
  "street": "sample-value",
  "city": "sample-value",
  "state": "sample-value",
  "zip_code": "sample-value",
  "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 lead record in Zoho CRM using its unique Record ID.

Install

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

When to use this.

The "Update Lead (Zoho CRM)" action allows users to efficiently update existing lead records in Zoho CRM by utilizing the unique Record ID associated with each lead. This action supports a variety of input parameters, including optional fields such as Company, First_Name, Last_Name, Email, Phone, and more, enabling comprehensive updates to lead information. The output includes essential data fields such as status, message, modified_time, and record_id, providing users with clear feedback on the update process. This action is particularly useful for sales and marketing teams looking to maintain accurate lead information, streamline customer interactions, and enhance lead management workflows within the CRM category. By utilizing this API action, organizations can ensure their lead data remains current and relevant, ultimately driving better engagement and conversion rates.

Try it

Run a sample request.

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

Update Lead (Zoho CRM)

Try it

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-lead. Auth: x-api-key.

cURL · api.texau.app

84ms

POST/v1/zoho-update-lead

curl -X POST 'https://v3-api.texau.com/api/v1/zoho-update-lead' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"lead_id":"sample-value","company":"Acme, Inc.","last_name":"Doe","first_name":"Jane","title":"sample-value","email":"[email protected]","secondary_email":"[email protected]","mobile_number":"sample-value","fax":"sample-value","website":"https://acme.com","lead_source":"sample-value","lead_status":"sample-value","industry":"sample-value","number_of_employee":1,"annual_revenue":1,"rating":"sample-value","skype_id":"sample-value","twitter":"sample-value","street":"sample-value","city":"sample-value","state":"sample-value","zip_code":"sample-value","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 Lead (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.

Input	Status	Score
[email protected]	valid	96
[email protected]	risky	54
[email protected]	invalid	12

Workflow

A real example.

Trigger → update lead (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 Lead (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.

Code	Cause	Fix
200 OK	Action ran. Data in `data`.	Read response.
400 Bad Request	Missing or malformed input.	Validate against the input schema.
401 Unauthorized	Missing or invalid `x-api-key`.	Re-issue from /api-platform.
403 Forbidden	Workspace lacks plan tier.	Upgrade or contact sales.
404 Not Found	Action key not recognized.	Verify the slug.
429 Rate Limited	Per-minute or per-day cap hit.	Backoff; reduce concurrency.
500 Server Error	Unexpected TexAu issue.	Retry with backoff.
502 Bad Gateway	Upstream provider 5xx.	Retry; we surface root cause.
504 Timeout	Upstream 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 Update Lead (Zoho CRM) in 60 seconds.

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

Start free →Read the API docs

Update Lead (Zoho CRM)

Add update lead (zoho crm) to your MCP client.

When to use this.

Run a sample request.

Update Lead (Zoho CRM)

Output schema.

Copy-pasteable snippets.

How this fits a workflow.

Get Account by ID (Zoho CRM)

Delete Account (Zoho CRM)

List Contacts (Zoho CRM)

Results land in a TexAu table.

A real example.

Who runs this.

Rate limits & reliability.

HTTP status codes.

What it costs to run.

More Zoho CRM actions.

Get Account by ID (Zoho CRM)

Delete Account (Zoho CRM)

List Contacts (Zoho CRM)

Create Account (Zoho CRM)

FAQ.

Is this real-time?

Do I get charged on failure?

Does it work with Claude / Cursor via MCP?

What CRMs can I push results to?

Run Update Lead (Zoho CRM) in 60 seconds.