Power BI Header Auth

Overview

This node enables interaction with the Power BI API using header-based authentication. It allows users to perform various operations on Power BI resources such as dashboards, datasets, groups, reports, and administrative functions by providing a bearer token for authorization.

Common scenarios where this node is beneficial include:

• Automating retrieval of Power BI dashboards or reports metadata.
• Managing datasets and groups within an organization’s Power BI workspace.
• Accessing administrative information about workspaces.
• Integrating Power BI data into workflows without using OAuth2 but instead supplying a direct bearer token.

For example, a user can fetch all dashboards in a specific workspace by providing a valid authentication token and selecting the "Dashboard" resource with the appropriate operation.

Properties

Output

The node outputs JSON data representing the results of the selected Power BI API operation. The structure depends on the chosen resource and operation but generally includes arrays of objects corresponding to entities like dashboards, datasets, groups, or reports.

If an error occurs during execution, the output JSON will contain an error field with a descriptive message.

The node does not output binary data.

Dependencies

• Requires a valid bearer token for Power BI API authentication. This token must be provided either as input data or via the node parameter.
• Connects to the Power BI REST API at https://api.powerbi.com/v1.0/myorg.
• No internal credential types are used; the token must be supplied directly.
• Uses helper functions from bundled dependencies to load options dynamically (e.g., fetching groups, dashboards).

Troubleshooting

• Missing or invalid token: If no token is provided or it is invalid, the node throws an error stating that the authentication token is required. Ensure you provide a valid bearer token without the "Bearer" prefix.
• Token format issues: If the token string starts with "Bearer ", the node automatically strips this prefix. Providing the token with or without the prefix should work, but avoid including extra spaces.
• API errors: Errors returned from the Power BI API (e.g., unauthorized, forbidden) will appear in the output JSON under an error field. Verify token permissions and scopes.
• Loading options failures: When loading dynamic options like groups or dashboards, if the token is missing or invalid, the node returns placeholder error messages prompting to check the token.
• Continue on Fail: If enabled, the node continues processing subsequent items even if one fails, returning error details per item.

Links and References

• Power BI REST API Documentation
• Power BI Authentication Overview
• n8n Documentation - Creating Custom Nodes