Current Channel Matrix
Channel Roles
Channel Versus Connector
Slack can be both:- a channel where work starts and replies are sent
- a connector target for workflow actions or tool access
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Understand current SuperEmber channel availability and channel roles.
| Channel | Status | Notes |
|---|---|---|
| Slack | Primary self-serve | OAuth install, workspace binding, channel and DM replies. |
| Microsoft Teams | Preview/admin-install | Visible in the app as coming soon unless your workspace has access. |
| Dashboard | Available | Control room for setup, workflows, files, integrations, and approvals. |
| Webhooks | Workflow feature | Can trigger published workflows when configured. |
| Schedules | Workflow feature | Can trigger workflows on cron-style schedules. |
| Connected app events | Connector feature | Some connectors expose manually created triggers. |
| WhatsApp, Telegram, LINE | Expansion/historical surfaces | Not the current public self-serve business wedge in these docs. |
| Role | Description |
|---|---|
| Intake | The channel starts work. |
| Context | The channel provides thread, sender, or conversation context. |
| Output | SuperEmber sends the result back. |
| Approval | The channel collects a human decision. |
| Resume | A reply resumes a paused workflow. |