FireFly III icon

FireFly III

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

Actions45

Overview

This node interacts with the FireFly III API, specifically focusing on the Transactions API resource and its operation to list transaction links for a journal. It retrieves all linked transactions associated with a specific transaction journal or split ID. This is useful in scenarios where you want to explore relationships between transactions within a journal, such as viewing all splits or related entries tied to a particular transaction.

Practical examples include:

  • Fetching all linked transactions for a given transaction journal to analyze how a complex transaction is split across accounts.
  • Auditing or reporting on transaction relationships within financial records managed by FireFly III.

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).
Transaction ID The ID of the transaction journal or split for which to list linked transactions. This is required.
Pagination Options Controls pagination of results:
- Limit: Max number of results to return (minimum 1, default 50).
- Page: Page number to retrieve (minimum 1, default 1).

Additionally, there are informational notices guiding users to the official API documentation and clarifying that the Transaction ID should correspond to a transaction journal or split ID.

Output

The output is a JSON object containing the list of transaction links associated with the specified transaction journal ID. The structure corresponds directly to the FireFly III API response for the endpoint /transaction-journals/{transactionId}/links.

Typical fields in the JSON output may include arrays of linked transactions with their details such as IDs, amounts, dates, and related metadata depending on the API's response schema.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the FireFly III API via an authenticated credential (such as an OAuth2 token).
  • The node depends on the FireFly III API being accessible and the user having appropriate permissions to read transaction journals and their links.
  • No additional environment variables or external services beyond the FireFly III API and its authentication are needed.

Troubleshooting

  • Missing or invalid Transaction ID: The operation requires a valid transaction journal ID. Ensure the ID is correct and exists in FireFly III.
  • API authentication errors: If the API key or OAuth token is missing, expired, or invalid, requests will fail. Verify credentials and re-authenticate if necessary.
  • Pagination issues: Setting the limit or page parameters incorrectly (e.g., less than 1) may cause errors or unexpected results. Use sensible values.
  • Network or connectivity problems: Ensure the FireFly III API endpoint is reachable from your n8n instance.
  • Unexpected API responses: If the API changes or returns errors, check the FireFly III API status and documentation for updates.

Links and References

Discussion