PDF file content data type changes between flow, APIM and custom connector

(0) Share

Report

Posted on by schwibach Super User 2025 Season 1

Hello,

I'm trying to implement an App Service wrapped in a Logic App wrapped in APIM as a Custom Connector.

When I give the App Service the file content from the flow action, it works fine.

When I give the file content to the HTTP-trigger as payload directly, it works fine.

However, when I let power automate send the data through the custom connector, it turns into some weird other content type, that's not usable in the logic app.

If I wrap base64() around the file content when giving the file content to the custom connector, it works.

So, my question is: How do I get the connector to accept the direct output of the word-to-pdf action without having to wrap it in a base64() function, so users of the connector don't have to do that every time?