Thank you. Followed your video instructions and publish the Copilot to Teams (since there is no authentication, Teams is the only channel available) and it worked the next day. Before that it was going to the default topics :). Question: If i want to do what you did and this time use the Zendesk connector in Power Platform (instead of creating a new connector), can it be done?
I have tried to recreate this using my own api and i am facing a problem. The custom connector in power apps has 7 output fields from the api and the test is also working fine however when we create an action to connect to this custom connector only 2 outputs are recognised in copilot studio i am not sure why this is. Can someone please help. The outputs recognised have one thing in common which is they are a single word and the rest of the unrecognised outputs are two words Eg. Item Id Any help would be appreciated.
This is awesome, and very helpful. Would love to see a connector for OpenAI combined with AI Search. What is the difference between "Sample API Connector" vs making a call through a trigger phrases to a HTTP request node?
@@Dewain27 Sorry for the confusion. I meant, what is the difference between the action you built here vs. the http call to the API through a node? I thought it would be a seamless conversation in case of the action, but not sure if that's true.
First of wonderfull example. It will help to show how the Authentication flow, for example flow in logged in users email and ID. How can this further be made available so that it can be used from Copilot in Team, Office and web version ?
I also created a custom connection with a free to use api I found on the internet, but for some reason I can not see output variables in copilot studio. Do you have any suggestions why is it the case? Edit: It is probably not working because the api response is wrapped in [ ]. Do you have any idea how to solve that?
Really useful video, thanks! Looking forward to more practical and well structured use cases like this.
Thank you. Followed your video instructions and publish the Copilot to Teams (since there is no authentication, Teams is the only channel available) and it worked the next day. Before that it was going to the default topics :). Question: If i want to do what you did and this time use the Zendesk connector in Power Platform (instead of creating a new connector), can it be done?
I have tried to recreate this using my own api and i am facing a problem. The custom connector in power apps has 7 output fields from the api and the test is also working fine however when we create an action to connect to this custom connector only 2 outputs are recognised in copilot studio i am not sure why this is. Can someone please help.
The outputs recognised have one thing in common which is they are a single word and the rest of the unrecognised outputs are two words Eg. Item Id
Any help would be appreciated.
This is awesome, and very helpful. Would love to see a connector for OpenAI combined with AI Search. What is the difference between "Sample API Connector" vs making a call through a trigger phrases to a HTTP request node?
You can't do an action with the HTTP node
@@Dewain27 Sorry for the confusion. I meant, what is the difference between the action you built here vs. the http call to the API through a node? I thought it would be a seamless conversation in case of the action, but not sure if that's true.
First of wonderfull example. It will help to show how the Authentication flow, for example flow in logged in users email and ID. How can this further be made available so that it can be used from Copilot in Team, Office and web version ?
do you know how to do this?
I also created a custom connection with a free to use api I found on the internet, but for some reason I can not see output variables in copilot studio. Do you have any suggestions why is it the case?
Edit: It is probably not working because the api response is wrapped in [ ]. Do you have any idea how to solve that?
Did u find an answer to that yet