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 data sources associated with a specific dataflow within a workspace. It is useful for users who want to programmatically access and manage metadata about their Power BI dataflows, particularly to understand which data sources feed into a given dataflow.
Practical scenarios include:
- Auditing or documenting data sources used in Power BI dataflows.
- Automating monitoring or reporting workflows that depend on dataflow source information.
- Integrating Power BI dataflow metadata into broader data management or ETL pipelines.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Power BI API: either OAuth2 or Bearer Token (API key). |
| Workspace Name or ID | The workspace (group) containing the target dataflow. Can be selected from a list or specified by ID. |
| Dataflow Name or ID | The specific dataflow to retrieve data sources for. Can be selected from a list filtered by workspace. |
Output
The node outputs JSON data representing the data sources of the specified dataflow. Each item in the output array corresponds to a data source linked to the dataflow, including relevant metadata as provided by the Power BI API.
If the node supports binary data output (not indicated here), it would typically represent files or attachments related to the data sources, but this node focuses on JSON metadata.
Dependencies
- Requires an active connection to the Power BI API.
- Supports two authentication methods: OAuth2 or Bearer Token (API key).
- Uses dynamic loading methods to populate selectable options for workspaces and dataflows.
- No additional external dependencies beyond standard n8n credentials and HTTP request capabilities.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens can cause authorization errors.
- Specifying a workspace or dataflow ID that does not exist or to which the user lacks access will result in errors.
- Network connectivity problems may prevent API calls from succeeding.
Error messages:
"The resource "dataflow" is not supported!"— indicates an unsupported resource was selected; ensure "Dataflow" is chosen.- API error messages related to authentication failures suggest checking the validity and permissions of the provided credentials.
- Errors about missing or invalid IDs indicate that the workspace or dataflow identifiers need verification.
Resolutions:
- Re-authenticate or refresh credentials if authorization fails.
- Verify workspace and dataflow selections are correct and accessible.
- Check network settings and proxy configurations if requests time out or fail.