Actions32
- Admin Actions
- Dashboard Actions
- Dataflow Actions
- Dataset Actions
- Gateway Actions
- Group Actions
- Report Actions
Overview
This node interacts with the Power BI API to retrieve information about datasets, specifically to get the tables within a specified dataset. It is useful when you want to programmatically explore or manipulate the structure of your Power BI datasets, for example, to automate reporting workflows, data validation, or integration with other systems.
A practical example would be:
- Automatically fetching all tables from a dataset in a Power BI workspace to generate documentation or metadata reports.
- Using the table list to dynamically build queries or data transformations in downstream nodes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Power BI API. Options: OAuth2, Bearer Token |
| Group (Workspace) Name or ID | The Power BI group (workspace) identifier. Leave blank to use "My Workspace". Can select from a list or specify an ID via expression. |
| Dataset Name or ID | The identifier of the dataset from which to retrieve tables. Required. Can select from a list or specify an ID via expression. |
Output
The node outputs JSON data representing the tables contained in the specified dataset. Each item in the output array corresponds to a table and includes its properties as returned by the Power BI API.
If the node supports binary data output (not indicated here), it would typically represent file contents or images related to the dataset, but this operation focuses on JSON metadata only.
Dependencies
- Requires access to the Power BI API.
- Needs either OAuth2 authentication or a Bearer Token credential configured in n8n.
- The node depends on dynamic loading methods to fetch available groups (workspaces) and datasets for user selection.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials will cause API request failures.
- Specifying a non-existent group or dataset ID will result in errors indicating resource not found.
- Network connectivity problems can prevent successful API calls.
Error messages:
"The resource \"dataset\" is not supported!"— indicates an internal misconfiguration or unsupported resource; ensure the node is correctly set to "Dataset" resource.- API errors returned from Power BI (e.g., 401 Unauthorized, 404 Not Found) should be checked by verifying credentials and IDs.
Resolutions:
- Re-authenticate or update API keys if authorization fails.
- Verify that the group and dataset IDs exist and are accessible with the provided credentials.
- Check network settings and proxy configurations if requests time out.