Unanswered

PowerFlow Custom Connector to IIS API resolves base url

(0) Share

Report

Posted on by pasindudt

I have a python Flask API hosted on IIS. API url path working when tried from web browser. But when calls the API from Power Flow custom connector, it resolves to base url, not for request url. Any idea?

Categories:

Connector development

I have the same question (0)

All responses (3)

Answers (0)

Sort by

murshed Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Sounds like you don't have parameters defined on the call. Please take a look at the documentation to explore more on this: https://docs.microsoft.com/en-us/connectors/custom-connectors/define-openapi-definition
If you can share the definition for the action I can provide more specific instruction.
If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION ☑️. If you find this reply helpful, please consider giving it a LIKE 👍.

Was this reply helpful? Yes No
MS-16081941-0 4 on at

Like (0)

Report
Copy link

Link copied!

Were you ever able to find a solution to this? I have the same exact scenario - python flask API hosted on IIS using FastCGI which always resolves to the base URL when trying to hit it from a custom connector using an on-premise gateway.

I can get it working successfully in the following two tests:
1) Testing using the swagger editor in the connector (after enabling CORs module in IIS)
2) Running the python flask app from command line instead of IIS

Was this reply helpful? Yes No
MS-16081941-0 4 on at

Like (0)

Report
Copy link

Link copied!

I'm having the same issue (see comment above) and don't think it is related to action parameters. I created a simple flask app just to troubleshoot where I have 3 routes without the need for any parameters and it still always goes to the base URL. It works from the swagger editor or if I stop the IIS service and run my flask app from command line. Any insight would be appreciated!

Was this reply helpful? Yes No