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 dataflow transactions within a specified workspace. It is useful for users who want to monitor or audit changes and activities related to dataflows in their Power BI environment. For example, a business analyst or data engineer might use this node to fetch transaction logs of a particular dataflow to understand recent updates or troubleshoot issues.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Power BI API. Options: OAuth2, Bearer Token |
| Workspace Name or ID | The workspace (group) containing the target dataflow. Select from a list or specify an ID via expression |
| Dataflow Name or ID | The specific dataflow to get transactions for. Select from a list or specify an ID via expression |
Output
The node outputs JSON data representing the transactions associated with the specified dataflow. Each item in the output array corresponds to a transaction record detailing changes or operations performed on the dataflow. This structured data can be used downstream for logging, auditing, or triggering further workflows.
No binary data output is indicated for this operation.
Dependencies
- Requires access to the Power BI API.
- Requires valid authentication credentials configured in n8n, either via OAuth2 or a Bearer token.
- The node depends on dynamic loading of available workspaces and dataflows through internal methods that query the Power BI environment.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens may cause authorization errors.
- Specifying a workspace or dataflow that does not exist or to which the user lacks access will result in errors.
- Network connectivity issues can prevent successful API calls.
Error Messages:
"The resource "dataflow" is not supported!"— indicates an unsupported resource was selected; ensure "Dataflow" is chosen.- Authorization errors typically mention invalid credentials or insufficient permissions; verify API keys or OAuth2 tokens.
- If no transactions are returned, confirm that the dataflow has recorded transactions and that the correct IDs are used.
Links and References
- Power BI REST API Documentation
- n8n Expressions Documentation (for specifying IDs dynamically)