Call the getConnectors MCP tool
List this workspace's third-party connector integrations (Smartlead, Instantly) with status, plus the providers that can be connected and what each supports (inbound events, outbound action names). Connecting or reconnecting a provider, and entering or rotating its API key, happens ONLY in Settings > Connectors (connect_url in the result): never request an API key or any other credential from the user in chat. Rules on a connected integration: getConnectorRules to read, createConnectorRule to save one (off), activateConnectorRule (launch scope) to turn it on.
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.
Request
- Base URL: https://app.reachium.io
- URL: https://app.reachium.io/api/v1/actions/getConnectors
- Auth: HTTP bearer
Headers
Optional caller-generated key (8-200 characters: letters, digits, dot, underscore, colon, or hyphen). A final tool result is replayed for the same key and body. An ambiguous result remains 409 under that key; reconcile external state before using a new key. Reuse with a different body returns 422.
Request body
Response
The result of calling this tool.
Changes
No recorded changes to this operation across all 3 revisions of this API.