How do I change the output type in a prompt action?

(1) Share

Report

Posted on by AB-12031119-0

Hi all,

I noticed I am forced to do this workaround where I get a record object (which I don't need) and have to transform it into text using the Message action. Is there a way to straight up set up my output as a string from the get-go? Thank you!

Categories:

Building Copilot Studio chatbots in Microsoft Teams

Topic creation & management

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Valantis 5,211 on at

Like (1)

Report
Copy link

Link copied!
Hi @AB-12031119-0,

if you’re using an agent flow called from Copilot Studio, you can return a plain string directly so you don’t have to turn a record into text afterward.

In your agent flow, open the “Respond to the agent” action.

Select Add an output > Text, give it a name, and set its Value to the text you want to return.

Publish the flow. Back in your topic, insert that String_Output variable directly no conversion step needed.

Use input/output variables and add a Text output in “Respond to the agent”: https://learn.microsoft.com/microsoft-copilot-studio/advanced-flow-input-output#add-an-output-parameter-to-the-flow

Example that also ends with a Text output: https://learn.microsoft.com/microsoft-copilot-studio/advanced-flow-list-of-results#format-results

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/

Was this reply helpful? Yes No
Suggested answer

DP_Prabh 361 on at

Like (0)

Report
Copy link

Link copied!
Hi @AB-12031119-0,

No. In Copilot Studio, the Prompt action always returns a record, not a plain string.

What to do instead:
Extract the text field from the record and store it in a string variable.

Example:

Set variable (String) Value = Topic.<PromptName>.predictionOutput.<textField>

Then use that variable directly.

So, the record → text extraction step is currently required.

Was this reply helpful? Yes No