Add a Power Automate Activity to Fabric Data Factory Pipelines
In the world of Microsoft low-code/no-code, Power Automate has been referred to as the glue that holds Power Platform solutions together. With Fabric, there are occasions where activities need to be performed in areas not supported by Fabric, and Fabric solutions may even have dependencies on data fetched or produced by Power Automate. While there are HTTP-based approaches out there, this isn't low/no-code friendly and also introduces potential security risks if not properly handled.
Please add a built-in Power Automate activity that let's users trigger Power Automate flows and consume the response values from Power Automate flows.
5 Comments
- fbcideas_migusrNew Member
I think this Idea will open up a lot of exciting and valuable possibilities, and I think such a feature would be hugely popular among the users. Fabric and Power Platform joining forces would be amazing, and I think this activity would enable just that.
- adana1New Member
this would allow us to pull data from web extractions and be very powerful.
- nicky1New Member
Yes, we definitely need a PA activity! For example to build in an approval step for validating master data inside a pipeline.
- fbcideas_migusrNew MemberStatus added:Needs Votes
- Almon_DevRegular VisitorI agree, I was able to trigger a power automate BUT from a fabric notebook. It's hard-coded and much more time consuming to write. I set up an app registration active both in my fabric capacity in Azure as a contributor, and in my power platform envinroment as basic user. Fabric: You write pretty basic code to get token and call the post url from the power automate Trigger action "When a HTTP request is received" So the notebook is: import requests import json tenant_id = client_id = client_secret = flow_url = token_url = f"https://login.microsoftonline.com/{tenant_id}/oauth2/v2.0/token" token_payload = { "grant_type": "client_credentials", "client_id": client_id, "client_secret": client_secret, "scope": "https://api.powerplatform.com/.default" } token_response = requests.post(token_url, data=token_payload) token_response.raise_for_status() access_token = token_response.json()["access_token"] print("✅ Token acquired successfully") headers = { #"Authorization": f"Bearer {access_token}", "Content-Type": "application/json" } # Add any payload your flow expects, or leave as empty dict payload = {} response = requests.post(flow_url, headers=headers, json=payload) print(f"Status Code: {response.status_code}") if response.status_code in [200, 202]: print("✅ Flow triggered successfully") print(response.text) else: print("❌ Error calling flow:") print(response.text) POWER AUTOMATE: You don't need much, just the trigger action When a HTTP request is received and the rest goes according to your needs. Just the user you get the token for should be the same that runs and owns the flow. Connections used in the flow have to be shared. Hope it helps until Microsoft enable the low code/no code action to call!
Recent ideas
Restore "no-reply" option for Power BI Subscriptions
Please add a setting in the Power BI Subscription pane to choose the sender identity. With the recent update the platform forces emails to route through the subscription owner's personal Exchange On...LenaFid7 hours agoRegular VisitorNew298Views52likes11CommentsEnforcing OneLake Security on external semantic model API calls without adding security risks
Problem External applications cannot query Fabric semantic models on a user’s behalf - with OneLake RLS security rules enforced - unless the Fabric API is exposed to any and every client an authoriz...sean_cochran9 hours agoResolver INew21Views0likes0CommentsAllow ownership transfer (“Take over”) for Activator items
Activator rules run under the identity of the item’s creator. When that person leaves the organization and their account is disabled, all rules stop working silently. Unlike other Fabric items, there...ndelcastillo10 hours agoRegular VisitorNew29Views1like0Comments