Actions24
- Admin Actions
- Dashboard Actions
- Dataset Actions
- Group Actions
- Report Actions
- Token Actions
Overview
This node enables exporting Power BI reports to files in various formats. It supports both standard Power BI reports and paginated reports, allowing users to specify export options such as format type (PDF, PNG, PPTX for Power BI reports; PDF, CSV, Excel, Word, etc., for paginated reports), locale, page selection, filters, parameters, and Row-Level Security identities.
Common scenarios include:
- Automating report exports for archival or distribution.
- Generating report snapshots in different formats for sharing via email or messaging platforms.
- Integrating report exports into workflows that require report data in specific file formats.
- Applying filters or bookmarks dynamically before export to customize the output.
Practical example:
- A marketing team automatically exports a Power BI sales report as a PDF every morning and sends it via email.
- An operations team exports a paginated report filtered by region and date range to Excel for further analysis.
Properties
| Name | Meaning |
|---|---|
| Authentication Token | Bearer token for authentication (without the "Bearer" prefix). Required to authorize API requests. |
| Workspace Name or ID | The ID of the Power BI workspace (group) containing the report. Can be selected from a list or specified via expression. |
| Report Name or ID | The ID of the report to export. Can be selected from a list or specified via expression. |
| Report Type | Type of report to export: "Power BI Report" or "Paginated Report". |
| Export Format | Format to export the report to. For Power BI reports: PDF, PNG, PowerPoint (PPTX). For Paginated reports: PDF, Accessible PDF, CSV, Image (BMP, EMF, GIF, JPEG, PNG, TIFF), Microsoft Excel (XLSX), Microsoft Word (DOCX), MHTML, XML. |
| Wait For Completion | Whether to wait for the export process to complete before returning the result. |
| Baixar Arquivo | If enabled (and waiting for completion), the exported file will be available as binary data for download and also as base64 in the fileBase64 field for use in integrations like WhatsApp. |
| Additional Fields | Collection of optional fields: • Maximum Wait Time (seconds) - max time to wait for export completion. • Polling Interval (seconds) - interval between status checks during export. |
| Power BI Report Configuration | Options specific to Power BI reports: • Include Hidden Pages (boolean) • Locale (string, e.g., "en-US") • Export Specific Pages (boolean) with JSON array of pages • Use Report Level Filters (boolean) with JSON filters • Use Default Bookmark (boolean) with bookmark name and state • Use Alternative Dataset (boolean) with dataset ID • Use Identities (RLS) (boolean) with JSON identities for row-level security |
| Paginated Report Configuration | Options specific to paginated reports: • Locale (string) • Use Parameters (boolean) with JSON array of parameter name-value pairs • Use Format Settings (boolean) with JSON object of format-specific settings • Use Identities (RLS) (boolean) with JSON identities for row-level security |
Output
The node outputs JSON data representing the result of the export operation. If the "Baixar Arquivo" option is enabled and the node waits for completion, the exported file is provided as binary data attached to the output item, enabling direct download or further processing in workflows.
Additionally, the exported file content is available as a base64-encoded string in the fileBase64 field within the JSON output, facilitating integration with services that accept base64 file content (e.g., sending files over WhatsApp).
If the node does not wait for completion, the output typically contains metadata about the export job status or an export identifier.
Dependencies
- Requires a valid Bearer authentication token with sufficient permissions to access the Power BI API.
- The node interacts with the official Power BI REST API endpoints (
https://api.powerbi.com/v1.0/myorg). - No internal credential types are exposed; users must provide the authentication token manually or via upstream nodes.
- Network connectivity to Power BI service endpoints is required.
- Optional: JSON-formatted strings for advanced configurations (pages, filters, parameters, identities) must be well-formed.
Troubleshooting
- Missing or invalid authentication token: The node requires a valid Bearer token. Ensure the token is provided either as input data or in the node parameter. Tokens should not include the "Bearer" prefix.
- Invalid workspace or report IDs: Selecting or specifying incorrect workspace or report IDs will cause API errors. Use the provided load options to select valid IDs or verify expressions carefully.
- Malformed JSON in configuration fields: Fields like pages, filters, parameters, and identities expect valid JSON arrays or objects. Invalid JSON will cause parsing errors.
- Timeouts waiting for export completion: The export may take longer than the default maximum wait time. Adjust "Maximum Wait Time" and "Polling Interval" accordingly.
- Unsupported export format for report type: Ensure the export format matches the report type (Power BI vs. Paginated). Using unsupported combinations may cause errors.
- Row-Level Security (RLS) issues: When using identities for RLS, ensure the JSON identity configurations are correct and that the user has appropriate permissions.
- API rate limits or permission errors: Check that the token has necessary scopes and that the Power BI service is accessible.