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 different Power BI resources. Specifically, for the Admin resource and the Get Scan Result operation, it retrieves the scan result of a workspace scan previously initiated (typically by a "getInfo" operation). This is useful for administrators who want to programmatically access detailed scan results about their Power BI workspaces, such as metadata or compliance information.
Practical scenarios include:
- Automating the retrieval of workspace scan results for auditing or reporting.
- Integrating Power BI workspace scan data into other systems or workflows.
- Monitoring workspace changes or compliance status via scheduled workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use when connecting to Power BI API. Options: OAuth2, Bearer Token |
| Scan ID | The unique identifier of the scan result to retrieve. This ID is generated by the "getInfo" operation |
Output
The node outputs an array of JSON objects representing the scan result data retrieved from the Power BI API for the specified Scan ID. Each item in the output corresponds to part or all of the scan result details.
- The
jsonfield contains the scan result data structure as returned by the Power BI API. - No binary data output is indicated for this operation.
Dependencies
- Requires valid Power BI API credentials configured in n8n, either via OAuth2 or a Bearer Token.
- The node depends on the Power BI API being accessible and the provided Scan ID being valid and associated with the authenticated user’s workspace scans.
Troubleshooting
- Invalid Scan ID: If the Scan ID does not exist or is incorrect, the node will likely throw an error indicating that the scan result could not be found. Verify the Scan ID was correctly obtained from a prior "getInfo" operation.
- Authentication Errors: Using invalid or expired credentials will cause authentication failures. Ensure the OAuth2 token or Bearer Token is valid and has sufficient permissions.
- API Rate Limits: Frequent requests may hit Power BI API rate limits, resulting in errors. Implement retry logic or reduce request frequency.
- Resource or Operation Not Supported: If the node configuration specifies unsupported resource-operation combinations, it will throw an error. Confirm the resource is set to "Admin" and operation to "Get Scan Result".
Links and References
- Power BI REST API Documentation
- Power BI Admin APIs
- n8n Expressions Documentation (for dynamic Scan ID input)