FireFly III icon

FireFly III

Read, update, write and delete data using the powerful FireFly III API

Actions45

Overview

The "Get Transactions" operation under the "Accounts API" resource in this node retrieves a list of transactions associated with a specific account from the FireFly III financial management system. It allows filtering transactions by type and date range, as well as controlling pagination to manage large result sets.

This operation is useful when you want to programmatically access detailed transaction data for an account, such as for reporting, auditing, or integration with other financial tools. For example, you could use it to fetch all expenses within a certain period or to retrieve deposits made to a particular account.

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).
Account ID The ID of the account whose transactions you want to retrieve. This is a required field.
Transaction Type Filter transactions by type. Options include: no filter (--), all, withdrawal(s), expense, deposit(s), income, transfer(s), opening balance, reconciliation, special(s), default.
Pagination Options Controls the number of results and page to retrieve:
• Limit: Max number of results per page (minimum 1, default 50).
• Page: Page number to retrieve (minimum 1, default 1).
Date Range Filters Filters transactions by date range:
• Start Date: Filter results starting from this date (YYYY-MM-DD).
• End Date: Filter results up to this date (YYYY-MM-DD).

Output

The output is a JSON object containing the retrieved transactions for the specified account. The structure corresponds directly to the FireFly III API response for the /accounts/{accountId}/transactions endpoint. Typically, this includes an array of transaction objects with details such as transaction IDs, dates, amounts, types, descriptions, and related metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires connection to a FireFly III instance with appropriate API access.
  • Requires an API authentication token configured in n8n credentials to authorize requests.
  • The node uses the FireFly III REST API endpoints; network connectivity to the FireFly III server is necessary.

Troubleshooting

  • Missing or invalid Account ID: The operation requires a valid account ID. Ensure the account ID exists in your FireFly III instance and is correctly entered.
  • Invalid date formats: Date filters must be in YYYY-MM-DD format. Incorrect formats may cause errors or no results.
  • Pagination issues: Setting very high limits or invalid page numbers may lead to unexpected results or API errors.
  • API authentication errors: Ensure that the API key or OAuth2 token is valid and has sufficient permissions.
  • Empty results: If no transactions are returned, verify that the account contains transactions matching the filters applied.
  • Network or server errors: Check connectivity and FireFly III server status if requests fail.

Links and References

Discussion