---
title: "Call the activateConnectorRule MCP tool"
method: POST
path: "/api/v1/actions/activateConnectorRule"
tags: ["Actions"]
---

# Call the activateConnectorRule MCP tool

`POST /api/v1/actions/activateConnectorRule`

## Request

- Base URL: `https://app.reachium.io`
- URL: `https://app.reachium.io/api/v1/actions/activateConnectorRule`
- Auth: HTTP bearer

Turn ON one saved automation rule (rule_id from getConnectorRules). LAUNCH action, two-step: the first call (no confirm_token) returns a preview of the provider, trigger and filters, the action with every parameter in full (the whole message template for a DM rule, the destination for a provider action), and the daily cap, plus a confirm_token, and turns nothing on. The token binds that exact rule state; if anything changes, the next call previews again. Relay the preview to the user; after they approve, call again with the same rule_id plus confirm_token. Once on, the rule runs on every matching event with no further confirmation: a send_linkedin_message rule DMs leads automatically, an outbound rule acts in the provider, and add_to_campaign enrolls leads in a campaign. Activation also re-checks the provider webhooks; a warning in the result means the rule is on but that re-check did not fully succeed. A campaign-managed rule is refused.

Called through the Actions bridge: the response is that tool's own result, wrapped as `{ data: <tool result> }` under HTTP 200. Billing, daily-cap, and confirm-step outcomes are embedded INSIDE `data`, never remapped to an HTTP status (see the templated `/api/v1/actions/{toolName}` operation above for the full protocol, and `x-mcp-actions` for this tool's machine-readable scope/cap/confirm_behavior fields). Authentication, request-shape, and optional idempotency-protocol failures still use their documented non-200 statuses.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `rule_id` string, uuid, required: From getConnectorRules.
  - `confirm_token` string: From the preview response. Re-send with the same rule_id to execute.

## Response `200`

The result of calling this tool.

- object
  - `data` unknown, required
  - `error` unknown, required

## Other responses

- `400`: The request body was not a JSON object (code invalid_request), or Idempotency-Key is malformed (code invalid_idempotency_key).
- `401`: Missing or invalid API key. Send `Authorization: Bearer rmcp_...` (code unauthorized).
- `403`: This tool is out of the key’s granted scope (code insufficient_scope).
- `409`: This Idempotency-Key has an unresolved in-flight or ambiguous result (code request_in_flight). Reconcile before using a new key.
- `422`: This Idempotency-Key was already used with a different request body (code idempotency_key_reuse).
- `429`: Rate limited: shared `mcp:ip:{ip}` (600/60s) or `mcp:key:{keyId}` (120/60s) bucket, the SAME buckets the MCP endpoint uses (code rate_limited).
- `500`: Unhandled server error (code internal_error).

---

[API](https://skmtc.dev/reachium/apis/reachium-api.md) · [All operations](https://skmtc.dev/reachium/apis/reachium-api/llms.txt) · [OpenAPI document](https://skmtc.dev/reachium/apis/reachium-api/revisions/80c82dd6c7a1?raw)