Slack

Push work-item activity into Slack. Map a project to a channel and every work item created, updated or commented on in that project shows up there as a formatted message with a link straight back into Coco Kanban.

Plan: Business and above

What you can do

  • Connect one Slack workspace to your Coco Kanban workspace.
  • Map any project to any Slack channel — several projects to one channel, or one project to several channels.
  • Get a message in the channel when a work item is created, updated or deleted, and when someone comments.
  • Share a report from the Reports page into a connected Slack channel.

Getting started

Step 1 — Create a Slack app and get a bot token

Coco Kanban posts as a Slack bot, so you need a bot token from your own Slack app. This is a one-off.

  1. Go to api.slack.com/apps and create a new app in your Slack workspace.
  2. Give it permission to post messages (the chat:write bot scope), then install it to your workspace.
  3. On the app's OAuth & Permissions page, copy the Bot User OAuth Token — it starts with xoxb-.
  4. Note your Slack workspace (team) ID — it looks like T0XXXXXXXX and is visible in your Slack app settings.

Step 2 — Connect Slack

  1. Go to Workspace settings → Integrations.
  2. On the Slack card, click Connect. This opens the Slack settings page for your workspace.
  3. Click Add to Slack, then fill in:
    • Bot User OAuth Token — the xoxb-… token from step 1.
    • Slack Workspace ID (Team ID) — e.g. T0XXXXXXXX.
    • Slack Workspace Name — a display name, e.g. your company name.
  4. Click Connect.

The page then shows a green connection status with your Slack workspace name and team ID, and a Disconnect button.

📷 Screenshot: The Slack settings page showing the connected status card with the Slack workspace name and team ID.

Step 3 — Register the webhook

Slack notifications are driven by a Coco Kanban webhook. You register it once per workspace.

  1. On the Slack settings page, under Register Webhook, copy the Webhook URL shown (there's a Copy button).
  2. Go to Workspace settings → Webhooks → Create Webhook and paste that URL.
  3. Enable Issues and Comments on the webhook.
  4. Save.

The webhook's signing secret is picked up automatically — there's nothing else to configure. Deliveries that aren't correctly signed are rejected, so a mistyped URL simply won't post anything rather than leaking data.

📷 Screenshot: The Slack settings page "Register Webhook in Coco Kanban" panel with the webhook URL and Copy button.

Step 4 — Map projects to channels

  1. Still on the Slack settings page, scroll to Channel Mappings.
  2. Pick a Project from the dropdown.
  3. Type the Channel Name, e.g. #engineering.
  4. Click Add.

The mapping appears in the list below as Project → #channel, with a Remove button.

From here on, every work-item and comment event in that project posts to that channel.

📷 Screenshot: The Channel Mappings section with a project mapped to a Slack channel.

Invite the bot to the channel. Slack won't let a bot post into a channel it isn't a member of. In Slack, type /invite @YourApp in the channel — otherwise messages silently fail.

What the messages look like

Work item events post a message with the action (created / updated / deleted), the project name, the work item title as a link back into Coco Kanban, and — where present — its status and up to three assignees.

Comments post the commenter's name and the first 200 characters of the comment, with a "View issue" link.

Sharing a report to Slack

From the Reports page you can share a report into a connected Slack channel. The report is converted to Slack formatting — headings become bold, bullets stay bullets — and posted as a message. If you don't name a channel, it goes to the first channel mapped for the workspace.

Scheduled digests can also be delivered to a Slack channel on a recurring basis.

Tips

  • One project, several channels works fine — add the same project twice with different channel names. Both channels get every event.
  • Channel names with or without # are both accepted.
  • Test it with a throwaway work item. Create one in a mapped project; the message should land within a second or two. If nothing arrives, the usual cause is the bot not being in the channel.

Limits & good to know

  • It's one-way. Coco Kanban posts into Slack. You cannot create, update or comment on work items from Slack — there are no slash commands.
  • You bring your own Slack app. There's no one-click "Add to Slack" marketplace install; you create the app and paste its bot token.
  • No per-event filtering per channel. A mapped channel gets create, update, delete and comment events for that project. If a channel gets noisy, map a narrower project rather than a busier one.
  • No back-fill. Only events that happen after the mapping exists are posted.
  • One Slack workspace per Coco Kanban workspace. Connecting a second replaces the first.
  • Disconnecting clears the token and stops all posting. Channel mappings are preserved, so reconnecting resumes where you left off.