Zoho logo

Link Deal and Contact (Zoho CRM)

Zoho CRM → Link Deal and Contact (Zoho CRM)

POST/v1/zoho-generic-contact-deal-association
texau__zoho-generic-contact-deal-associationcrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/zoho-generic-contact-deal-association
{
  "primary_module": "sample-value",
  "primary_record_id": "sample-value",
  "related_module": "sample-value",
  "related_record_id": "sample-value",
  "contact_role": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "status": "valid",
    "message": "sample",
    "linked_record_id": "rec_4f3a91"
  }
}

Bi-directional action to link a Deal and a Contact

Install

Add link deal and 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-generic-contact-deal-association

When to use this.

The "Link Deal and Contact (Zoho CRM)" action facilitates the bi-directional association of Deals and Contacts within Zoho CRM, allowing users to establish both Contact-to-Deal and Deal-to-Contact relationships. Key input parameters include the Primary_Module and Primary_Record_ID, which identify the main record, as well as the Related_Module and Related_Record_ID, which specify the associated record. Additionally, the Contact_Role parameter defines the specific role of the contact in relation to the deal. The output fields provide essential feedback, including the status of the operation, a message detailing the result, and the linked_record_id for reference. This action is particularly useful for sales teams looking to streamline their CRM processes, enhance relationship management, and ensure accurate tracking of interactions between deals and contacts. It falls under the CRM category and supports various data types, including text and ID, making it a versatile tool for effective customer relationship management.

Try it

Run a sample request.

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

Link Deal and Contact (Zoho CRM)

Try it

Select the primary module.

The unique 19-digit ID of the primary record.

Select the related module.

The unique 19-digit ID of the related record.

The specific role assigned to this contact for the deal.

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
  • linked_record_id
    Linked Record Id
    nullablestring

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/zoho-generic-contact-deal-association
curl -X POST 'https://v3-api.texau.com/api/v1/zoho-generic-contact-deal-association' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"primary_module":"sample-value","primary_record_id":"sample-value","related_module":"sample-value","related_record_id":"sample-value","contact_role":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "status": "valid",
    "message": "sample",
    "linked_record_id": "rec_4f3a91"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Link Deal and 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 → link deal and 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 2Link Deal and 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 Link Deal and Contact (Zoho CRM) in 60 seconds.

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

Start free →Read the API docs