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 perform various operations on Power BI resources. Specifically, for the Group resource and the Get Reports operation, it retrieves reports associated with a specified Power BI group (workspace). This is useful when you want to programmatically access report metadata or details within a particular workspace in Power BI.
Common scenarios include:
- Automating report management workflows by fetching all reports in a workspace.
- Integrating Power BI report data into other systems or dashboards.
- Monitoring or auditing reports available in specific workspaces.
Example: You might use this node to get a list of all reports in a marketing team's Power BI workspace to generate a summary report or trigger further processing based on report availability.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Power BI API. Options: OAuth2 or Bearer Token. |
| Group Name or ID | The Power BI group (workspace) from which to retrieve reports. Choose from a dropdown list or specify an ID using an expression. |
Output
The node outputs an array of JSON objects representing the reports retrieved from the specified Power BI group. Each object contains metadata about a report, such as its ID, name, and other relevant properties provided by the Power BI API.
If the node supports binary data output (not explicitly shown here), it would typically represent report content or exported files; however, for the "Get Reports" operation, the output is JSON metadata only.
Dependencies
- Requires valid authentication credentials for Power BI API access, either via OAuth2 or a Bearer Token.
- The node depends on the Power BI API being accessible and the user having appropriate permissions to read reports in the specified group.
- No additional external services are required beyond Power BI itself.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens will cause authorization errors.
- Specifying a non-existent or inaccessible group ID will result in errors or empty results.
- Network connectivity problems can prevent API calls from succeeding.
Error messages:
"The resource \"group\" is not supported!"— indicates an unsupported resource was selected; ensure "Group" is chosen.- Authorization errors typically mention invalid credentials or insufficient permissions; verify your API key or OAuth2 token.
- If the node returns an error message wrapped in the output, enabling "Continue On Fail" allows processing to continue despite individual item failures.
Links and References
Note: This summary is based solely on static analysis of the provided source code and property definitions. Runtime behavior may depend on actual API responses and environment configuration.