Create TopDesk Change Request from Flow

(0) Share

Report

Posted on by Community Power Pla...

Hi all,

I'm trying to build a Flow to create a change request in TopDesk.

I started with a custom connector and tried using this documentation - specifically the operatorChanges API.

I edited the swagger file so and I have the authentication working, I think. but when I run the Flow (manually trigger, then run the connector, no other steps) it fails at the connector and says:
"This page is not available for you. You might have followed an old or incorrect link, or you might not have permissions to view the content."

Has anyone successfully used a TopDesk API in Flow? If so am I missing something, can anyone give me any advice?

Thanks!

Categories:

Using connectors

I have the same question (0)

All responses (10)

Answers (0)

v-litu-msft on at

Like (0)

Report

Hi @Anonymous,

I have no subscription to TopDesk, so there is no way to test it. Here is a post talked about TopDesk API, hope it could help you something:

Solved: Custom Connector API issue - Power Platform Community (microsoft.com)

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Thank you so much @v-litu-msft , I checked out the post but it's not the same issue. I'm getting like authentication / page not available errors and I can't get past it.

Thanks though!

Was this reply helpful? Yes No
Taylope1 60 on at

Like (0)

Report

What operator command are you trying? Assume you have given the api account in TD sys admin rights?

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

I tried a few different ones including:
operatorChanges (Get AND Post)
requesterChanges (Get)
operators (Get)
The last one seemed to sort of work - it pumped out a bunch of IDs, but no additional data and I couldn't verify if it was correct beacuse I can't see the IDs in TopDesk
I am not positive that the API account has Sys Admin rights - I don't think so. I'm not tenant admin for the TopDesk enviro though so I will check. Is that the level that's definitely needed?
I am just using an API login for the authentication.

Was this reply helpful? Yes No
Taylope1 60 on at

Like (0)

Report

API will need elevated rights to patch/post data for sure. Are you trying to create tickets and add updates etc?

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

That's the end goal yes, but I am running into 404 errors even with the GET requests.

Was this reply helpful? Yes No
Taylope1 60 on at

Like (0)

Report

So is TD on-prem? If yes I assume you have created a gateway? I guess yes as you said you did get back some ID's. I will try and send you my Create TD swagger file that maybe can assist you.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

I believe it is not on-prem, will confirm. So today I tried with changeStatuses command and I tested it in:
Flow - same error
Postman - no error, I got the results. I authenticated the exact same way in both tools...so this seems like a Flow-specific issue? My swagger file is the simplest thing on earth, only contains the login credentials...

Was this reply helpful? Yes No
Taylope1 60 on at

Like (0)

Report

Can you post the file up here?

Was this reply helpful? Yes No
NielsHakkers 25 on at

Like (0)

Report

Hi @Anonymous , I am also working on connecting several of the TOPdesk API's to my environment.

One thing that I struggled with is that custom connectors are actually considered a premium function. You are allowed to create custom connectors, but they will fail to run if you don't have the proper licensing. Therefore you either need a additional Power Automate license on top of your Office 365 license. Or work from a Power Apps Community Plan. My advice is to check if you are working in the default environment or not, and perhaps use your personal environment instead.

As mentioned by @ Taylope1, posting your swagger input would help. Or posting the apiDefinitions.json and apiProperties.json (using the Microsoft Power Platform Connectors CLI | Microsoft Docs).

Was this reply helpful? Yes No