Document Upload in Copilot Studio

(3) Share

Report

Posted on by CU04020731-1

Hi Team,

I need to handle a scenario where a user uploads a document through Copilot Studio (published in Teams), and I want to save the document to base64 and send it to a Power Automate flow. Can you suggest a solution for this?

Categories:

Copilot Studio skills development

I have the same question (0)

All responses (3)

Answers (0)

DougM_Barhead 25 on at

Like (0)

Report

It appears this is not possible. My earlier post.

https://community.powerplatform.com/forums/thread/details/?threadid=24519333-bce9-ef11-a731-000d3a55d9c6

Pls let me know if you manage to achieve this.

You can catch the event of the document being attached which you can extract as a variable of type "file" in Copilotstudio.

Power Automate will allow you to specify a variable of type "File" as input (from Copilotstuido) to your flow, however these variable types are not compatible.

It would appear the in CPS the variable type "file" is base64 encoded, which you would think is helpful, but PA won't accept this - as a File, String or anything else it would seem.

Converting the CPS "file" to another type does not seem to be an option as there are no ways to convert this to another type. That I could find anyway.

Was this reply helpful? Yes No
Suggested answer

Vinoth Selvam 1,590 Super User 2025 Season 2 on at

Like (0)

Report

Hi CU04020731-1,

Unfortunately i believe this is not possible at this point of time. We will not be able to save the document to base64 format using copilot studio.

We will be able to only pass other datatypes such as Text, Boolean, num from Copilot Studio to Power automate.

Thanks.

Visit my Blog

Was this reply helpful? Yes No
Suggested answer

-jake- 20 on at

Like (0)

Report

Haven't tried this myself, but wondering if a connector action might help out here.

1. Create a topic to "catch" file attach events (mentioned by DougM earlier)

2. Add a connector action to store the attachment in a designated SharePoint library (Create File action)

3. Collect the newly created file ID, which is (presumably) returned in the action output

4. Then, invoke your flow, passing the file ID as a parameter, instead of the binary content

5. Update the flow so that when triggered, it retrieves the file content from the SharePoint library

6. ???

7. Profit

There are a few assumptions in the mix there and it will require a little retooling of your existing work... But I'm curious if that might offer a path.

Was this reply helpful? Yes No