User Community Service Desk Downloads

Send Notifications to MS Teams

Ataccama ONE can send alert notifications to Microsoft Teams channels using incoming webhooks. Unlike Slack and Jira integrations, MS Teams does not require a connection in Global settings. Instead, you configure a webhook in MS Teams and provide the webhook URL when creating an audience.

Prerequisites

  • You need access to a Microsoft Teams channel where you want to receive notifications.

  • You need permission to add Workflows connectors to the channel.

Add an incoming webhook to MS Teams

  1. In MS Teams, select the channel where you want to receive notifications and open the three-dot menu.

  2. Select Workflows.

  3. Locate and select Post to a channel when a webhook request is received.

  4. Provide a name for the workflow and select Next.

  5. Select the Teams channel to receive notifications.

  6. Copy the generated webhook URL and save it for later.

    You need to provide this URL when creating an audience in Ataccama ONE.

  7. Select Done.

The webhook is now configured. You can view and edit your configured webhooks from the Workflows tab in MS Teams.

Add MS Teams to an audience

Once you have the webhook URL, add MS Teams as a notification channel when creating or editing an audience:

  1. In Ataccama ONE, go to Global settings > Notifications > Audiences.

  2. Create a new audience or edit an existing one.

  3. Select the MS Teams checkbox.

  4. Enter the Webhook URL you copied from MS Teams.

  5. Enter the Channel name to identify the channel.

  6. Select Add another to include additional MS Teams channels if needed.

  7. Select Save.

For more information about creating audiences, see Create an Audience.

Troubleshooting

The webhook returns HTTP 202 Accepted but notifications don’t appear

The incoming webhook API processes requests asynchronously, which can cause delays. If notifications don’t appear, check your Workflows processing details on the Workflows tab in MS Teams. Requests typically fail due to invalid message format.

Next steps

Was this page useful?