Microsoft Teams
Introduction
Microsoft Teams is a collaboration platform designed for teams, businesses, and organizations of all sizes. With its real-time communication and collaboration features, it makes it easy to integrate into media workflows, keeping teams connected and productive, whether working remotely or in person.
You can find more details and the supported operations on Microsoft Teams | qibb Catalog.
Since the update on 07/23/2024, Microsoft retired the connector and migrated it to a new workflow feature. You can read more about it on the following page: https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/.
The following guide showcases how to use the Workflows app. However if you are still using Office 365 connectors you can checkout this guideline.
How to get started with Microsoft Teams integration (Webhooks)
Go to the Workflows app in Teams and click on the
"Create"
tab
Set up webhook configurations.
Once you're here, you can set up the configuration for your webhook. You can either choose a template or create one from scratch. In this case, we will select a template to Post to a channel when a webhook request is received.
Customize the template as needed with your Workflow name, Team, and Channel.
Finally, copy and use the webhook URL within your MS Team Node.
Use the webhook with the MS Teams node
Important
Please keep in mind that this template has by default an action that work with adaptive cards. You can change this default configuration and add a different action as needed in the Edit
section of your workflow.
Send Adaptive Cards
Drag the Microsoft Teams Webhook Connector node from the left sidebar and place it in your flow.
Open the node by double-clicking it, and ensure you use the Microsoft Teams Webhook 1.0 - Workflows connection.
Add the workflow URL to the flow by either:
Using the webhook helper: Copy your workflow URL into the inject node (as shown in the flow example).
Extracting the components from the workflow URL: Extract the host and query parameters from the workflow URL and use them within your node (example below).
Example how to extract data from workflow URL:
Workflow Url:
https://prod-***.westeurope.logic.azure.com:443/workflows/host****/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=sig****
Extracted Parameters:
Parameter in Microsoft Teams node | Value |
---|---|
Host |
|
Api-Version |
|
Sp |
|
Sv |
|
Sig |
|
Customize your adaptive card.
To design your adaptive card you can use the following page: https://adaptivecards.io/designer.
Once you have your adaptive card payload replace the body in the Microsoft Teams node with the body of your adaptive card.
Body:
{
"attachments": [
{
"contentType": "application/vnd.microsoft.card.adaptive",
"content": {
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.4",
"body": [
/// Paste here your adaptive card body.
]
}
}
]
}
With the node configured deploy and trigger the flow. You should now observe the adaptive card within the selected Channel.
Send Plain Text
As mentioned earlier, the chosen template for posting to a channel when a webhook request is received is configured by default to receive an adaptive card in the request body. To modify this configuration and send simple text in the request body instead, please follow these steps.
Insert a new action configuration
Choose an operation
Navigate to Standard
→ Microsoft Teams
→ Actions
→ Post Message in a Chat or Channel
Configure each field with the desired destination value, and add to the message field the following dynamic expression.
triggerBody()['message']
This is an expression configuration to send dynamic content via payload. If you want to set static content, please remove it and hardcode the desired value.
Finally, with your webhook configured, use the workflow URL to utilize the qibb node.
Use the following body in your Microsoft Teams node to send your dynamic content.
{
"message": // your content here.
}
How to get started with Microsoft Teams integration (Office 365 Connectors) deprecated
Before you get started creating Microsoft Teams integration in qibb please make sure that your account has permission to create connectors and post messages because you will need to create certain settings. Here you can find MS Teams Webhooks documentation.
Open Microsoft Teams and click on the horizontal dots on the channel you would like to use for your qibb workflow. Click on the Manage Channel button.
Navigate to Settings and open the expandable “Connectors” section. Click on the Edit button.
Locate the Incoming Webhook Connector and click on Add button. If you have already had a webhook, click on the Configure button.
Name your new Incoming Webhook, customize your image as desired and click on the Create button.
Copy your URL for use in the Flow Editor and click on the Done button.
Go to the qibb Flow Editor, open the Node Catalog in the right sidebar and install the Microsoft Teams node by clicking on the + button.
Drag the Microsoft Teams Webhook Connector node from the left sidebar and place it in your flow.
Make sure Microsoft Teams Webhook 1.0 - Connector is selected as connection, enter the Webhook URL into the Host field & you can start using the node!
Importing flow examples of a node
Once you've successfully installed a node from the qibb catalog, you can easily import example flows that showcase how the nodes can be used. These example flows are directly accessible within the Flow Editor and are designed to guide users with helpful hints, including how to configure mandatory parameters and credentials.
Here's how to import examples:
In the top right corner of the Flow Editor, click on the menu icon.
Select Import to open the Import Dialog.
Click on the Examples tab.
Choose an example from the list.
Confirm your selection by clicking on the Import button.
By following these steps, you are now ready to make basic API calls using the provided examples. For further exploration of what’s possible, you can find more complex examples in the Flow Catalog.