Call the createWebhookEndpoint MCP tool

Create a new outbound webhook endpoint. url must be https; a private, local, or internal host is refused. Pass at least one event type in events (see getWebhookEndpoints or the "known" list on an unknown_event error for the currently subscribable types). Optional category_filters narrows reply.* events to specific reply classifications; omit to receive every event you subscribed to. Optional campaign_filters restricts delivery to events for those campaign ids only (must be campaigns already in this workspace); omit or leave empty for every campaign. From this surface the endpoint is created INACTIVE and its signing secret is never returned: the user opens Settings > Developer > Webhooks (ui_url in the result), rotates the secret on the new endpoint to see it once, then enables it. The REST API creates it active and returns the secret directly for server-side automation.

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.