Teams (Microsoft Teams)

Send work-item activity from Coco Kanban into your Microsoft Teams channels — new work items, state changes and comments, posted as cards where your team already talks.

Plan: Business and above

A note on the name: Teams here means Microsoft Teams. It connects your workspace to Teams channels. It does not create groups of members inside Coco Kanban — for that, use projects, project members and labels.

What you can do

Connect one or more Microsoft Teams channels to a workspace.
Scope each connection to a single project, or leave it on All projects.
Choose which events each channel receives: Issue Created, State Changed, Comment.
Send a test message to check a channel is wired up correctly.
Remove a channel connection at any time.
Deliver scheduled digests to a connected Teams channel.

Connections are made with a Teams channel Workflow webhook. No Azure app registration, no admin consent, no legacy connectors.

Getting started

Open the Teams settings

Click Teams in the workspace sidebar. It takes you to Workspace settings → Teams.
You can also go there directly: Workspace settings → Teams.

📷 Screenshot: Workspace settings → Teams, showing the "Connect a Teams channel with a Workflow" instructions card and an empty "Connected channels" list.

Create the webhook in Microsoft Teams

Do this once per channel you want to post into.

In Microsoft Teams, hover over the channel → click ••• (More options) → Workflows.
Choose the template "Post to a channel when a webhook request is received."
Confirm the team and channel, then click Add workflow. Teams generates a webhook URL.
Copy the URL and click Done.

Add the channel in Coco Kanban

On Workspace settings → Teams, click Add channel.
Paste the Teams Workflow webhook URL. It must start with https://.
Optionally give it a channel label (for example, Engineering — #general) so you can tell connections apart later.
Pick a project, or leave it as All projects.
Toggle the events you want: Issue Created, State Changed, Comment.
Click Add channel.

Register the workspace webhook (one time)

Events only reach Teams once the workspace is sending them.

On the Teams settings page, copy the URL shown under the instructions card — it looks like .../workspace-webhook/<your-workspace>.
Go to Workspace settings → Webhooks and add it as a new webhook.
Save. The webhook's signing secret is used to verify every event, so unsigned or forged requests are rejected.

This is a one-off step per workspace, not per channel.

Managing connected channels

Each connected channel shows as a card on the settings page with its label, its project scope (or an All projects badge), and a masked version of the webhook URL.

Send test — posts a test card to the channel. If you see it in Teams, you're connected.
Toggles — flip Issue Created, State Changed or Comment on or off. Changes save immediately.
Trash icon — removes the connection. You'll be asked to confirm.

📷 Screenshot: A connected channel card showing the label, project badge, masked webhook URL, "Send test" button and the three event toggles.

What a Teams message looks like

Each event posts a card containing the work item's identifier and title, its priority, its state and its project, plus a View in Coco Kanban button that deep-links straight to the work item. Comment events include the commenter's name and the first part of the comment.

Tips

Create one connection per project rather than a single All projects connection if different squads live in different channels — otherwise every project's noise lands in one place.
Turn Comment off on high-traffic projects. Created + State Changed is usually the right signal-to-noise balance.
Use the channel label field. A masked webhook URL is unreadable; a label like Support — #triage is not.
Removing a channel here stops the posts but leaves the Workflow in Microsoft Teams alone. Delete it in Teams too if you want it gone for good.

Limits & good to know

Notifications are one-way. With the Workflow-webhook method, events flow from Coco Kanban into Teams. Replying in the Teams channel does not create a comment back on the work item.
Three event types only. Created, state changed and comment. There is no "assigned to me" toggle in the UI, and no notifications for cycles, modules or pages.
Webhook URLs must be HTTPS. Anything else is rejected when you add the channel.
Nothing posts until the workspace webhook is registered. If channels are connected but silent, check Workspace settings → Webhooks first — that's almost always the cause.
Removing a channel is immediate and cannot be undone; you'd need to re-add the webhook URL.