Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Microsoft Power BI

Create and manage Power BI datasets and reports, and push data to them

CategoryBusiness Intelligence
Authenticationcustom
Version0.4.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Microsoft Power BI with Flows360

Create and manage Power BI datasets and reports, and push data to them

Use the Microsoft Power BI connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 9 actions and no declared triggers.

Available actions

  • Create Dataset
  • Push Rows to Dataset Table
  • Refresh Dataset
  • Run DAX Query
  • Export Report to File
  • List Reports
  • Clone Report
  • Import File (.pbix)
  • Plus 1 additional declared action.

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Microsoft Power BI
  • Package: @activepieces/piece-microsoft-power-bi@0.4.0
  • Exact artifact digest: sha256:4f495dfdee28ad838636e1e85bc6b5df852f004fb16031d842527ead449a36ac
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Dataset (create_dataset), Create a new dataset in Power BI with custom schema (Push, Streaming, or PushStreaming mode). Classification: read.
  • Push Rows to Dataset Table (push_rows_to_dataset_table), Add rows to a table in a Power BI dataset (supports Push, Streaming, and PushStreaming modes) Classification: read.
  • Refresh Dataset (refresh_dataset), Triggers a refresh of a Power BI dataset so its data reflects the latest changes from the underlying source. Classification: read.
  • Run DAX Query (run_dax_query), Executes a DAX (Data Analysis Expressions) query against a Power BI dataset and returns the resulting rows. Classification: read.
  • Export Report to File (export_report_to_file), Exports a Power BI report to a PDF, PPTX, or PNG file. Classification: read.
  • List Reports (list_reports), Lists all reports in a Power BI workspace. Classification: read.
  • Clone Report (clone_report), Creates a copy of a Power BI report, optionally into a different workspace or bound to a different dataset. Classification: read.
  • Import File (.pbix) (import_pbix), Uploads a Power BI Desktop (.pbix), Excel (.xlsx), or RDL file into a workspace, creating a new dataset and report. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects9
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Access token Required · protected credential
  • Cloud Environment Required

Supported objects

ObjectReadWriteNotes
Create Dataset Yes No Create a new dataset in Power BI with custom schema (Push, Streaming, or PushStreaming mode).
Push Rows to Dataset Table Yes No Add rows to a table in a Power BI dataset (supports Push, Streaming, and PushStreaming modes)
Refresh Dataset Yes No Triggers a refresh of a Power BI dataset so its data reflects the latest changes from the underlying source.
Run DAX Query Yes No Executes a DAX (Data Analysis Expressions) query against a Power BI dataset and returns the resulting rows.
Export Report to File Yes No Exports a Power BI report to a PDF, PPTX, or PNG file.
List Reports Yes No Lists all reports in a Power BI workspace.
Clone Report Yes No Creates a copy of a Power BI report, optionally into a different workspace or bound to a different dataset.
Import File (.pbix) Yes No Uploads a Power BI Desktop (.pbix), Excel (.xlsx), or RDL file into a workspace, creating a new dataset and report.
Custom API Call Yes No Make a custom API call to a specific endpoint

Setup

Setup

  1. Add the Microsoft Power BI connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Cloud Environment (cloud), required.

OAuth scopes

  • https://analysis.windows.net/powerbi/api/Dataset.ReadWrite.All
  • https://analysis.windows.net/powerbi/api/Report.ReadWrite.All
  • https://analysis.windows.net/powerbi/api/Content.Create
  • https://analysis.windows.net/powerbi/api/Workspace.Read.All
  • offline_access
  • openid
  • email
  • profile
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-microsoft-power-bi@0.4.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 9 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Microsoft Power BI connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-microsoft-power-bi@0.4.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com