Actions32
- Admin Actions
- Dashboard Actions
- Dataflow Actions
- Dataset Actions
- Gateway Actions
- Group Actions
- Report Actions
Overview
This node interacts with the Power BI API, specifically to retrieve information about a datasource within a specified gateway. It is useful when you need to programmatically access detailed metadata or configuration of datasources managed by Power BI gateways.
Common scenarios include:
- Automating monitoring or auditing of datasources connected through Power BI gateways.
- Integrating datasource details into broader workflows for reporting or alerting.
- Fetching datasource configurations dynamically to support data pipeline orchestration.
For example, you might use this node to get the connection details of a datasource before triggering a dataset refresh or to verify datasource status as part of an automated health check.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with the Power BI API. Options: OAuth2, Bearer Token |
| Gateway Name or ID | The specific Power BI gateway that contains the datasource. Select from a list or specify an ID via expression. |
| Datasource Name or ID | The datasource to retrieve from the selected gateway. Select from a list or specify an ID via expression. |
Output
The node outputs JSON data representing the retrieved datasource's details. This typically includes metadata such as datasource name, type, connection details, and other relevant configuration information as provided by the Power BI API.
If the datasource has any binary content (e.g., certificates or keys), it would be included in the binary output field, but based on the static code analysis, this node primarily returns JSON metadata.
Dependencies
- Requires valid authentication credentials for the Power BI API, either via OAuth2 or a bearer token.
- The node depends on the Power BI API endpoints for gateways and datasources.
- n8n environment must have these credentials configured accordingly.
- The node uses internal helper methods to load options dynamically (e.g., available gateways and datasources).
Troubleshooting
Common issues:
- Invalid or expired authentication tokens will cause API calls to fail.
- Specifying a gateway or datasource ID that does not exist or is inaccessible will result in errors.
- Network connectivity issues can prevent successful API communication.
Error messages:
"The resource "gateway" is not supported!"— indicates an unsupported resource was selected; ensure "Gateway" is chosen.- API errors returned from Power BI (e.g., 401 Unauthorized, 404 Not Found) should be checked by verifying credentials and IDs.
Resolutions:
- Refresh or reconfigure authentication credentials if authorization errors occur.
- Double-check gateway and datasource IDs or names for correctness.
- Use expressions carefully to ensure they resolve to valid values.