Coroid connects to Slack, Discord, Telegram and SMS.
Configure them under Settings → Connections → Channels, which has two parts: Platform bots (the connection to the platform) and Channel bridges (which conversations map to what).
Platform bots
The bot is the identity Coroid uses on the platform. Install it once per workspace or server, and grant it access to the channels it should post in.
A bot removed from a channel causes delivery to fail silently from Coroid's side — it looks identical to nothing having happened. If channel notifications stop arriving, check bot membership before anything else.
Channel bridges
A bridge maps a Coroid context to a conversation — a project's activity to a team channel, for instance.
Some bridges are bidirectional, letting people start and steer work from the channel they already talk in. That is genuinely useful for the "can someone just fix…" requests that would otherwise never become tracked work.
What to send where
Channels are for team-visible events; personal notifications are for things needing a specific person.
| Event | Channel | Personal |
|---|---|---|
| Pull request ready | Yes | — |
| Task failed | Yes | — |
| Task asking a question | — | Yes |
| Plan awaiting approval | — | Yes |
Putting personal actions in a shared channel makes them everyone's problem, and therefore nobody's.
SMS
SMS is for genuine urgency and nothing else. It is the most intrusive channel available and the least suited to routine updates.
Keeping it quiet enough to matter
The failure mode is volume. A channel receiving every status change gets muted, and the notification that mattered is muted with it.
Start with pull requests ready and tasks failed. Add more only when you catch yourself finding out about something too late.