Actions24
- Admin Actions
- Dashboard Actions
- Dataset Actions
- Group Actions
- Report Actions
- Token Actions
Overview
This node interacts with the Power BI API using header-based authentication. Specifically, for the Admin resource and the Get Scan Result operation, it retrieves the result of a workspace scan previously generated by another operation. This is useful in scenarios where you want to programmatically fetch detailed scan results about Power BI workspaces for auditing, monitoring, or integration purposes.
Practical examples include:
- Automatically retrieving scan results to analyze workspace contents.
- Integrating scan data into reporting or alerting workflows.
- Using scan results to trigger further automation based on workspace status or metadata.
Properties
| Name | Meaning |
|---|---|
| Authentication Token | Bearer token for authentication (without the "Bearer" prefix). Required to authorize API calls. |
| ID do Scan | The ID of the scan result generated by the getInfo operation. Identifies which scan result to retrieve. |
Output
The node outputs JSON data representing the scan result of a Power BI workspace. The exact structure depends on the scan performed but typically includes detailed information about the workspace's contents, datasets, reports, and other metadata collected during the scan.
No binary data output is indicated for this operation.
Dependencies
- Requires a valid Bearer token for Power BI API authentication. This token must be provided either as an input or via the node parameter.
- The node uses the Power BI REST API endpoint
https://api.powerbi.com/v1.0/myorg. - No additional external services or environment variables are explicitly required beyond the authentication token.
Troubleshooting
- Missing or invalid token: If the authentication token is missing or invalid, the node will throw an error indicating that the token is mandatory. Ensure the token is correctly provided without the "Bearer" prefix.
- Scan ID not provided or incorrect: The node requires a valid scan ID generated from a previous scan operation. Providing an incorrect or empty scan ID will likely cause the API call to fail.
- API errors: Errors returned from the Power BI API (e.g., permission issues, expired tokens) will propagate as node errors. Verify token validity and permissions.
- Token format: The node automatically strips the "Bearer " prefix if included; however, best practice is to provide the raw token string only.
Links and References
- Power BI REST API Documentation
- Power BI Admin APIs
- OAuth 2.0 Authorization Framework (for understanding token generation)
This summary is based solely on static analysis of the provided source code and property definitions.