Power Automate Flows

21/07/2026

Connectors 1.0 // GW4M365

Note

This functionality is currently in beta and will be included in a future release.

GW4Copilot relies on five Power Automate flows to process requests. These flows direct requests to Azure Functions or the Graph Modeling server to process, handle responses, format the returned data, and pass results back to the Copilot agent.

This section provides an overview of the five Power Automate flows used by the agent. Expand each flow to view detailed information about its purpose, functionality, and role in the overall process.

This flow processes files uploaded by the user through the CoPilot agent. It converts the file content to Base64 encoding and sends it to the Graph Modeling server for tag extraction. After processing, the server returns a list of tags for each file, including the tag name, relevance score, URL, and display name. The flow uses the GetTagsFromParameters custom connector method.

Input parameters:

taxonomyId (string): GUID ID of the selected taxonomy to use for tags extraction.
uploadedFile (array): JSON array containing the uploaded file data in the format required by the Microsoft Teams app.

Note

Code marked in red is always present, no matter how many files are uploaded and must be excluded from processing.

Output parameters:

Extracted tags: JSON object with headers and string representation of JSON array files and their respective tags as body content.

This flow takes text sent by the user to the CoPilot Agent and transforms it to Base64 encoding to send to Graph modeling for tags extraction. After extraction, tags are returned to the CoPilot Agent as a list of tags with a score, URL, and display name. The flow uses the GetTagsFromText custom connector method.

Input parameters:

taxonomyId (string): GUID ID of the selected taxonomy to use for tags extraction.
TextContent (string): Plain text sent by the user to the CoPilot Agent for tags extraction.

Output parameters:

Extracted_tags (string): JSON object containing response headers and a body that contains a JSON array represented as a string. The array contains a single item representing the submitted text and its associated tags.

This flow sends the selected tags into Azure function, which builds SharePoint Search REST API request and returns all files, which have those tags associated with them.

Input parameters:

URIsArrayJson (string): JSON array of selected tags uris.
UniqueFilenames (bool): Defines if only unique names from the search results should be returned, or if the same file name from different locations in SharePoint are returned.
siteURL (string): The URL of the SharePoint search scope, to which the results should be narrowed down.

Output parameters:

Documents (string): JSON array of all documents sorted by the summary of the searched tag score in each file.

In this section: