If your team lives in Microsoft Teams, tickets sitting silently on a kanban board don't help anyone. With the Todo4you Teams integration you push every relevant update straight into the channel where work is actually being discussed - and the message is a proper Adaptive Card with buttons, not a wall of plain text.
This post covers what lands in Teams, what it looks like, how to set it up in a few minutes, and a few tips for keeping the channel useful rather than noisy.
What arrives in Teams
Every card follows the same shape: a short headline, the ticket reference and title, the project it belongs to, and action buttons that take the recipient back to the ticket in one click. You choose which events the channel receives when you set up the integration. The available events are:
- Ticket created - someone opened a ticket in this project.
- Ticket moved - a ticket changed status column (for example, from To do to In progress).
- Ticket updated - the title, description, priority, deadline, or tags changed.
- Ticket deleted - a ticket was removed.
- Comment posted - someone commented on a ticket.
- Timer started / stopped - a teammate started or stopped the built-in time tracker on a ticket.
Each card includes the actor (who triggered the event), the relevant fields that changed, and an Open ticket button linking back to Todo4you. For move events the card also shows old and new status side by side, so you can scan the change without opening the ticket.
Because Teams renders Adaptive Cards natively, the message looks like something Teams itself might send - not a generic bot post.
Why a channel and not a chat
The integration posts to a channel, not to a chat. In Teams vocabulary:
- A channel is a topic-based section inside a Team (
#general,#design,#platform-alerts). Anyone in the Team can join it and the message history is persistent. - A chat is a separate 1:1 or group direct message outside any Team.
Channels are the right home for project notifications because they're durable, searchable, and already attached to the people who care about the work. The integration relies on Microsoft's Workflows feature (the successor to the legacy Office 365 connectors), and Workflows only fire into channels.
One important note: Workflows require a Microsoft Teams work or school account. The free personal tier of Teams runs on Communities instead and does not support Workflows. If the "Workflows" option is missing from your channel's three-dot menu, that's almost always why.
Setting it up
You need two things: a channel where notifications should land, and a workflow that accepts webhook requests from Todo4you. It takes about two minutes end to end.
- Open the channel. In Microsoft Teams, open the channel where you want notifications to appear. If you don't have a channel yet, click the three-dot menu next to a Team name and choose Add channel.
- Start a Workflow. Click the three-dot menu next to the channel name and choose Workflows. In the template list, pick Post to a channel when a webhook request is received. Give the workflow a name (Todo4you notifications works well), confirm the team and channel, and click Add workflow.
- Copy the webhook URL. Teams will generate a URL that starts with
https://prod-...logic.azure.com/workflows/.... Copy the whole thing. - Create the integration in Todo4you. In your project, go to Settings -> Integrations -> Microsoft Teams. Paste the webhook URL, pick which events the channel should receive, and save.
- Send a test message. The integration page has a Send test message button. Use it once to confirm the card arrives in the right channel. If it doesn't, double-check the channel in Teams (it's easy to accidentally target General in the wrong Team).
That's it - from the next ticket event onwards, the channel will keep itself up to date.
Tips for a useful, not noisy, channel
Notification channels go bad fast if they get spammed. A few habits that keep them useful:
- Pick one project per channel. Don't fan every project into
#general. Most teams end up with a dedicated#t4y-<project>channel per active project. - Drop the events you don't read. For most teams, Ticket created, Ticket moved, and Comment posted are enough. Skip Timer started/stopped unless you want a running log of billable time.
- Mute, don't leave. If the channel gets quiet-chatty, set it to Only show in channel list so mentions still notify you without the badge count stress.
- Pair it with the Git integration. If you already have GitHub, GitLab, Gitea, or Bitbucket wired up, Todo4you can auto-move tickets on PR events and announce those moves in Teams. You get a continuous narrative: "Jorden merged #142 -> ticket TDL-47 moved to Review" without anyone typing a status update.
- Treat the webhook URL like a password. Anyone with it can post to your channel. If a URL leaks, delete the workflow in Teams and generate a new one - the integration config in Todo4you will tell you when it's been revoked.
Ready to try it?
Open any project and head to Settings -> Integrations -> Microsoft Teams. The setup page has the steps laid out with screenshots and a Send test message button so you can verify the connection before turning real traffic on. If you run into anything weird, let me know - info@todo4you.com.