Anyone able to run data pipeline with Power Automate successfully?

[arpost]

Greetings, all. I am wanting to use Power Automate to run Fabric pipelines and get info about a pipeline run. I have successfully used other Fabric REST APIs, but when I try to use the Run on-demand item job API, I can never access the header response and instead get an error.

However, the pipeline runs behind the scenes as expected and includes the input parameter I send.

Does anyone have suggestions or know how to get this working? I found an article indicating this may have to do with the fact that this call doesn't return a response (article here), but it seems to me like there HAS to be a way to get this working. I can do this easily with the Try it! feature in the MS docs related to this API (doc link)

Anyone have ideas/suggestions?

[v-achippa]

Hi @arpost,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @lbendlin for the prompt response.

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the super user resolved your issue? or let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @arpost,

We wanted to kindly follow up to check if the solution provided by the super user resolved your issue.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Thanks and regards,

Anjan Kumar Chippa

[lbendlin]

Write your own custom connector until they fix the incomplete response.

[arpost]

Thanks for the response, @lbendlin. I did start down that path but am running into issues getting the custom connector working. Do you (or anyone else in the community) have resources specifically related to creating a custom Power Platform connector to use with Fabric?

[lbendlin]

should be straightforward.  What are your issues?  Make sure to turn asynchronous mode off.

[arpost]

Appreciate the help. It probably is, and I'm overlooking something obvious. 🙂 Here's my current connector and app reg configuration:

I wasn't certain that I'm including all of the required URLs for Fabric access. I had trouble authenticating previously until I used the graph.microsoft.com URL to authenticate my user. However, when I try to use a basic form of the List Pipelines API, I get this error (added a fake RequestID):

{
"requestId": "111111-1111-1111-1111-11111",
"errorCode": "RequestFailed",
"message": "Unable to process the request"
}

[lbendlin]

no real need for an app registration if you use HTTP with Entra pre-authorized.

[arpost]

@lbendlin, are you saying use HTTP with Entra in a Power Automate custom connector? Or natively in Power Automate?

If you're referencing the native connector in Power Automate, there is a need for custom connector when trying to work with APIs such as the Run On Demand API (see initial post with error examples when calling via Power Automate). The HTTP with Pre-Auth apparently can't read API responses that do not have a response body and throws errors.

That API returns the unique ID for an object run in the header (see this example) :

[v-achippa]

Hi @arpost,

Since the Run on-demand item job API returns only a 202 response with no body, power automate's standard HTTP action does not handle it well.

• Create a custom connector, use https://api.fabric.microsoft.com as the base URL and authenticate using OAuth 2.0 (Azure AD) with the proper scope.
• In the action settings, turn off asynchronous mode.
• Even though the body is empty, the location header contains the runId. So in your response section define the location header so you can extract the pipeline run ID from it in your flow.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thanks and regards,

Anjan Kumar Chippa