Microsoft Copilot Studio

Return Data from Power Automate to Copilot Studio | Day 105

Learn how to return Power Automate flow outputs to Copilot Studio and turn ticket data into a useful agent response.

Suresh Girinathuni
Published
Reading time
2 min read

Quick answer

Define output parameters in the flow’s response action, map them to the results, and use the returned values in the agent’s response.

An AI assistant receives structured results from an automated workflow.

Week 15 · Day 105 of 365 in 365 Days of Copilot Studio — view the full series

Before you start

Is this guide for you?

Best entry point
365 Days of Copilot Studio
Time investment
2 min read
Prerequisite knowledge
A Copilot Studio agent and a compatible Power Automate agent flow with an input such as a ticket ID.

What you’ll learn

  • Flow outputs pass results back to the agent.
  • Use descriptive output names and map the correct values.
  • Return only the information needed and authorized.
  • Handle errors and test the complete interaction.

Before you start

Prerequisite knowledge
A Copilot Studio agent and a compatible Power Automate agent flow with an input such as a ticket ID.

Day 105 of 365 Days of Copilot Studio continues the Day 104 ticket lookup. After an agent passes a ticket ID to a flow, the flow can return the result for the agent to explain.

What are flow outputs?

Outputs are values returned by Power Automate to the calling agent. In our example, the flow looks up ticket INC-1024 and returns a status such as “In Progress.” The agent can use that value to give the user an answer based on the retrieved record.

From request to response

  1. The user asks to check a ticket.
  2. The agent calls the flow with the ticket ID.
  3. The flow retrieves the authorized ticket information and returns the required result.
  4. The agent uses the output to respond.

Configure a response action

  1. Open the compatible agent flow and select or add Respond to the agent.
  2. Add an output parameter with a descriptive name, such as TicketStatus, and choose the appropriate type.
  3. Map the output to the actual status retrieved by the flow.
  4. Save and publish the flow, then check that the agent tool exposes the expected output.

Designer options can vary by experience. Confirm the flow and agent are configured in the appropriate environment and test the published configuration.

Use the result in Copilot Studio

Configure the agent or topic to use the returned TicketStatus value in its response. For example, it can say, “Your ticket INC-1024 is In Progress.” Ensure the answer reflects the returned result rather than a hard-coded example.

Return multiple values

A flow can return several defined outputs, such as TicketID, TicketStatus, an assigned team and priority. Map each value to its corresponding field and include only the information the agent needs and the user is authorized to see.

Make the integration reliable

  • Use clear parameter names and appropriate types so inputs and outputs are easy to understand.
  • Validate the ticket ID and check the requester's access before retrieving data.
  • Return a meaningful outcome for a missing record or service failure without exposing sensitive internal details.
  • Account for supported response time limits and use a separate follow-up for longer-running processes.
  • Test a valid ticket, missing or invalid input, unauthorized access and a failed connection; verify the actual flow output and the agent's response.

Return the smallest useful set of results and review the flow's run history when troubleshooting. Clear output contracts help the agent turn business data into a useful conversation.

Share this

Tagged

AI Agents · Automation · Governance

Frequently asked questions

What is a flow output?

A flow output is a value returned by the flow for the calling agent to use, such as a ticket status.

Can a flow return multiple values?

Yes. Define the required output parameters and map each to the corresponding result.

What if the flow cannot retrieve the data?

Handle the failure and return an appropriate outcome so the agent can explain the problem without exposing internal details.

Have a Microsoft 365 topic idea?

Share article suggestions, community session ideas, corrections, or real-world scenarios for future nextM365 learning notes.

Discuss your project requirements

Keep learning Microsoft 365

Explore more practical guides for SharePoint, Power Platform, Copilot Studio, migration, automation, governance, and security.

Continue learning

Next action

What to do next

Browse all tutorials →