Public API
A Public API workflow exposes custom REST endpoints that external systems, partners, or frontend applications can call. Each workflow defines a single HTTP endpoint with its own path, method, authentication, rate limiting, and business logic.
Webhook
Workflow Webhook is a workflow type that defines processes triggered by webhooks. It allows external systems to trigger workflows via HTTP requests.
MCP Server
Every organization gets its own MCP (Model Context Protocol) server whose tools, resources, and prompts are defined as workflows. AI assistants and agents (Claude, Claude Code, and any other MCP-compatible client) connect to your organization's MCP endpoint and can only see and call what your organization has explicitly defined — none of the platform's built-in tools are exposed there.
Organization Connections & Transmissions
Organization connections link two organizations inside the same CXTMS instance. Transmissions carry messages, documents and files across such a link: one organization publishes an outbound transmission, the platform mirrors it into the partner organization as an inbound transmission, and the partner's workflows react to it. Together they replace point-to-point HTTP calls, shared API keys and file drops between tenants of the same platform.
Agent Responses API
Every active Agent workflow in an organization is reachable over an OpenAI Responses-compatible HTTP API Introduction) — every OpenAI-compatible SDK, and the AI SDK, can point at it directly.