Forum Discussion
PowerBi and Power Automate
- You’re very close — and no, you don’t need a custom connector for this.The key point is that Power BI cannot consume a file directly from an HTTP POST request. The file needs to be stored first in a location that Power BI/Fabric can access.The usual pattern is:
- Power Automate receives the HTTP POST
- Save the file to SharePoint / OneDrive / ADLS / Lakehouse
- Power BI reads the file from that location
Regarding your questions:- You do not need a custom connector for this.- A gateway is only required if the file is stored in an on-premises location.- If you store the file in SharePoint or OneDrive Online, Power BI can access it as a cloud source.Official Microsoft references for the building blocks:- Power Automate HTTP request trigger / authentication:
https://learn.microsoft.com/en-us/power-automate/oauth-authentication - SharePoint connector actions in Power Automate:
https://learn.microsoft.com/en-us/sharepoint/dev/business-apps/power-automate/sharepoint-connector-actions-triggers - Power Query SharePoint Folder connector for Power BI/Fabric:
https://learn.microsoft.com/en-us/power-query/connectors/sharepoint-folder
A closer step-by-step example of the exact pattern, HTTP POST file upload to Power Automate and then SharePoint, is here:
https://blog.ninethsense.com/technology/automation/power-automate-post-a-file-to-trigger-a-http-flow-and-upload-to-sharepoint/So the important part is the staging step: receive file → store file → let Power BI read it. Power BI is pull-based, while your HTTP POST scenario is push-based.
Hi thankegyssling,
Power BI can't directly access a file from a POST request.
Power Automate would need to put the file somewhere that Fabric/Power BI can access it. The easiest place is prbably sharepoint, but you could also put the file in a Azure Storage Account in Azure data lake gen 2 storage, or you could use the storage APIs to shove the file directly into a lakehouse for Fabric to pick up.
Regardless of which option you choose, you need to stage the file somewhere that Fabric/PowerBI can access it
tayloramy Thanks for that so if i understand correct i need an place like sharepoint where Power Automate stores the file and then our On-Prem PowerBI Gateways can take the file and forward this?
i did also some search with copilot and the answer was that i need an custom connector in Power Automate!
Regards
Thorsten
- You’re very close — and no, you don’t need a custom connector for this.The key point is that Power BI cannot consume a file directly from an HTTP POST request. The file needs to be stored first in a location that Power BI/Fabric can access.The usual pattern is:
- Power Automate receives the HTTP POST
- Save the file to SharePoint / OneDrive / ADLS / Lakehouse
- Power BI reads the file from that location
Regarding your questions:- You do not need a custom connector for this.- A gateway is only required if the file is stored in an on-premises location.- If you store the file in SharePoint or OneDrive Online, Power BI can access it as a cloud source.Official Microsoft references for the building blocks:- Power Automate HTTP request trigger / authentication:
https://learn.microsoft.com/en-us/power-automate/oauth-authentication - SharePoint connector actions in Power Automate:
https://learn.microsoft.com/en-us/sharepoint/dev/business-apps/power-automate/sharepoint-connector-actions-triggers - Power Query SharePoint Folder connector for Power BI/Fabric:
https://learn.microsoft.com/en-us/power-query/connectors/sharepoint-folder
A closer step-by-step example of the exact pattern, HTTP POST file upload to Power Automate and then SharePoint, is here:
https://blog.ninethsense.com/technology/automation/power-automate-post-a-file-to-trigger-a-http-flow-and-upload-to-sharepoint/So the important part is the staging step: receive file → store file → let Power BI read it. Power BI is pull-based, while your HTTP POST scenario is push-based.Parchitect
Thanks for that i will check
Regards
ThorstenHi thankegyssling ,
Did you get a chance to check the solution?I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you.
Best Regards,
Community Support Team
