Coroid has platform bots for Slack, Discord, Telegram and SMS. Configure them in this section: Settings → Connections → Channels.
What each one does today:
| Platform | Messages become requests | Receives updates |
|---|---|---|
| Slack | Yes, through an event automation | Task updates, through an incoming webhook |
| Telegram | Yes, through an event automation | No |
| Discord | No | No |
| SMS | No | No |
You can save a Discord or SMS bot, but nothing uses it today. The same page also has channel bridges, which do not work yet. See Channel bridges.
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 read. Slack and Telegram need their bot so an event automation can read messages.
A Slack bot removed from a channel stops Coroid from reading that channel, and nothing says so. If Slack messages stop becoming requests, check that the bot is still in the channel.
Only owners and admins can add, change or remove a bot. Each platform sends its events to a webhook URL on the API gateway, which Coroid shows for each bot. Coroid refuses a delivery that is not signed with the bot's secret.
Starting work from a channel
A Slack or Telegram message can become a request for work. Discord and SMS messages cannot.
A message becomes a request through an event automation. That is useful for the "can someone just fix…" requests that would otherwise never become tracked work.
A matching message goes to Qualification as a request. Qualification screens it, looks for duplicates and settles what it should become. Nothing is created until it passes. See Ways to start work.
Coroid does not link Slack or Telegram accounts to Coroid accounts, so anyone who can post in a matching chat can file a request. For that reason, work from a chat never starts on its own. A qualified task is created and waits for someone to start it, and a plan waits for approval.
See Triggers and destinations.
Slack
- Configure the Slack bot in this section: Platform bots. It needs the bot token and the Slack app's signing secret.
- In your Slack app, send channel messages and app mentions to the webhook URL
that Coroid shows:
https://api.coroid.ai/api/v1/webhooks/slack/events. - Invite the bot to each channel it should read.
- Turn on Slack in Quality Control → Organization default → Before work starts → Where requests come from. Only owners and admins can turn a source on, and only once the bot is connected.
Turning Slack on adds an automation that files matching messages as requests. It is listed in Factory → Automations, where you can change its filter. Turning Slack off pauses the automation and keeps its filter.
The automation's filter decides which messages count. It starts by matching
messages that contain this mention: @coroid. A filter can also limit the
automation to one channel, or to messages posted by bots, such as alerts.
Coroid runs at most 10 Slack automations a minute for one channel.
Telegram
- Add the Telegram bot in this section: Platform bots. Coroid registers its webhook with Telegram and protects it with a webhook secret. If you leave the secret empty, Coroid generates one.
- Add the bot to the group, or make it an admin of the channel.
- Turn on Telegram in Quality Control → Organization default → Before work starts → Where requests come from. Its automation is listed in Factory → Automations, where you can change its filter.
- In the chat, start each request with this command:
/coroid.
Telegram's privacy mode, on by default, lets the bot see commands but not ordinary messages. A filter can also limit the automation to one chat by its chat ID. The bot ignores direct messages unless the filter allows them.
Anyone can add your bot to another group and file requests from there. To
prevent that, limit the automation to your chat, or stop the bot joining groups
with this BotFather command: /setjoingroups.
Coroid accepts at most 10 matching messages a minute from one chat. If the automation is limited to one project, its requests go to that project.
Channel bridges
A bridge connects a channel to a session with the chat assistant.
Talking to the assistant through a bridge is not available. A bridge does not pass messages to the assistant, so it cannot start or steer work.
Updates in a channel
Slack is the only chat platform that receives updates. Coroid posts to one Slack channel when a task completes, fails or is escalated, and when it retries or gives up on a merge conflict. The messages go through a Slack incoming webhook connected to your organization, not through the Slack bot. No settings screen connects the webhook yet.
Discord, Telegram and SMS receive no updates. Everything else arrives in the portal. See Notifications.