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 to retrieve transactions associated with a specific tag. It is useful for users who want to filter and analyze financial transactions by tags they have assigned, enabling better categorization and reporting of expenses or incomes.

Typical use cases include:

  • Fetching all transactions labeled with a particular tag to review spending in a category.
  • Applying date range filters to analyze tagged transactions within a specific period.
  • Paginating through large sets of tagged transactions to process or export data incrementally.

For example, a user might want to get all transactions tagged as "Business Travel" between January 1st and March 31st, limiting results to 100 per page.

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).
Target Tag Name/ID The name or ID of the tag whose transactions you want to retrieve. Note: Using tag names with international characters may cause issues.
Pagination Options Controls pagination of results:
• Limit: Maximum number of results to return (minimum 1).
• Page: Page number to retrieve.
Date Range Filters Filters transactions by date range:
• Start Date: Filter results starting from this date (format YYYY-MM-DD).
• End Date: Filter results up to this date (format YYYY-MM-DD).

Output

The node outputs JSON data containing the list of transactions associated with the specified tag. The structure corresponds directly to the FireFly III API response for /tags/{tagNameId}/transactions, typically including transaction details such as amounts, dates, descriptions, and related metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the FireFly III API with appropriate authentication credentials (such as an OAuth2 token).
  • The node expects the FireFly III instance URL and credentials to be configured in n8n.
  • The X-Trace-ID header is optional but can be provided for enhanced request tracing and debugging.

Troubleshooting

  • Invalid Tag Name/ID: If the tag does not exist or the name/ID is incorrect, the API will likely return a 404 error. Verify the tag identifier is correct.
  • International Characters in Tag Name: Using tag names with non-ASCII characters may cause unexpected behavior. Prefer using tag IDs when possible.
  • Pagination Limits: Setting very high limits may result in timeouts or large responses. Use reasonable limits and paginate through results.
  • Date Format Errors: Ensure that start and end dates are in the YYYY-MM-DD format; otherwise, the API may reject the request.
  • Authentication Issues: If the API returns unauthorized errors, check that the API credentials are valid and have sufficient permissions.

Links and References

Discussion