Skip to main content
Channels connect your deployed agents to the surfaces where users interact: your own apps, voice calls, messaging apps, webhooks, and other agent frameworks. Artemis provides channel adapters that handle the protocol-specific details, so a single agent definition works across every channel without modification. A channel always binds to a deployment in a specific environment. Configure deployments first, then add channels on top. Navigation: Project > Deployments > Channels All five route to the same agent definition. The adapter normalizes inbound and outbound formats, so your agent doesn’t need channel-specific logic for basic conversations.

Messaging or digital

The Platform supports the following messaging or digital channels: Each setup page covers credential registration, webhook configuration, channel-specific features (such as Slack threading and slash commands, or WhatsApp interactive messages), and troubleshooting.

Voice

The Platform supports the following voice channels: Each voice setup page covers caller identity fields (session.anonymousId and related), voice-specific VOICE: response blocks, SSML control, and troubleshooting.

SDK

The Platform supports the following SDK channels to embed an agent in your own application or call it server-to-server:

Webhook

The Platform supports the following webhook channel to receive asynchronous events:

Protocols

The Platform supports the following open protocols to connect agents with other agent frameworks and frontends:
Related articles: