Powell Teams authorizes users with the Automation service to add additional functions and logic to the team or SharePoint site, created through a Powell Teams template.
Powell Teams automation service supports three connector types:
- Azure Automation
- Azure functions
- Power Automate
They can be associated with a Powell Teams template and executed at the end of a team or SharePoint site creation, after an approval workflow has been sent, or after a report creation
With Azure Automation, users will create a code in Azure and link it to Powell Teams. They will be able to import any functionality they need.
How to use the Powell Teams Automation service
Step 1: Link your flow in Powell Teams in the automation section.
- Go to the "Control" section of the Powell Teams menu and click the page "Automation".
- Click on the button "Create a new automation."
- Start filling in the form:
- Name: choose the name of the function
- Description: write a description of the function
- Trigger: select the trigger.
1. After approval workflow request is sent: This trigger will run when the approval request is made. It allows, for example, to notify a 3rd party app like ServiceNow that you need to manage action in Powell Teams.
2. After application of a team template: The trigger will run after the application of the template. So after team creation or template association on an existing team.
3. After a tag value change in an existing team: All along a team lifecycle, its information can evolve following a business process. It is possible to be informed about a team's tag value change with automation.
4. When a team arrives in a report: this type of automation can be associated with a campaign to trigger a flow each time a new team arrives in the report associated with the campaign.
5. After the application of a SharePoint template: The trigger will run after the application of the template. So after site creation or template association on an existing site.
- select the type of automation you want to associate from Power Automate, Azure function, and Azure automation
- Add the HTTP URL where you want to be triggered
Powell Teams only support anonymized URLs, authenticated
Powell Teams only support anonymized URLs into the HTTP POST URL in the automation configuration.
Just below, you have the list of details displaying the information that will pass through depending on the type of trigger chosen. Here is an example of an "After application of a team template".
- Team ID
- Team name
- Template ID
- Template name
- Owners of the team
- Members of the team
- Requestor ID: who does the actual request come from (requestor does not necessarily have to be the owner)
- Tag values: tags assigned to that particular team
You also have a JSON schema example of what you will receive after the automation has been triggered. This schema can be downloaded to help you to construct your scenario easily.
When an automation is already associated with a template, you can see the list of templates associated with the automation as you scroll down.
Step 2: Associate your Powell Teams automation to your Powell Teams template, tag, or report:
Associate your Powell Teams automation to your Powell Teams template:
- Go to the "Templates" page in the administration menu
- Choose the team or site template from the list
- Go to the governance tab in the template settings
- Go to the "Automation" section in the template settings
- Choose the automation you created from the dropdown list
You can now associate multiple automation in a Powell Teams template to trigger multiple events. Note: there is no order in the automation executions, all are launched at the same time.
- Save the changes
Associate your Powell Teams automation to your tag:
Go to your tags and edit or create a new one; you will find an option to associate existing automation with your tag.
Step 3: Action the trigger or wait for the automation to be triggered
Depending on the type of trigger you choose, you can trigger the automation manually if the trigger is awakened after the application of a template, after an approval request, or after a tag value change.
Find the Microsoft documentation explaining how to use an HTTP webhook with Logic Apps.