Copilot Studio

Copilot Studio Workflow calling agent with input parameters

(1) Share

Report

Posted on by PL-25081330-0

Dear,

From the workflow I'm calling an agent which has input parameters.

The call to the agent:

The agent input parameters:

How can I pass __locale__ parameter to my agent ?

Thanks

Categories:

Autonomous agents

All responses (3)

Answers (0)

Sort by

Suggested answer

Valantis 7,545 Super User 2026 Season 2 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi @PL-25081330-0,

The agent node in a Copilot Studio workflow, when calling an existing published agent, only exposes a single Message field. There is no separate UI field per input parameter, so you can't set __locale__ directly through a dedicated box.

Per the connected/child agent docs, the called agent fills its defined inputs (including __locale__) from the available context of the incoming message, or prompts the user if configured to do so under the input's Advanced settings.

Since there's no explicit parameter mapping UI, the way to get __locale__ populated is to include it in the natural language Message field so the agent can extract it, for example: Locale: fr-FR. <rest of your message/instructions>. If the agent still doesn't pick it up reliably, go to that input's Advanced settings and turn on Should prompt user, so the agent asks for it explicitly if it can't find it in context.

I couldn't find any doc stating __locale__ is auto-populated by the runtime without you passing it. Worth testing both approaches (embedding it in the message vs enabling prompting) and reporting back.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups  @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube
Suggested answer

Mohsin Ali 1,075 on at

Like
a
(1)

Report
Copy link

Link copied!
Hello @PL-25081330-0 - Currently, the Agent node does not expose each agent input as a separate field. It mainly provides the Message input.
As a workaround, pass the locale in the message using dynamic content, for example:

Locale: fr-FR. Process the following request: ...

Then configure the target agent to use that value for __locale__.

If __locale__ is only for language selection, you can also use the agent’s multilingual configuration instead.
Valantis 7,545 Super User 2026 Season 2 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @PL-25081330-0,

Just wanted to check in and see if everything is working now. If you still need any help, feel free to let me know.

Also, if the issue is resolved, it would be great if you could mark the answer as solved so others with the same question can find it easily.

Thanks and have a great day!