Actions24
- Admin Actions
- Dashboard Actions
- Dataset Actions
- Group Actions
- Report Actions
- Token Actions
Overview
This node enables interaction with the Power BI API using header-based authentication via a bearer token. Specifically, for the Dataset resource and the Get Refresh History operation, it retrieves the refresh history records of a specified Power BI dataset within an optional workspace (group). This is useful for monitoring dataset refresh activities, troubleshooting refresh failures, or auditing refresh schedules.
Practical examples:
- Automatically fetch the last N refresh attempts of a dataset to monitor success/failure rates.
- Integrate dataset refresh history into custom dashboards or alerting systems.
- Audit refresh patterns across multiple datasets in a workspace.
Properties
| Name | Meaning |
|---|---|
| Authentication Token | Bearer token for authentication (without the "Bearer" prefix). Required to authorize API calls. |
| Group (Workspace) | Power BI group (workspace) ID. Leave blank to use "My Workspace". |
| Dataset | ID of the dataset whose refresh history will be retrieved. |
| Limit | Maximum number of refresh history entries to return (corresponds to the $top query parameter). |
Output
The node outputs JSON data representing the refresh history entries of the specified dataset. Each entry typically includes details such as refresh start time, end time, status (success/failure), and possibly error messages if a refresh failed.
If binary data were involved (not applicable here), it would be summarized accordingly, but this operation returns only JSON data.
Dependencies
- Requires a valid Bearer token for Power BI API authentication. The token must have sufficient permissions to access the dataset and its refresh history.
- No additional external dependencies beyond the Power BI REST API.
- The node expects the token either as input data or as a parameter.
- The base URL used is
https://api.powerbi.com/v1.0/myorg.
Troubleshooting
- Missing or invalid token: If the authentication token is missing or invalid, the node throws an error indicating that the token is required or that authentication failed. Ensure you provide a valid bearer token without the "Bearer" prefix.
- Invalid group or dataset ID: If the group (workspace) or dataset ID is incorrect or inaccessible, the API call will fail. Verify IDs are correct and that the token has access rights.
- API rate limits or network issues: Temporary failures may occur due to API throttling or connectivity problems. Retrying after some delay can help.
- Empty results: If no refresh history exists or the limit is set too low, the output may be empty. Adjust the "Limit" property accordingly.