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.
If a bot is removed from a channel, delivery fails silently from Coroid's side — it appears identical to nothing having happened. Should channel notifications stop arriving, check the bot's membership before taking any other action.
Channel bridges
A bridge maps a Coroid context to a conversation — for example, a project's activity to a team channel.
Certain bridges are bidirectional, allowing people to start and manage work from the channel they already use. This is particularly useful for those "can someone just fix…" requests that would otherwise never be tracked as formal work.
What to send where
Channels are for team-visible events; personal notifications are for items requiring a specific person's attention.
| Event | Channel | Personal |
|---|---|---|
| Pull request ready | Yes | — |
| Task failed | Yes | — |
| Task asking a question | — | Yes |
| Plan awaiting approval | — | Yes |
Placing personal actions in a shared channel makes them everyone's responsibility, and thus nobody's.
SMS
SMS is reserved for genuine emergencies only. It is the most intrusive channel available and least suited to routine updates.
Keeping it quiet enough to matter
The main failure mode is excessive volume. A channel receiving every status update gets muted, and the important notification is silenced along with it.
Begin with pull requests ready and tasks that failed. Add further notifications only when you notice you're finding out about something too late.