Microsoft Teams

Send work-item activity into Microsoft Teams channels. Connect a channel with a Teams Workflow — no Azure app, no admin consent, no connectors.

Plan: Business and above

What you can do

Connect any number of Teams channels to your workspace.
Send each channel everything, or scope it to a single project.
Choose per channel which events to send: Issue Created, State Changed, Comment.
Send a test message to confirm a channel is wired up before you rely on it.
Share a report from the Reports page into a connected Teams channel.

Getting started

Open Workspace settings → Teams. (The Teams item in the app sidebar goes to the same page.)

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

Step 1 — Create the Workflow in Teams

This is done inside Microsoft Teams, and it's the only setup Microsoft requires.

In Microsoft Teams, hover over the channel you want, then 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 that URL, then click Done.

The URL looks like https://prod-00.westus.logic.azure.com:443/workflows/…. Keep it to hand — you'll paste it in a moment. Treat it as a secret: anyone with the URL can post to that channel.

Step 2 — Register the Coco Kanban webhook (once per workspace)

Work-item events reach Teams through a Coco Kanban webhook. You set this up once, not once per channel.

On the Workspace settings → Teams page, find the URL shown under "One-time per workspace" and click Copy.
Go to Workspace settings → Webhooks and create a webhook with that URL.
Enable work-item and comment events, then save.

The signing secret is picked up automatically. Deliveries that aren't correctly signed are rejected, so a wrong URL fails safe rather than posting nonsense.

Step 3 — Add the channel

Back on Workspace settings → Teams, click Add channel.
Paste the Teams Workflow webhook URL from step 1. It must start with https://.
Give it a Channel label — optional, but a name like Engineering – #general makes the list readable.
Pick a Coco Kanban project, or leave it as All projects.
Choose which events to send: Issue Created, State Changed, Comment. All three are on by default.
Click Add channel.

📷 Screenshot: The "Add a Teams channel" dialog with the Workflow webhook URL, label, project selector and the three notification toggles.

Step 4 — Prove it works

Each connected channel has a Send test button. Click it and a test card should appear in the Teams channel within a second or two. If it doesn't, the webhook URL is wrong — regenerate the Workflow in Teams and paste the new URL.

Managing connected channels

The Connected channels list shows each channel with its label, the project it's scoped to (or an "All projects" badge), and a masked version of its webhook URL.

Change what it sends — flip the Issue Created / State Changed / Comment toggles. Changes save immediately.
Send test — post a test card to confirm the channel is live.
Remove — the trash icon. Coco Kanban stops posting to that channel. The Teams Workflow itself is untouched, so removing a channel here doesn't break anything on the Microsoft side.

What the messages look like

Each event posts a card into the channel showing the action, the project, and the work item's ID and title, with Priority, State and Project as fields, and a View in Coco Kanban button that opens the work item.

Comment events show the commenter's name and the first 300 characters of the comment.

From the Reports page you can share a report into your connected Teams channels — it's posted as a card with the report title and body. Scheduled digests can also be delivered to Teams on a recurring basis.

Tips

Start with "All projects", then narrow. If a channel gets noisy, add a second channel scoped to the one project the team actually cares about, and remove the broad one.
Turn off "State Changed" for busy projects. It's the highest-volume event by far. Create + Comment is usually the right signal-to-noise mix for a general channel.
One Teams channel, several entries is fine — e.g. one entry for project A and one for project B pointing at the same channel, each with its own event toggles.

Limits & good to know

It's one-way. Coco Kanban posts into Teams. Replies in the Teams channel do not come back as work-item comments, and you can't create work items from Teams.
Notifications only. There's no Teams tab, personal app, or bot you chat with.
The webhook URL is the credential. There's no OAuth handshake — whoever holds the Workflow URL can post to that channel. It's stored masked and is never shown in full again after you add it.
No back-fill. Only events that happen after the channel is connected get posted.
"Assigned" notifications aren't sent. The three supported events are Issue Created, State Changed and Comment.
The Workflow lives in Teams, not here. If someone deletes the Workflow in Teams, the channel goes quiet and Send test will fail — recreate the Workflow and paste the new URL.