First Channel

Channels are how matic connects to the outside world. They receive inbound signals from messaging platforms, webhooks, and the terminal, then route them to the right agent or group. Every channel is durable org configuration stored at .matic/channels/, not an ad hoc integration, which makes your communication surface versioned, auditable, and portable across environments. This section walks through standing up your first channel, wiring it to agents, and controlling how signals flow through your org.

Terminal Channel

Terminal Channel - The built-in matic chat channel requires no external configuration and is always available; start here to understand how signals, sessions, and routing work before adding external integrations.

Configure Slack

Configure Slack - Connect a Slack workspace so messages in designated channels become routable signals, with support for @-mention routing and threaded sessions.

Configure Telegram

Configure Telegram - Set up a Telegram bot as a channel, mapping chat IDs to agents or projects for direct and group conversations.

Configure Webhooks

Configure Webhooks - Create HTTP inbound channels that accept structured payloads from CI/CD pipelines, monitoring platforms, or any system that can POST JSON.

Channel Signals and Sessions

Channel Signals and Sessions - Learn how inbound messages become normalized SignalPayload objects, enter the Listen -> Interpret -> Resolve pipeline, and create or resume stateful sessions.

Handle Mentions and Routing

Handle Mentions and Routing - See how @agent-handle triggers direct routing, @group-handle resolves to a single responder, and unmatched signals fall through to Auto Matic.

Notification Policies

Notification Policies - Define policy-driven outbound notifications for events like budget warnings, HITL checkpoints, or run failures, distinct from conversational replies and governed by escalation rules.