---
title: "Send a notification to a Teams Chat in Boomi (and get started with Microsoft Graph API)"
canonical: "https://kb.uconn.edu/space/SIM/26418905296/Send%20a%20notification%20to%20a%20Teams%20Chat%20in%20Boomi%20(and%20get%20started%20with%20Microsoft%20Graph%20API)"
format: markdown
---
> ℹ️ From Microsoft: The **Microsoft Graph API** offers a single endpoint, `https://graph.microsoft.com`, to provide access to rich, people-centric data and insights in the Microsoft cloud, including Microsoft 365, Windows, and Enterprise Mobility + Security
Microsoft Graph API can be used for a vast array of integrations with Microsoft products used at UConn, such as Outlook Mail and Calendar, OneNote, OneDrive, SharePoint, and more. Many groups communicate mainly through Teams, so we thought that a Teams message would be the best way to alert a group about a problem with a Boomi integration.
You must first ensure the M365 service account utilized by your Boomi subaccount has the required permissions to interact with any particular Microsoft Graph API. For this example, we’ll reference a service account of [boomi-notify@uconn.edu](mailto:boomi-notify@uconn.edu).
Before building the process in Boomi, we added the [boomi-notify@uconn.edu](mailto:boomi-notify@uconn.edu) user to a group chat:
We needed the ID of the chat, which we found by using the [Microsoft Graph Explorer](https://developer.microsoft.com/en-us/graph/graph-explorer) via our [boomi-notify@uconn.edu](mailto:boomi-notify@uconn.edu) account and sending a GET to
```json
https://graph.microsoft.com/v1.0/me/chats
```
> ⚠️ You must first add your service account to a Teams chat for Graph Explorer to return the respective chat IDs. If you receive an empty 200 response, the account is not a member of any Teams chats.
> ⚠️ This article is intended for individuals who have a Boomi Associate Integration Developer Certification. If you do not know how to complete an action like “add a message shape,” please complete the recommended trainings.
## \uD83D\uDCD8 Instructions
The message that is most helpful to send in teams will be particular to your use case. For this guide we decided to call an API that returns a random quote in JSON format and send that to our Teams chat. This simple process looks like:
You can do the same, add complexity or remove complexity up to the Map shape.
1. Whatever precedes the map shape (Teams content ff to json) needs to be mapped to the proper JSON format, defined in the *Teams Message JSON profile*. Your map shape should populate the content element as shown below
2. The Map shape connects to an HTTP Client Connection. The Connections looks like:
| **URL: **[https://graph.microsoft.com](https://graph.microsoft.com)
**Authentication Type**: OAuth 2.0
**Grant Type**: Authorization Code
**Client ID**: *find in Last Pass*
**Client Secret**: *leave blank*
**Authorization Token URL**: [https://graph.microsoft.com](https://graph.microsoft.com)
**Scope**: ChatMessage.Send offline_access ChannelMessage.Send
**Access Token URL**: [https://login.microsoftonline.com/17f1a87e-2a25-4eaa-b9df-9d439034b080/oauth2/v2.0/token](https://login.microsoftonline.com/17f1a87e-2a25-4eaa-b9df-9d439034b080/oauth2/v2.0/token)
**Refresh Authorization Scheme**: Refresh Body Parameters |  |
| --- | --- |
3. The Teams Post Operation looks like:
| **Select Request Profile Type**: JSON
**Request Profile**: Teams Message JSON
**Select Response Profile Type**: None
**Content Type**: application/json
**HTTP Method**: POST
_______________________________________________
In **Request Headers** Add
Name = Accept and Value = **/ **
________________________________________________
In **Resource Path** Add
Name = v1.0/chats/{your chat id here}/messages |  |
| --- | --- |
4. Add a Stop shape to the Http Client Connector
5. Click the Test button on the Process Pallet
6. Select the appropriate test atom cloud:
7. You should see a Teams notification on the chat id you specified:
8. You should also see the green halos around each shape in the Process Pallet as Boomi moves successfully through the steps:
You should now be able to re-use this same HTTP Client configuration to send appropriate teams messages within your Boomi process or change the operation (and scope) and implement other Microsoft Graph API calls.
## \uD83D\uDCCB Related articles
> Macro (contentbylabel)