Actions32
- Admin Actions
- Dashboard Actions
- Dataflow Actions
- Dataset Actions
- Gateway Actions
- Group Actions
- Report Actions
Overview
This node integrates with the Power BI API to retrieve information about reports and their pages within a specified workspace (group). The "Get Pages" operation under the "Report" resource fetches all pages of a given report. This is useful for scenarios where you want to analyze or manipulate individual report pages, automate report documentation, or integrate report page data into other workflows.
Practical examples:
- Automatically list all pages of a specific Power BI report to generate a table of contents.
- Extract page metadata for auditing or reporting purposes.
- Use page details to trigger further actions like exporting or refreshing specific report pages.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Power BI API. Options: OAuth2, Bearer Token. |
| Group (Workspace) Name or ID | Power BI workspace identifier. Leave blank to use "My Workspace". Can be selected from a list or specified via expression. |
| Report Name or ID | Identifier of the report whose pages are to be retrieved. Must be selected from a list or specified via expression. |
Output
The node outputs an array of JSON objects, each representing a page within the specified Power BI report. Each object typically contains metadata about a page such as its name, display name, and unique identifier. This structured output allows downstream nodes to process or filter pages individually.
If the node supports binary data output (not indicated here), it would typically represent exported report pages or images, but this operation focuses on JSON metadata only.
Dependencies
- Requires access to the Power BI API.
- Needs either OAuth2 credentials or a Bearer Token for authentication.
- The node uses dynamic loading methods to populate dropdowns for groups (workspaces) and reports, which depend on successful API calls.
- Proper permissions in Power BI to read report and workspace information are necessary.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens will cause authorization errors.
- Specifying a non-existent group or report ID will result in not found errors.
- Network connectivity problems can prevent API calls from succeeding.
Error messages and resolutions:
"The resource \"report\" is not supported!"— Indicates an unsupported resource; ensure the resource parameter is set correctly.- Authorization errors — Verify that the provided OAuth2 or Bearer Token credentials are valid and have sufficient permissions.
"Report not found"or similar — Check that the report ID and group ID are correct and accessible by the authenticated user.- If the node fails but "Continue On Fail" is enabled, error details will be included in the output for easier debugging.