--- title: "Microsoft Teams channel" slug: "microsoft-teams-channel" updated: 2026-04-27T19:25:38Z published: 2026-04-27T19:25:38Z canonical: "help.quickbase.com/microsoft-teams-channel" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.quickbase.com/llms.txt > Use this file to discover all available pages before exploring further. # Microsoft Teams channel > *Go to the*[*Channels*](https://team.quickbase.com/nav/main/action/pipelines/channels)*page to learn more about what plans have access to this channel. Sign into Quickbase, and then go to Pipelines > Channels.* Microsoft Teams is a persistent chat-based collaboration platform complete with document sharing, online meetings, and many more extremely useful features for business communications. ## Admin consent workflow You need to work with your Office 365 administrator to setup the admin consent workflow if you will be using `Channel.Create `or `ChannelMessage.Read.All`. Depending on your organization's settings, admin consent might be required for any external application such as Pipelines, so admin consent will be requested for any set of permissions. For more information, learn more about [Configure the admin consent workflow](https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/configure-admin-consent-workflow). ## Connect 1. On the My pipelines page, select **Create Pipeline**. 2. Search for or select a step, and then select it to add it to the pipeline. When you add a step to a pipeline, it is added to the canvas of the pipeline designer. 3. Expand the Connection section of the step, and add the required information. ### Connect to Microsoft Teams 1. Expand Microsoft Teams and select **Connect to Microsoft Teams**.​ You will be redirected to Microsoft Teams to authorize Pipelines: ![Microsoft Teams authorization prompt in Pipelines](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471425789844.png) 2. This is the list of permissions that are required for running specific pipes. Four of them are required to use Pipelines and are selected: - Read all users' basic profiles - Read the names and descriptions of teams - Read the names and descriptions of channels. - Send channel messages Select **Connect to Microsoft Teams**. 3. Your account should have these permissions or you will need an admin approval: ![Microsoft Teams admin approval permissions screen](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471446884500.png) 4. Sign to your account: ![Microsoft account sign-in screen](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471307134228.png) > [!NOTE] > Note: Your functionality and integration may be different depending on your permissions. ## Reconnect You may need to reconnect your account to a channel. Reasons may be (but not limited to): - If you need to connect a different account. - Authorization updates, such as a changed password. - Editing the access rights that Pipelines has to the channel. To reconnect: 1. Select a pipeline that already has this channel in it. 2. Open a step that contains this channel. 3. Under account, select **Connect (or reconnect)** and follow the process above, [Connect](/v1/docs/microsoft-teams-channel#connect). ![Connect or reconnect option in the pipeline step account section](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/17571588306708.png) ## Steps The steps you can use with Microsoft Teams fall under three categories: Channels, Message, and Teams. | Type | Name | Description | | --- | --- | --- | | Channels | | | | Action | Create a Channel | Creates a new channel. | | Action | Look Up a Channel | Look up a channel by id or name. | | Action | Fetch a Linked Channel | Fetches a linked channel. | | Query | Search Channels | Search all channels based on search criteria. | | Messages | | | | Trigger | Message Created | Triggers when a new message is created. | | Trigger | Message Updated | Triggers when a message is updated. The Message Updated pipe triggers when a message in a channel is edited or someone reacts to it with an emoji. Replying to a message does not trigger the pipe. | | Action | Send a Message To Channel | Posts a new message to a channel. | | Action | Reply to a Message | Replies to a message in a channel. | | Action | Look Up a Message | Look up a message by id or name. | | Query | Search Messages | Search all messages based on search criteria. | | Teams | | | | Action | Look up a team | Look up a team by id. | | Query | Search Teams | Search all teams based on search criteria. | All message pipes are for channel messages. We are polling every 5 minutes for messages which means there is a 5 minute delay in the worst case before triggering. ## Limits Four requests per second per app can be issued on a given team or channel. 3000 messages per app per day can be sent to a given channel. When a throttling threshold is exceeded, Microsoft Graph limits any further requests from that client for a period of time. When throttling occurs, Microsoft Graph returns the HTTP status code 429 (Too many requests) and the requests fail. A suggested wait time is returned in the response header of the failed request. Throttling behavior can depend on the type and number of requests. For example, if you have a high volume of requests, all requests types are throttled. Threshold limits vary based on the request type and you could encounter a situation where writes are throttled but reads are still permitted. ## Examples In our example, we have an Opportunities table in our Quickbase app: ![Opportunities table in a Quickbase app](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471425856148.png) Whenever a record is created in the Opportunities table, we want a message with summary to be sent to our team's channel called *Opportunities*. In this use case first we create a trigger - Record Created, we enter the Account and Table fields and then choose the fields on which we trigger. ![Record Created trigger configuration in Pipelines](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471440425876.png)![Trigger field selection in the Pipelines pipeline designer](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471307149716.png) We select **Send a Message To Channel** - choose **Team** from the dropdown then Channel and the Body Content (our message). ![Send a Message To Channel step configuration with Team dropdown](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471425950740.png)![Body Content field in the Send a Message To Channel step](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471447057940.png) The resulting message: ![Resulting message posted to the Opportunities channel in Microsoft Teams](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471440541460.png)