![]() Note that ''$'' is a collection of user IDs, so it does not need to be enclosed in quotes to be interpreted correctly. Furthermore, placeholders are also supported here, for which it is important to note which data type they have in order to comply with the JSON syntax. If it is syntactically incorrect, the flow cannot be triggered.Īny data in JSON format can be specified in the payload. The payload, defined in a Teams-Spirit Rule, must be specified in JSON format. If you don't want that, take care to give your flow a unique name.That can be usefull, if a single Rule in the Teams-Spirit Rule-Engine should trigger more than one flow.It is possible to register two or more Flow-Trigger with the same name.None Known issues and limitations Pay attention about duplicate flow names The number of weeks by which the expiration date should be extended The ID of the group in which the expiration date should be extended *Only possible if the account used for the connection in the flow has the role "Spirit-Approver". List of teams spirit tags set for the group ''true'': the group is public, ''false'': the group is private ![]() If present, the date of the last reaction to the approvalĭetermines whether the group should be created for an external user If present the reason for rejecting the approval If available the expiration date of the team ![]() User ID of the user who reacted to the approval User ID of the external user, if the team is to be created for an external user The user ID of the user who requested the approval The username of the user who requested the approval Under the tab ''Custom'' the ''Teams-Spirit'' Connector can be selected, which provides the ''Action-Trigger''.After initially skipping the selection, the user is asked to select a trigger for the flow.Adding the teams-spirit action trigger.If the Teams-Spirit action trigger is not available there, the selection must be skipped. When creating the flow, the user is asked to select a trigger for the flow.Create a new ''Automated Cloud Flow'' in Power Automate.You can send every parameter available in the Teams-Spirit Rule to the Flow and use it to further automate your workflows.Ī new ''Automated Cloud Flow'' must first be created that uses the Teams-Spirit action trigger. Once you have given it a name it will register itself in Teams-Spirit and will be available in the Rule-Engine. If you want a Flow to be triggered by a Teams-Spirit Rule you can create a new Flow with the Action-Trigger. In order to sign-in Teams-Spirit has to be in you Azure ADs Enterprise Applications which will be the case if you are already using Teams-Spirit outside of PowerAutomate. Once you create a Flow using one of the actions or triggers the Teams-Spirit Connector provides, you will be prompted to sign-in. Teams-Spirit Azure AD Enterprise Application (usually this will be present if you are using Teams-Spirit).Overall, there are significantly more actions available than in the default Teams Connector. Users and permissions can also be customized via flow. Conversely, a team's metadata can be modified and augmented by Flow actions. Teams metadata related to a team's categorization, usage, or lifecycle can be used as a trigger for a flow. This connector is available in the following products and regions: ServiceĪll Logic Apps regions except the following:Īll Power Automate regions except the following:Īll Power Apps regions except the following:įor users of the Teams-Spirit enterprise application, the connector provides the ability to automate Teams-related business processes with Flow and connect them to all other applications available in Flow. The Teams-Spirit Connector enables you to connect your Teams-Spirit Subscription to your flows.
0 Comments
Leave a Reply. |