Link Record to Campaign (Zoho CRM)
Zoho CRM → Link Record to Campaign (Zoho CRM)
/v1/zoho-link-record-to-campaign{ "campaign_id": "sample-value", "related_module": "sample-value", "related_record_id": "sample-value", "member_status": "sample-value" }
{ "ok": true, "data": { "status": "valid", "message": "sample", "linked_record_id": "rec_4f3a91" } }
Adds a Lead or Contact to a Campaign and sets their Member Status.
Install
Add link record to campaign (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.
{ "mcpServers": { "texau": { "command": "npx", "args": ["-y", "@texau/mcp-server"], "env": { "TEXAU_API_KEY": "..." } } } }
Tool name: texau__zoho-link-record-to-campaign
When to use this.
The "Link Record to Campaign (Zoho CRM)" action facilitates the integration of leads or contacts into specific marketing campaigns within Zoho CRM. By providing key input parameters such as Campaign_ID, Related_Module (to specify whether the record is a Lead or Contact), Related_Record_ID, and an optional Member_Status, users can effectively manage their campaign memberships. The action outputs essential data, including a status message and the linked_record_id, confirming the successful addition of the record. This functionality is particularly useful for marketing teams looking to streamline their campaign management processes, enhance lead tracking, and improve engagement strategies. As part of the integration category, this action supports efficient data handling and campaign optimization within the Zoho CRM ecosystem.
Try it
Run a sample request.
The response is a deterministic, cached example. No live call, no credits used.
Link Record to Campaign (Zoho CRM)
Response
Output schema.
Every field returned in `data`. Click rows to expand nested objects.
statusStatusnullablestringmessageMessagestringlinked_record_idLinked Record Idnullablestring
Integrate
Copy-pasteable snippets.
Real endpoint: https://v3-api.texau.com/api/v1/zoho-link-record-to-campaign. Auth: x-api-key.
/v1/zoho-link-record-to-campaigncurl -X POST 'https://v3-api.texau.com/api/v1/zoho-link-record-to-campaign' \ -H 'x-api-key: $TEXAU_API_KEY' \ -H 'content-type: application/json' \ -d '{"campaign_id":"sample-value","related_module":"sample-value","related_record_id":"sample-value","member_status":"sample-value"}'
{ "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.
crm
Get Account by ID (Zoho CRM)
Retrieve details of a specific account using its unique Zoho Record ID.
crm
Delete Account (Zoho CRM)
Delete an existing account record in Zoho CRM using its unique record ID. This action typically moves the record to the Recycle Bin.
crm
List Contacts (Zoho CRM)
Retrieve a paginated list of contacts from Zoho CRM, including basic contact fields and pagination info.
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 → link record to campaign (zoho crm) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.
Built for
Who runs this.
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. |
Related
More Zoho CRM actions.
crm
Get Account by ID (Zoho CRM)
Retrieve details of a specific account using its unique Zoho Record ID.
crm
Delete Account (Zoho CRM)
Delete an existing account record in Zoho CRM using its unique record ID. This action typically moves the record to the Recycle Bin.
crm
List Contacts (Zoho CRM)
Retrieve a paginated list of contacts from Zoho CRM, including basic contact fields and pagination info.
crm
Create Account (Zoho CRM)
Create a new account record in Zoho CRM, including company details, billing, and shipping addresses. Requires an Account Name.
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 Record to Campaign (Zoho CRM) in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.