thanks
@chiaraalina atm like the MSFTEE said in the related post, the send file to the copilot connector is not implemented yet.
you have multiple solution : Get the document ID, Get the document URL etc and then get it inside the agent
For the scenario you have, what i do at the moment as a temporary workaround.
First : I connect the agent to the knowledge base where the document are drop (will explain later why) and i change the KB behavior to be only able inside topic from the advanced option of the KB
Second : I send the document absolute URL to the agent from the power automate trigger and then within a Topic (with advanced input configure to take the url) a use a generative answer node with a custom prompt like " your job is [blablablalblable] and compare this document [insert here with a variable the document absolute url] within this content to analyze [set of rules]"
Important tips : before sending the document URL to the agent, you need to be sure that the document have been indexed by sharepoint, other way the agent will not see it.
An easy way is to have a little loop in the power automate, just before answer to the agent, to check if the document is inside the sharepoint search index
The trick is here : this variable from the search api call is equal to 0 until document is not indexed (took 20 second in mot time)
a little zoom in the loop
here is how i send the info to the agent (tips : the message is a real prompt, so you can customize it as you want)
It work very well :)
then the topic
and then you have the foundation to do whatever you want : add a doc id inside the send to copilot to prepare for an approval workflow later if you need :)
I hope this quick tuto help you to solve the problem or helped you to go to the answer :)
if yes, it's important to check the answer as green good answer with the checkbox, it's important for the community and more for the search engine :) truly :)