A core component of Encodian Trigr is the 'When a user runs a Trigr' Power Automate trigger action which is available via our Power Automate connector (Flowr).
You can find the 'When a user runs a Trigr' Power Automate trigger action within Power Automate via the 'Encodian' standard connector
Note: You do not need to purchase a Flowr subscription to use the 'When a user runs a Trigr' Power Automate trigger action, this is covered by a Trigr subscription.
To create a Trigr 'Action' please refer to: Create a Trigr 'Action'
After adding the Encodian Trigr is the 'When a user runs a Trigr' Power Automate trigger action to a flow you'll be prompted to enter a 'Title' and 'Description' which is later available within the Encodian admin portal and used to identify the flow.
Using data provided by the 'When a user runs a Trigr' action
Please review the following video tutorial or/and the information provided within this section:
The 'When a user runs a Trigr' Power Automate trigger action provides all of the properties relevant to the SharePoint items / documents which were selected by the user when the Trigr 'Action' was started within the SharePoint app. The following properties are available:
Site Address: The SharePoint site address
Library/List ID: The source SharePoint Library/List ID
Library/List Name: The source SharePoint Library/List Name
Forms Fields: Dynamic form data provided by the user
User Email Address: The email address of the user who triggered this flow
File Identifier: The select file identifier, or the first file identifier in the 'File Identifiers' array
File Identifiers: A collection of file identifiers for the selected files
Item: The select item ID, or the first item ID in the 'Items' array
Items: A collection of item ID's for the selected items
These properties allow you to easily access the SharePoint list items or files selected by the user when the flow is executed.
However, be mindful of the limitations of Power Automate when working with dynamic fields as opposed to fixed values when building flows. As per many of the connectors across Power Automate; when you enter a dynamic value as opposed to a typed value into the SharePoint connector actions you will not be able to access the properties provided by the SharePoint action, for example:
To work around this issue is very simple; When creating your flows use hard-coded values and once you have completed the configuration simply go back and replace the hard coded values with the dynamic properties: