Power BI icon

Power BI

Work with the Power BI API

Actions32

Overview

This node interacts with the Power BI API to retrieve the refresh history of a specified dataset within a workspace (group). It is useful for monitoring and auditing dataset refreshes, helping users track when data was last updated and diagnose refresh issues.

Typical use cases include:

  • Automating reports on dataset refresh status.
  • Triggering workflows based on refresh success or failure.
  • Auditing refresh frequency and history for compliance or operational insights.

For example, you can configure this node to fetch the last 10 refresh events of a dataset in a specific Power BI workspace to monitor its update schedule.

Properties

Name Meaning
Authentication Method used to authenticate with Power BI API. Options: OAuth2, Bearer Token.
Group (Workspace) Name or ID The Power BI workspace identifier where the dataset resides. Leave blank to use "My Workspace". Can be selected from a list or set via expression.
Dataset Name or ID Identifier of the dataset whose refresh history is to be retrieved. Must be selected from a list or specified via expression.
Limit Maximum number of refresh history entries to return. Corresponds to the $top parameter in the API request.

Output

The node outputs an array of JSON objects representing refresh history entries for the specified dataset. Each entry typically includes details such as:

  • Refresh start and end times.
  • Refresh status (e.g., completed, failed).
  • Refresh type (manual, scheduled, etc.).
  • Any error messages if the refresh failed.

This output allows downstream nodes to analyze or act upon dataset refresh information.

The node does not output binary data.

Dependencies

  • Requires access to the Power BI REST API.
  • Needs either OAuth2 authentication or a Bearer Token credential configured in n8n.
  • The node dynamically loads available groups (workspaces) and datasets via helper methods, so proper API permissions are necessary to list these resources.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication credentials will cause API calls to fail.
    • Specifying a non-existent group or dataset ID will result in errors.
    • Insufficient API permissions may prevent listing groups or datasets.

  • Error Messages:

    • "The resource \"dataset\" is not supported!" — indicates an unsupported resource; ensure the correct resource and operation are selected.
    • API errors related to authentication or authorization should be resolved by verifying credentials and permissions.
    • If no refresh history is returned, verify that the dataset has refreshes recorded and that the correct workspace/dataset IDs are used.

Links and References

Discussion