Actions45
- General Actions
- About API Actions
- Accounts API Actions
- Transactions API Actions
- Categories API Actions
- Tags API Actions
- Rules & Groups API Actions
Overview
This node integrates with the FireFly III API to export various types of financial data. Specifically, the "General" resource with the "Export Data" operation allows users to export different categories of data such as accounts, bills, budgets, categories, piggy banks, recurring transactions, rules, tags, and transactions.
The node supports exporting data in JSON by default or CSV format for most data types except transactions, which require date range filters and optionally account filters.
Common scenarios where this node is beneficial:
- Exporting financial data for backup or migration purposes.
- Extracting transaction data within a specific date range for reporting or analysis.
- Automating periodic exports of budget, category, or tag data for integration with other systems.
- Generating CSV files for use in spreadsheets or other tools.
Practical example:
- A user wants to export all transactions between January 1, 2023, and March 31, 2023, for specific accounts to analyze spending patterns in Excel. They configure the node to export "Transactions" with the required start and end dates and specify account IDs if needed. The node returns a CSV file containing the filtered transactions.
Properties
| Name | Meaning |
|---|---|
| X-Trace-ID | A unique UUID identifier for the request, used for debugging and tracing (e.g., 123e4567-e89b-12d3-a456-426614174000). |
| Export Type | The type of data to export. Options include: Accounts, Bills, Budgets, Categories, Piggy Banks, Recurring Transactions, Rules, Tags, Transactions. |
| Format | The format to export the data in. Options are None (default JSON) or CSV. CSV is available for all export types except Transactions. |
| Start Date | (Required for Transactions export) The start date for the export in YYYY-MM-DD format. |
| End Date | (Required for Transactions export) The end date for the export in YYYY-MM-DD format. |
| Account IDs | (Optional for Transactions export) Comma-separated list of account IDs to filter transactions. |
Output
- The node outputs the exported data in the
jsonfield when exporting in JSON format. - When exporting in CSV format, the node outputs the data as binary under the
binary.dataproperty. The binary data contains the CSV file content, and the filename is derived from the HTTP response headers or defaults toexport.csv. - For transactions export, the output respects the specified date range and optional account filters.
- The structure of the JSON output depends on the export type selected and corresponds to the FireFly III API's export endpoint response.
Dependencies
- Requires an active connection to the FireFly III API.
- Requires an API authentication token configured in n8n credentials (referred generically as an API key credential).
- No additional external dependencies beyond the FireFly III API.
Troubleshooting
- Missing or invalid API credentials: Ensure that the API authentication token is correctly configured in n8n credentials.
- Invalid date formats for transactions export: The
Start DateandEnd Datemust be inYYYY-MM-DDformat. Incorrect formats may cause API errors. - Empty or no data returned: Verify that the date range and account filters actually match existing data in FireFly III.
- CSV export issues: If the CSV file is not generated or is empty, check that the export type supports CSV format and that the API response includes the expected content-disposition header.
- Network or API errors: Check connectivity to the FireFly III server and ensure the API endpoint is reachable.