Zoho logo

Remove Record from Campaign (Zoho CRM)

Zoho CRM → Remove Record from Campaign (Zoho CRM)

POST/v1/zoho-unlink-record-from-campaign
texau__zoho-unlink-record-from-campaignintegration
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/zoho-unlink-record-from-campaign
{
  "campaign_id": "sample-value",
  "related_module": "sample-value",
  "related_record_id": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "status": "valid",
    "message": "sample"
  }
}

Removes a Lead or Contact from a Campaign.

Install

Add remove record from 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.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__zoho-unlink-record-from-campaign

When to use this.

The "Remove Record from Campaign (Zoho CRM)" action allows users to efficiently unlink a Lead or Contact from a specific Campaign within Zoho CRM. This integration action requires three key input parameters: the unique 19-digit Campaign_ID to identify the Campaign, the Related_Module to specify whether the record is a Lead or a Contact, and the Related_Record_ID, which is the unique 19-digit identifier for the Lead or Contact being removed. Upon execution, the action returns a status indicating the success or failure of the operation and a message providing additional context. This action is particularly useful for managing campaign participation, ensuring that your marketing efforts are accurately targeted and up-to-date. It falls under the integration category, streamlining the process of maintaining clean and relevant campaign data in your CRM system.

Try it

Run a sample request.

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

Remove Record from Campaign (Zoho CRM)

Try it

The unique 19-digit ID of the Campaign.

Select whether you are removing a Lead or a Contact.

The unique 19-digit ID of the Lead or Contact.

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

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/zoho-unlink-record-from-campaign. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/zoho-unlink-record-from-campaign
curl -X POST 'https://v3-api.texau.com/api/v1/zoho-unlink-record-from-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"}'
200 Accepted
{
  "ok": true,
  "data": {
    "status": "valid",
    "message": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Remove Record from Campaign (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 → remove record from campaign (zoho crm) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Remove Record from Campaign (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 Remove Record from Campaign (Zoho CRM) in 60 seconds.

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

Start free →Read the API docs