Someone suggested using a custom connector with API Key security + Secure Outputs so the connector "parses the Authorization header internally and passes it to later steps." Does this actually capture a token returned by a login response, or does API Key auth only replay a token I already hold? My reading of the docs is the latter, but I'd like confirmation.
If it genuinely can't be done natively, what's the lightest reliable pattern people use, Power Automate Desktop's "Invoke web service" (which returns raw header), an Azure Function proxy that returns the token in a JSON body, or something else?

Report
All responses (
Answers (