--- title: "M365 Teams Connector" slug: "microsoft-teams-connector" updated: 2024-04-04T20:19:27Z published: 2024-04-04T20:19:27Z --- > ## Documentation Index > Fetch the complete documentation index at: https://support.tulip.co/llms.txt > Use this file to discover all available pages before exploring further. # Microsoft Teams Connector To download the app, visit: [Library](https://tulip.co/library/connectors/microsoft-teams-connector/) ## Microsoft 365 Connector *For integration with Microsoft apps like Teams, Outlook, and Office Suite.* ## Purpose Use this document to integrate your Tulip Apps with Microsoft 365 products like Teams, Office Suite, and Outlook. ## Pre-Requisites Note: Oauth2 authentication information must be generated in Entra ID before using this Connector. Follow this guide to generate the required credentials. [Connect the MS Graph API to Tulip with Oauth2](https://support.tulip.co/docs/connect-the-microsoft-graph-api-to-tulip-with-oauth2) ## API Doc [Microsoft Graph API Documentation](https://docs.microsoft.com/en-us/graph/api/resources/team?view=graph-rest-beta) ## Scopes Needed for this Connector ## Connector Functions #### 1) Get all Teams **Purpose** This connector will fetch all the teams a user is a part of using their Microsoft teams account. **Endpoint** ``` HTTP GET call to the endpoint - https://graph.micrsoft.com:443/v1.0/me/joinedTeams ``` **Required Input** No Inputs required **Required Output Extractor** 1. teamID: Unique identifier of the Team which will be used to carry out the other tasks. 2. teamName: The display name of the Team. 3. teamDescription: The description of the Team. #### 2) Get all Channels of a Team **Purpose** This connector will fetch all the channels of a team by passing the teamID as input. **Endpoint** ``` HTTP GET call to the endpoint - https://graph.microsoft.com:443/v1.0/teams/{teamID}/channels ``` **Required Input** The following are the URL parameters that are to be passed 1. Team Id **Required Output Extractor** 1. channelId: Unique identifier of the Channel which will be used to carry out the other tasks. 2. channelName: The display name of the Channel. 3. channelDescription: The description of the Channel. #### 3) Create a New Channel **Purpose** 1. Users can pass a Team ID, Channel Name and Channel Description as input & Tulip will create a new channel with channel name provided. The response of the API will be the metadata and various properties of the channel. This can be further used to fetch and Update data from the channel. 2. Information is pulled from Microsoft Graph V1.0 API can then be further used either within Tulip apps, Tulip tables, or Tulip variables which would be piped into other connector functions. **Endpoint** ``` HTTP POST call to the endpoint - https://graph.microsoft.com:443/v1.0/teams/{teamID}/channels ``` **Required Input** The following are the parameters that are sent as the Request Body 1. Team ID 2. Channel Name 3. Channel Description **Required Output Extractor** 1. channelId: Unique identifier of the Channel which will be used to carry out the other tasks. 2. channelName:The display name of the Channel. 3. channelDescription:The description of the Channel. #### 4) Update Channel Properties **Purpose** 1. Users can pass a Team ID, Channel ID, New Channel Name, and New Channel Description as input & Tulip will update a new Channel with the new channel name and description provided. The response of the API will be the metadata and various properties of the channel. This can be further used to fetch and Update data from the channel. 2. Information is pulled from Microsoft Graph V1.0 API can then be further used either within Tulip apps, Tulip tables, or Tulip variables which would be piped into other connector functions. **Endpoint** ``` HTTP PATCH call to the endpoint https://graph.microsoft.com:443/v1.0/teams/{teamID}/channels/{channelID} ``` **Required Input** The following are the parameters that are sent as part of URL and/or Request Body 1. Team ID 2. Channel ID 3. Channel Name 4. Channel Description **Required Output Extractor** We don’t require any output extractor. #### 5) Send a Message to a Channel **Purpose** Users can pass a Team ID, Channel ID, Subject, and Message Content as input & Tulip will send a message with message content provided. **Endpoint** ``` HTTP POST call to the endpoint - https://graph.microsoft.com:443/v1.0/me/teams/{teamID}/channels/{channelID}/messages ``` **Required Input** The following are the parameters that are sent as part of URL and/or Request Body 1. Team ID 2. Channel ID 3. Subject 4. Message Content **Required Output Extractor** We don’t require any output extractor. #### 6) Get all Messages of a specific Channel **Purpose** This connector will fetch all the messages from a specific channel. **Endpoint** ``` HTTP GET call to the endpoint - https://graph.microsoft.com:443/v1.0/teams/{teamID}/channels/{channelID}/messages ``` **Required Input** The following are the URL parameters that are to be passed. 1. Team ID 2. Channel ID **Required Output Extractor** 1. messageId: Unique identifier of the Message which will be used to carry out the other tasks. 2. messageContent: The content of the Message. 3. messageFrom: The display name of the Sender. #### 7) Reply to a Message **Purpose** Users can pass a Team ID, Channel ID, Subject, and Message Content as an input to reply to a message & Tulip will send a reply with message content provided. **Endpoint** ``` HTTP POST call to the endpoint - https://graph.microsoft.com:443/v1.0/me/teams/{teamID}/channels/{channelID}/messages/{messageID}/replies ``` **Required Input** The following are the parameters that are sent as part of URL and/or Request Body 1. Team ID 2. Channel ID 3. Message ID 4. Message Content **Required Output Extractor** We don’t require any output extractor. #### 8) Delete a Channel **Purpose** Users can pass a Team ID and Channel ID as input & Tulip will delete the specific channel with the provided inputs. **Endpoint** ``` HTTP DELETE call to the endpoint -https://graph.microsoft.com:443/v1.0/teams/{teamID}/channels/{channelID} ``` **Required Input** The following are the URL parameters that are to be passed 1. Team ID 2. Channel ID **Required Output Extractor** We don’t require any output extractor. #### 9) Get the list of Members for a team **Purpose** This connector will fetch all the members of a specific team. **Endpoint** ``` HTTP GET call to the endpoint https://graph.microsoft.com:443/v1.0/teams/{teamID}/members ``` **Required Input** The following are the URL parameters that are to be passed. 1. Team ID **Required Output Extractor** 1. Member Id: Unique identifier of the Member. 2. Member Name: The display name of the Member. 3. Member EmailID: The email ID of the Member. 4. Member Role: The role of a member in the Team Channel. ## Further Reading Check out more information regarding Microsoft Connectors - [Microsoft Calendar Connector](https://support.tulip.co/docs/microsoft-calendar-connector) - [Microsoft Outlook Connector](https://support.tulip.co/docs/microsoft-outlook-connector) - [Microsoft Excel Connector](https://support.tulip.co/docs/microsoft-excel-connector)