Call the createConnectorRule MCP tool

Save a NEW automation rule on a connected integration. The rule is always saved OFF: nothing runs until activateConnectorRule (launch scope) or Settings turns it on. direction "outbound" reacts to a Reachium event (trigger.event from the webhook catalog, e.g. lead.accepted) and runs one of the provider's own actions (action.type such as add_lead_to_campaign, with params like { provider_campaign_id }); direction "inbound" reacts to a provider event (trigger.event provider.*) and runs a Reachium action: add_to_campaign { campaign_id }, add_tag / remove_tag { tag }, set_lead_status { status }, mark_booked {}, record_booking {}, or send_linkedin_message { template } which, once activated, DMs the matched lead automatically. Events and action names are validated against the specific provider, so an unsupported pairing is refused with the reason. Each action type accepts exactly its own params (see the schema); unknown keys are refused. Pull getPlaybook("integrations", "connectors") first for the recipes and template variables.

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.