Actions20
- Dataset Actions
- Group Actions
- Report Actions
- Admin Actions
- Dashboard Actions
Overview
This node interacts with the Power BI API, specifically providing administrative operations related to workspaces (referred to as "Admin" resource). The operation Obter Resultado de Scan ("Get scan result") retrieves the results of a previously performed scan on a workspace. This is useful for scenarios where you want to analyze or audit the metadata and structure of Power BI workspaces after scanning them.
Practical examples include:
- Automating the retrieval of scan results to monitor changes or issues in Power BI workspaces.
- Integrating scan results into reporting workflows to track workspace health or compliance.
- Using scan data to trigger further automation based on workspace content or status.
Properties
| Name | Meaning |
|---|---|
| ID do Scan | The unique identifier of the scan result generated by a previous scan operation (getInfo). This ID is required to fetch the specific scan result. |
Output
The node outputs JSON data representing the scan result associated with the provided scan ID. The exact structure depends on the scan details returned by the Power BI API but generally includes metadata about the scanned workspace, such as datasets, reports, lineage, and other relevant information captured during the scan.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Power BI API using an API key or OAuth token configured in n8n credentials.
- The node uses the base URL
https://api.powerbi.com/v1.0/myorgfor API requests. - The user must have appropriate permissions to access workspace scan results in Power BI.
Troubleshooting
Common Issues:
- Providing an invalid or expired scan ID will likely result in an error or empty response.
- Insufficient permissions to access the workspace or scan results can cause authorization errors.
- Network connectivity issues may prevent successful API calls.
Error Messages:
- Errors from the Power BI API will be surfaced, often indicating invalid parameters or authentication failures.
- If the node encounters an unsupported resource or operation, it throws an error stating the resource is not supported.
Resolutions:
- Verify the scan ID is correct and corresponds to a completed scan.
- Ensure the API credentials have sufficient privileges.
- Check network connectivity and API endpoint accessibility.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.