Pass Parameters to Power Automate from Copilot Studio | Day 104
Learn to pass input parameters from Copilot Studio to a Power Automate agent flow using a practical ticket lookup example.
- Published
- Reading time
- 2 min read
Quick answer
Define an input on the agent flow trigger, map the value collected by the agent to that input, validate it, and return the result to the agent.

Week 15 · Day 104 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
- An existing Copilot Studio agent and a compatible Power Automate agent flow.
What you’ll learn
- Input parameters allow one flow to process different user requests.
- Use descriptive names and appropriate data types.
- Map the correct agent value to each flow input.
- Validate inputs and protect sensitive data.
Before you start
- Prerequisite knowledge
- An existing Copilot Studio agent and a compatible Power Automate agent flow.
On this page (7 sections)
Day 104 of 365 Days of Copilot Studio continues the Day 103 ticket lookup. This lesson focuses on passing a value from the agent to a Power Automate flow so the same workflow can handle different requests.
What is an input parameter?
An input parameter is a value sent to a flow when it runs. For example, a user asks, “Check ticket INC-1024.” The agent collects the ticket ID and passes INC-1024 as the TicketID input. A different ID can be sent to the same flow for another lookup.
Define the input in your agent flow
- Open the agent flow in the appropriate environment.
- Select the When an agent calls the flow trigger.
- Add a text input and name it
TicketID. Give it a clear description so its purpose is understandable. - Save the flow and ensure it is available as a tool for your agent.
Choose an input type that matches the value you need. The precise designer options may vary with the experience and configuration.
Map the user's value
Configure the agent or topic to collect the ticket ID and supply it to the flow's TicketID input. Depending on the agent configuration, a value may be gathered during the conversation or mapped from a topic variable. If it is missing or unclear, ask the user for it before running the lookup.
Use the parameter in the flow
Validate the received ID and use it to find the matching ticket in an authorized SharePoint list or Dataverse table. If a record is found, prepare its status; if it is not found or the lookup fails, return a suitable result that the agent can explain. Check the requester's authorization independently: possession of an ID alone does not establish access.
Return the result
Configure Respond to the agent with the output fields needed for the conversation, such as ticket ID and status. The agent can then respond, “Your ticket is In Progress.” Return only necessary information and avoid exposing confidential data or internal error details.
Test the input and response
- In the agent test panel, enter a valid ticket ID and verify that the intended value reaches the flow.
- Check the flow run and confirm that the correct record and status are returned.
- Repeat with a different valid ID, an invalid ID and a missing value.
- Test a nonexistent ticket, an unauthorized user and an unavailable data source; confirm the agent gives an appropriate response.
Five mistakes to avoid
- Wrong data type: match the input definition to the value being sent.
- Missing values: collect required inputs before invoking the action.
- Incorrect mapping: verify that the flow receives the intended agent variable.
- Missing validation: check the input before querying or changing business data.
- Sensitive data exposure: apply appropriate access controls and limit information in outputs and logs.
Clear inputs make flows reusable and easier to test. Day 105 continues with returning outputs to Copilot Studio.
Tagged
AI Agents · Automation · Governance
Frequently asked questions
What is an input parameter?
It is a value passed to the flow so it can process a specific request, such as a ticket ID.
What happens if a required value is missing?
Ask the user for the value or return a clear validation result before running the business action.
How does the agent get the result?
The flow can return defined outputs using its response action, which the agent can use in its reply.
Have a Microsoft 365 topic idea?
Share article suggestions, community session ideas, corrections, or real-world scenarios for future nextM365 learning notes.
Keep learning Microsoft 365
Explore more practical guides for SharePoint, Power Platform, Copilot Studio, migration, automation, governance, and security.
Continue learning
Related tutorials
Related questions
Related comparisons
Next action