List Cloud Storage Files / Folders in Microsoft Power Automate throws Error

[Dgain]

I am attempting to call the Get Folder using PowerAutomate through the URI:

https://api.aspose.cloud/v3.0/pdf/storage/folder/%2F?storageName=Trial%20Storage

I have been able to successfully generate a Bearer Token using the https://api.aspose.cloud/connect/token, but using the header

“Authorization”: “Bearer {Access_Token}” with {Access_Token} being replaced with the access token.

I get a response:

“RequestId”: “968f96c1-263e-447b-9d8d-2a1315a88673”,
“Error”: {
“Code”: “error”,
“Message”: “ClientId is undefined. Please check authorization.”,
“Description”: “Operation Failed. General Error.”,
“DateTime”: “2022-04-25T11:14:42.5834279Z”,
“InnerError”: null
}

[tilal.ahmad]

@Dgain

I have tried to list cloud storage files in Microsoft Power Automate using Aspose.PDF Cloud API GetFilesList request and unable to notice the issue. Please check the screenshot of my sample workflow. You can parse the JSON output of Access Token workflow step and use it in the subsequent steps as follows.

Steps to List Cloud Storage Files with Microsoft Power Automate

- Add A Step to Trigger Flow Manually

- Use Http Connector to aspose.cloud Access Token

- Parse Access Token JSON Output for Authorization Header

- List Cloud Storage Files using Aspose.PDF REST API

[Dgain]

I have parsed the Access Token, the problem is the response I get:

{
“statusCode”: 400,
“headers”: {
“Transfer-Encoding”: “chunked”,
“Connection”: “keep-alive”,
“Strict-Transport-Security”: “max-age=2592000”,
“Date”: “Mon, 25 Apr 2022 13:25:21 GMT”,
“Server”: “Kestrel”,
“Content-Type”: “application/json; charset=utf-8”,
“Content-Length”: “249”
},
“body”: {
“RequestId”: “38783aff-59f2-400e-b508-764dff972c38”,
“Error”: {
“Code”: “error”,
“Message”: “ClientId is undefined. Please check authorization.”,
“Description”: “Operation Failed. General Error.”,
“DateTime”: “2022-04-25T13:25:21.4113266Z”,
“InnerError”: null
}
}
}

Screen Shot 2022-04-25 at 09.25.06.png (46.8 KB)

[Dgain]

I was able to Resolve this. I had parsed the output incorrectly. No additional support needed on this issue, thank you!

[tilal.ahmad]

@Dgain

It is good to know that you have managed to resolve the issue. Please feel free to contact us for any further assistance.