FlowRunner
PricingContact
Theme
Start Free

Microsoft Power BI

Analytics & Data

Operate Power BI from AI agents: refresh datasets and verify outcomes, run DAX queries for KPIs, stream rows into push datasets, and export reports to PDF, PowerPoint, or PNG into FlowRunner file storage across 36 actions.

36 actions OAuth available
The overnight warehouse load completes upstream
Refresh Dataset starts the semantic model refresh
Get Refresh History confirms the refresh completed, not failed
Execute DAX Query pulls the day's KPI figures from the model
KPI values compared against yesterday for out-of-range swings
Teams channel receives the KPI summary before the morning standup
Ops lead confirms an anomaly is real before it escalates to leadership

What This Integration Enables

Dashboards do not run the business. The meeting where someone looks at them does, and the quiet failure mode of every BI stack is a meeting run on a dataset that silently failed to refresh. This integration puts agents on that seam. They trigger Refresh Dataset when upstream data lands rather than on a hopeful timer, verify the outcome through Get Refresh History, and raise the alarm when a refresh fails, before anyone quotes a stale number. Execute DAX Query then gets the figures out of the semantic model and into the flow of work, so a KPI can be posted, compared, and acted on without anyone opening a report. Beyond the daily loop, agents stream rows into push datasets for live dashboard tiles, export reports to PDF, PowerPoint, or PNG into FlowRunner file storage for scheduled distribution, and manage the estate: cloning and rebinding reports across workspaces, taking over datasets, and updating Power Query parameters. Destructive operations like dataset deletion sit behind [human-in-the-loop](/concepts/human-in-the-loop/) approval, because in Power BI one delete can silently break every report built on top. Connector capabilities are built and verified against Microsoft's official Power BI REST API.

Without FlowRunner

Dashboards trusted blindly Nobody knows the 7am refresh failed until a decision is made on stale numbers
KPIs locked in the model Getting a figure out of Power BI means opening Power BI
Report distribution by hand Someone exports the PDF and emails it every Monday, when they remember

With FlowRunner

Refresh verified, then trusted Every refresh is triggered, checked against history, and flagged on failure
KPIs travel to the decision DAX queries carry the numbers into the channels where people act
Exports on a cadence Reports render to PDF or PowerPoint and distribute themselves on schedule

Use Case Scenarios

Refresh, verify, then report

The warehouse load finishes overnight. The agent calls Refresh Dataset on the operations model, waits, and checks Get Refresh History for a Completed status. On failure it posts the error to the BI channel immediately; on success it runs Execute DAX Query for the standing KPI set, compares against the prior day, and posts the summary to [Microsoft Teams](/integrations/microsoft-teams) before standup. When a figure swings out of range, the ops lead confirms whether it is a data problem or a business problem before it travels any further up the org.

Live tiles fed by workflows

An agent creates a push dataset with Create Push Dataset and streams operational events into it with Add Rows to Table as they happen: orders processed, exceptions opened, queue depths. Dashboard tiles built on the push dataset update in near real time without a refresh cycle. A nightly job calls Delete Rows from Table to reset rolling windows. The wallboard in the operations room stops being a screenshot of yesterday.

The Monday report that sends itself

On Monday at 6am, an agent calls Export Report to File for the weekly performance report, which renders the PDF and stores it in FlowRunner file storage. It posts the file link to the leadership channel and logs the export in a distribution sheet with [Google Sheets](/integrations/google-sheets). For long-running exports it switches to the asynchronous path: Start Report Export, Get Report Export Status, then Save Exported Report File once the job succeeds. The report arrives before the meeting every week, including the weeks the report owner is on holiday.

Human-in-Loop Highlight

Delete Dataset cannot be undone, and its blast radius is bigger than it looks: every report built on that semantic model stops working the moment it runs. So the workspace cleanup agent treats deletion as a proposal, not an action. It inventories candidates with List Datasets, cross-references List Reports to find which reports bind to each dataset, and checks Get Refresh History for signs of life. Then it asks the BI owner in Teams: "Dataset 'Sales_Model_v2_OLD' last refreshed in February, but 3 reports still bind to it, including one in the Finance workspace. Delete anyway, rebind those reports first, or leave it?" The agent surfaces the dependency graph nobody checks by hand. The person decides what breaks.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

36 actions

Workspaces

1
  • List Workspaces Retrieves the workspaces the user can access, with IDs and capacity information. Used to resolve targets before any scoped operation.

Datasets

8
  • List Datasets Retrieves the datasets in a workspace or My workspace, with capability flags. Used in estate audits and refresh scheduling.
  • Get Dataset Retrieves a single dataset with its owner and refreshability flags.
  • Delete Dataset Permanently deletes a dataset; reports built on it stop working. The gated action in this connector: deletion requires human approval with the dependency evidence attached.
  • Refresh Dataset Triggers an asynchronous refresh of a semantic model. Used to refresh when upstream data actually lands instead of on a blind schedule.
  • Get Refresh History Retrieves refresh outcomes with start, end, and completion status. The verification step that makes a refresh trustworthy.
  • Get Dataset Parameters Retrieves a dataset's Power Query parameters. Used before environment or source changes.
  • Update Dataset Parameters Updates Power Query parameter values; requires dataset ownership. Used to repoint models across environments.
  • Take Over Dataset Transfers dataset ownership to the connected user. Required before owner-only operations like parameter updates.

DAX Queries

1
  • Execute DAX Query Runs a DAX query against a semantic model and returns the rows. The action that moves KPIs out of the model and into workflows.

Push Datasets

5
  • Create Push Dataset Creates a push dataset with a defined table schema. Used to build real-time tiles fed by workflows.
  • Get Dataset Tables Retrieves the tables of a push dataset.
  • Add Rows to Table Streams rows into a push dataset table. Used to update live dashboard tiles as operational events happen.
  • Delete Rows from Table Removes all rows from a push dataset table while keeping the schema. Used to reset rolling windows.
  • Update Table Schema Updates a push dataset table's column definitions. Used when the streamed payload evolves.

Reports

5
  • List Reports Retrieves the reports in a workspace with type, dataset binding, and URLs. Used for distribution runs and dependency checks.
  • Get Report Retrieves a single report with its dataset ID and URLs.
  • Get Report Pages Retrieves a report's pages with internal names and order. Used to target specific pages in exports.
  • Clone Report Copies a report, optionally into another workspace or rebound to a different dataset. Used to promote reports across environments.
  • Delete Report Permanently deletes a report. Cannot be undone; runs only inside reviewed cleanup.

Report Export

4
  • Export Report to File Exports a report to PDF, PowerPoint, or PNG, waits for the job, and saves the file to FlowRunner file storage. The one-call path for scheduled distribution.
  • Start Report Export Starts an asynchronous export job and returns its ID. Used for exports that outlast the synchronous window.
  • Get Report Export Status Polls an export job's state and progress.
  • Save Exported Report File Downloads a completed export and stores it in FlowRunner file storage. The final step of the asynchronous export path.

Dashboards

3
  • List Dashboards Retrieves the dashboards in a workspace with URLs.
  • Get Dashboard Retrieves a single dashboard's details.
  • List Dashboard Tiles Retrieves a dashboard's tiles with the report and dataset each is built on. Used in dependency mapping before changes.

Dataflows

2
  • List Dataflows Retrieves the dataflows in a shared workspace. Used to audit upstream preparation layers.
  • Refresh Dataflow Triggers an asynchronous dataflow refresh, with optional failure notification. Used to refresh the preparation layer before dependent datasets.

Apps

4
  • List Apps Retrieves the Power BI apps installed for the user.
  • Get App Retrieves a single installed app's details.
  • List App Reports Retrieves the reports published in an installed app. Used to enumerate what consumers actually see.
  • List App Dashboards Retrieves the dashboards published in an installed app.

Platform

3
  • List Imports Retrieves uploaded PBIX files and content publications in a workspace. Used to trace where content came from.
  • List Gateways Retrieves the on-premises data gateways the user administers. Used to check connectivity paths before refresh troubleshooting.
  • List Capacities Retrieves the Premium, Embedded, and Fabric capacities the user can access. Used to confirm export-capable capacity before scheduling report exports.

Frequently Asked Questions

What can FlowRunner do with Microsoft Power BI?

FlowRunner agents can run List Workspaces, List Datasets, and Get Dataset in Microsoft Power BI, plus 33 more actions.

Does connecting Microsoft Power BI to FlowRunner require OAuth?

Yes. Microsoft Power BI connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Microsoft Power BI trigger a FlowRunner workflow automatically?

Microsoft Power BI doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Microsoft Power BI

$100 in credits. No card required. Connect in minutes.