Skip to content
Microsoft Power BI
Microsoft Power BI
Business intelligenceAvailable via the partner API

Connect Microsoft Power BI with TAC Flow

Connect directly to the read endpoints and build live dashboards for assets, costs, and consumption.

01Overview

Requirements

Requirements

  • A Power BI license with Power Query
  • A TAC Flow API key with the required scopes
  • A developer or the system implementer at your company

Scopes used

assets:readmaintenance:readincidents:readmovements:readfuel:readmeters:readinspections:read

First: issue an API key from Settings → Integrations — it will be used to read from TAC Flow.

02What syncs

Where your data lands

  • Asset register (equipment & vehicles)From TAC FlowAsset dashboards
  • Approved maintenance costsFrom TAC FlowCost reports
  • Fuel and diesel costsFrom TAC FlowConsumption analytics
  • Meter readingsFrom TAC FlowOperations KPIs
03Setup steps

The setup, start to finish

Executed by your technical team or your system implementer — typical effort is one working day.

  1. 1Issue the API keyFrom TAC Flow Settings → Integrations, issue a key with the required read scopes and save it — it is shown only once.
  2. 2Add the data sourceIn Microsoft Power BI, add a web data source reading the partner API endpoints with the Authorization header, per the reference examples.
  3. 3Build the dashboardsBuild asset, cost, and consumption dashboards from the standard fields the endpoints return.
  4. 4Enable scheduled refreshConfigure periodic refresh with incremental sync — pulling only what changed since the last run.
  5. 5Verify and monitorCompare the first batch against TAC Flow reports and watch the usage log in the Integrations screen.
04FAQ

Asked before implementation

Who implements the integration?

Your technical team or your system implementer — this guide plus the technical reference cover everything needed; typical effort is one working day.

Does the external system write into TAC Flow?

No — the partner API is read-only in its current version, which makes the integration inherently safe: no external mistake can corrupt your data.

Ready to integrate?

The full technical reference with runnable examples — your developer starts in minutes.