Apr 25, 2023 10:17:09 AM
Oct 11, 2022 10:42:03 AM
Qlik Application Automation includes a connector block for Microsoft Teams. You have multiple Microsoft Teams templates available when creating a new Automation, which will guide you through the process.
This article highlights the blocks applicable when sending messages.
Example Automation:
For additional information on requirements and message possibilities, see How to get started with Microsoft Teams in Qlik Application Automation.
Available Blocks
The Microsoft Teams Connector will list a number of different blocks for you to choose from.
The following are used to send chat messages to existing chats, or you can send messages to new chats:
- Create chat: Used to create a new chat. The block takes a topic and chat members as input. The topic is only applicable for group chats (chats with more than two members). A chat between two members is called a one-on-one chat. Only one one-on-one chat can exist between two chat members, so should one already exist, the existing chat id will be returned. The members that are added to this block must include the user who initiates the create request.
- Get Chat: Enables you to get a chat object, excluding messages, by providing a chat ID. The response includes chat members. The chat ID can be retrieved using the List Chats block.
- List Chats: Enables you to retrieve all the chats that you are a part of. It is possible to include a query phrase that is case sensitive to filter the result based on topic. This is only applicable for chats of the type group and meeting. Since one-on-one chats don't have a title, this would be ignored. It is also possible to include filtering of chats based on type: group, meeting or oneOnOne.
- Send message to existing chat: Enables you to send a message to an existing chat by specifying the chat ID.
- Send message to new chat: Enables you to send a chat message to a chat that previously didn't exist. For group chats you may include a topic.
Environment
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
