Configure MS Teams to Receive Status Updates from Fluid Boards

Edited

Fluid boards can be configured to integrate with a Microsoft Teams chat or channel, sending task update notifications, using webhooks, directly to the chat or channel when there is a new task or the status or due date of a task changes. This guide walks you through the setup process for a Teams Channel from start to finish.


What You Need Before You Start

Before configuring the integration in Fluid, you will need:

  • Access to the Microsoft Teams channel where the webhook will be created

  • Permission to add workflows/apps in that channel

  • Allow MS Teams Webhooks enabled (please contact your CSM or Fluid Support)

  • Board Owner permissions in Fluid to update the Teams Integration token


Steps to Setup the Integration

1. Open the Team and Channel in Microsoft Teams

Navigate to the channel where you want Fluid notifications to appear.

2. Create the Workflow

  1. Click the … (More Options) next to the channel name

  2. Select Workflow

  1. Search for “Send webhook alerts to a channel”

  2. Select it

  1. Select the Team the channel is in and the Channel the alerts should be sent to.

  2. Click 'Save'

3. Copy the Generated Webhook URL

  1. After saving, Microsoft Teams will display a unique Webhook URL.

  2. Click 'Copy webhook link' in the Teams Workflow dialogue

4. Add the Webhook URL to Fluid

  1. Navigate to the board you want to push notifications from in Fluid

  2. Click 'Tools' > 'Setup Integration'

  1. Click the '+ Add Integration' button

  1. Select the 'MSTeams' icon

  2. Click the 'Setup' tab

  3. Add a descriptive title will help you identify the integration

  4. Paste the Webhook URL into the 'Incoming Webhook Url' field

  5. Click the 'Save' button to save your changes

That's it; you're all done!

Now when the status, or due date of a task changes, you will receive automatic status updates to your Teams Channel.

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.