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 "Get Attachments" operation. It retrieves attachments related to a specific transaction by its ID. This is useful in scenarios where you want to programmatically access files or documents (such as receipts, invoices, or other supporting materials) linked to financial transactions stored in FireFly III.

Practical examples include:

  • Automatically fetching and processing transaction attachments for bookkeeping or auditing.
  • Integrating transaction attachments into document management systems.
  • Triggering workflows based on the presence or content of attachments.

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). Optional but helpful for tracing requests.
Transaction ID The unique identifier of the transaction whose attachments you want to retrieve. This is required.
Pagination Options Controls pagination of results:
- Limit: Maximum number of attachments to return (minimum 1, default 50).
- Page: Page number to retrieve (minimum 1, default 1).

Output

The output is a JSON object containing the list of attachments associated with the specified transaction. The structure corresponds directly to the FireFly III API response for transaction attachments, typically including metadata about each attachment such as filename, size, type, and possibly URLs or IDs to access the actual files.

No binary data output is produced by this operation; it only returns metadata in JSON format.

Dependencies

  • Requires an active connection to the FireFly III API via an OAuth2 or similar API authentication credential configured in n8n.
  • The node depends on the FireFly III API being accessible and the user having appropriate permissions to read transaction attachments.
  • No additional environment variables are explicitly required beyond the API credentials.

Troubleshooting

  • Missing or invalid Transaction ID: The operation requires a valid transaction ID. Ensure that the ID provided exists and is correctly formatted.
  • API authentication errors: If the API key or OAuth token is missing, expired, or invalid, the node will fail to authenticate. Verify your credentials configuration.
  • Pagination issues: Requesting pages beyond the available range may return empty results. Adjust the limit and page parameters accordingly.
  • Network or connectivity problems: Ensure that the FireFly III API endpoint is reachable from your n8n instance.
  • Permission denied errors: The authenticated user must have permission to view attachments for the specified transaction.

Common error messages usually come directly from the FireFly III API and might indicate invalid input, unauthorized access, or server errors. Reviewing the X-Trace-ID in logs can help trace and debug issues.

Links and References

Discussion