Unanswered

Multiple actions in custom connector for Azure Blob storage

(0) Share

Report

Posted on by Imke

281

Has anyone managed to create multiple actions in a custom connector for Azure blob storage?
The problem with that API is that the base url is always the same and the different endpoints are solely defined by query parameters.
So when defining an action, those query parameters are being shifted to the parameter-section and the (base) url will remain and causing duplicates.
https://<BlobName>.blob.core.windows.net/?comp=list
will become
https://<BlobName>.blob.core.windows.net
after the parameter have been moved.
Is there a trick on how to overcome this?

Categories:

Connector development

I have the same question (0)

All responses (7)

Answers (0)

EmadBeshai 806 Moderator on at

Like (0)

Report

Hi @Imke ,

Is that causing any issue with your flow?
Could you please share screenshot to help us identify what exactly happens with you?

Was this reply helpful? Yes No
Imke 281 on at

Like (0)

Report

Thanks @EmadBeshai ,
when defining the action in the custom connector, I get the following error message:

Was this reply helpful? Yes No
EmadBeshai 806 Moderator on at

Like (0)

Report

Hi @Imke ,
Could you please add the URL with the query string parameters inside variable step the passing this variable to the URL instead of adding it directly to the custom connector?

Was this reply helpful? Yes No
Imke 281 on at

Like (0)

Report

Thanks @EmadBeshai ,
but not sure I understand your last message.
Just to confirm: In my screenshot above: What you see in the URL is not what I have entered there when I filled in the fields for the action. I entered the full path including the query parameter. But Power Automate cuts out the query parameters automaticall in the background and moves them to the dedicated section.

Also, manually editing in the Swagger editor and putting them back doesn't work. Then I get the error message "Query strings in paths are not allowed".

Was this reply helpful? Yes No
Imke 281 on at

Like (0)

Report

Actually, this seems to be a general limitation with Swagger/OpenAPI definitions:
Swagger API which is having query string - Stack Overflow
Maybe there is actually no hope here 😞

Was this reply helpful? Yes No
EmadBeshai 806 Moderator on at

Like (0)

Report

Hi @Imke ,

Yes, it is a limitation but I was thinking if you composite the URL into variable and passing it to the custom connector that would help

If this post helps you with your problem, please mark this answer as Accepted Solution.
If you like my response, please give it a Thumbs Up.

Was this reply helpful? Yes No
Imke 281 on at

Like (0)

Report

Hi @EmadBeshai ,
thanks, that sounds interesting.
But when calling the custom connector, there is no field in the UI where I can fill in the URL.
The only fields displayed are for the query parameters and the header fields.
Is there a configuration option in the custom connector definition that would enable that?

Was this reply helpful? Yes No