Autopilot Teams does not work

Help Integration Service
1

Hello,

when I try to connect my Teams with my orchestrator via the Teams Plugin “UI Path Autopilot” I always get an error:

“Error
Client is not registered under given UiPath organization. Please contact UiPath administator to register this application. (#242)”

The image shows an error message from UiPath indicating that the client is not registered under the given UiPath organization and advises contacting the administrator to register the application (error #242). (Captioned by AI)
The image shows an error message from UiPath indicating that the client is not registered under the given UiPath organization and advises contacting the administrator to register the application (error #242). (Captioned by AI)789×609 14.8 KB

I can setup a connection directly in orchestrator with teams and then trigger automations via chat events. However, this way I cannot pass any arguments (I can simply start the automation but it seems impossible in the trigger settings to map a part of the message to the input argument…) So I thought using the autopilot would be much smarter and user friendly. But I cannot set it up…

2

@f.booch-arkossy

As per error I believe the second prereq is not met

The image lists prerequisites for using a UiPath Automation Cloud organization, including user access and administrator approval of the Teams Copilot Plugin registration. (Captioned by AI)
The image lists prerequisites for using a UiPath Automation Cloud organization, including user access and administrator approval of the Teams Copilot Plugin registration. (Captioned by AI)828×594 93.5 KB

Cheers

3

Thanks for your answer! When I register an external application with the needed scope I’ll get App Secret and ID but I am clueless on how to make orchestrator “understand” that this external application is the Autopilot plugin…

In the registration process of the App I am solely asked for entering login credentials from my orchestrator…

1 Like
4

@f.booch-arkossy

thats a fair ask…

@loredana_ifrim - Any help here?

cheers

5

Hi folks,

The fix for this needs you to require a org admin to permit a global app & configure specific labels on Orchestrator. This is quite limited in capabilities and the team is pushing a new version in the next 2 weeks, which will no longer need this.

Please stay tuned for the updates.

3 Likes
6

Great, thanks for your answer! Exciting news!

I will wait for the update and then try again!