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
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, see this guide - Configure the admin consent workflow.
How to Connect
- On the My pipelines page, click Create a pipeline. Enter name, description, and tag fields and click the Create Pipelines button. The pipelines wizard displays:
- From the wizard you choose the connections for the first steps of your pipeline. When you choose a type, you'll add the channels and steps for your first steps. You can always add more steps later. A Triggered pipeline is started by a specific event in real-time. A Scheduled pipeline will start according to a schedule. A Manual pipeline only starts manually. Once you've completed the wizard, you'll be prompted for connection detail, if necessary. If you are an experienced builder, click the Start from scratch button and then from the right side of the page, choose the All to list all available channels.
- Expand Microsoft Teams and click Connect to Microsoft Teams. You will be redirected to Microsoft Teams to authorize Pipelines:
- 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
Click Connect to Microsoft Teams.
- Your account should have these permissions or you will need an admin approval:
- Sign to your account:
Note: Your functionality and integration may be different depending on your permissions.
How to reconnect the Microsoft Teams channel
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.
Connect to Microsoft Teams
- Select a pipeline that already has Microsoft Teams in it.
- Open a step containing Microsoft Teams.
- Under account, select Connect (or reconnect) and follow the process above, How to connect.
The steps you can use with Microsoft Teams fall under three categories: Channels, Message, and Teams.
|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.|
|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.|
|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.
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.
In our example, we have a Opportunities table in our QuickBase App:
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.
We select Send a Message To Channel - choose Team from the dropdown then Channel and the Body Content (our message).
The resulting message: