Skip to main content

Connections & Integrations

Once you've built and published an Application, the Deployment tab (formerly named "Integration") is where you expose it to the world. SimplAI supports two broad categories of exposure:

  • Platform-managed surfaces — REST API, Embed widget, Webhooks, agent-to-agent (A2A) invocation. Use these when you control the calling application.
  • Third-party channel integrations — WhatsApp (via Karix), and coming: Kaleyra WhatsApp, Slack, Telegram, Microsoft Teams. Use these when the user is reaching the agent through an existing communication channel.

Prerequisites​

  • The application must have at least one Published version. If none exists, you'll see a notice to publish first.
  • The first time you open the Deployment tab (or any time after disabling), click Enable integration. Enabling may count toward your organization's plan limits on integrable applications.
  • You can disable / enable later from the top-right of the Deployment page.

Platform-managed surfaces​

REST API​

Call the application from your backend, mobile app, or any custom integration.

Endpoint for Agents:

POST /interact/api/v1/intract/agent/conversation

Required headers (exact names visible in the API tab):

  • Session / tenant / user / device identifiers
  • Content-Type: application/json

Request body (new or continued conversation):

{
  "agent_id": "<your-agent-id>",
  "language_code": "EN",
  "source": "APP",
  "action": "START_SCREEN",
  "conversation_id": "<existing-conversation-id>",
  "query": {
    "message": "<your text here>",
    "message_type": "string",
    "message_category": "string"
  }
}

Omit conversation_id for a new conversation; include it to continue. The tab provides:

  • API Key (choose from your saved keys)
  • Agent ID, Tenant ID, Client ID
  • A ready-to-copy curl example and a right-side request body template.

Embed widget​

Drop the application into a web page with a copy-paste snippet. Customize widget size, position, and primary color. A live preview shows what users will see. Voice agents have their own embed configured under Voice Agents → Deployment.

Webhooks​

Receive asynchronous results without polling. The Deployment tab provides the webhook configuration UI — register endpoint URLs and pick which events to subscribe to.

Agent-to-Agent (A2A)​

Allow agents to invoke other published agents directly within the platform. A2A bindings are configured per agent and respect the same versioning and permission model as direct invocations.

To connect an external A2A-compatible agent (one built outside SimplAI) and use it as a sub-agent, see A2A Agents.

Third-party channel integrations​

WhatsApp (Karix) — available now​

Route inbound WhatsApp messages through Karix to a published SimplAI Agent, with optional voice-message transcription. See Karix WhatsApp for the full setup walkthrough.

Coming soon​

The following third-party channels are in active product definition and will land in upcoming releases:

  • WhatsApp via Kaleyra — alternative WhatsApp provider for tenants standardized on Kaleyra.
  • Slack — bring a SimplAI agent into Slack channels and DMs.
  • Telegram — bot integration for Telegram chats and groups.
  • Microsoft Teams — agent integration for Teams channels.

These will be configurable from a unified Chat and Voice Integrations sub-tab on each agent, with group-conversation controls, session threading, and a one-agent-per-connection cardinality rule.

Connectors & external systems​

Beyond messaging channels, SimplAI connects to external agents and SaaS data sources:

  • MCP — register any external MCP-compatible server and use the tools it exposes in Tools, AI Chains, and Agents.
  • A2A Agents — connect any external A2A-compatible agent and use it as a sub-agent.
  • Google Workspace — fetch data from Google Sheets, Docs, and Drive via a data-fetch tool step.

Audit and versioning​

Every connection action — create, edit, delete, enable, disable — is captured in the Audit log.

Integrations are bound to specific application versions. If you publish a new version, you can choose whether to re-bind active integrations or leave them on the prior version.

Legacy AI Chain deployment​

Before the unification of Tools and AI Chains, AI Chains had their own integration page. See Legacy AI Chain Deployment for the historical view; new development uses Tools in Conversation mode with the standard Deployment tab.