FireFly III

Overview

The "Get Transaction" operation of the Transactions API resource in this node allows users to retrieve detailed information about a specific financial transaction by its unique ID. This is useful for workflows that need to fetch and process individual transaction data from FireFly III, such as auditing transactions, displaying transaction details in reports, or integrating transaction data into other systems.

For example, you might use this node to:

• Fetch a transaction's details after it has been created elsewhere.
• Retrieve transaction data to verify amounts, categories, or tags before further processing.
• Automate reconciliation processes by pulling transaction info based on IDs from external sources.

Properties

Output

The output JSON contains the full details of the requested transaction as returned by the FireFly III API. This typically includes fields such as transaction amount, date, description, involved accounts, categories, tags, and any other metadata associated with the transaction.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": "transaction-id",
  "date": "2024-01-01",
  "amount": 100.00,
  "description": "Grocery shopping",
  "category": "Food",
  "tags": ["groceries", "weekly"],
  "accounts": {
    "source": "checking-account-id",
    "destination": "store-account-id"
  },
  ...
}

Dependencies

• Requires an active connection to the FireFly III API via an OAuth2 API credential or equivalent authentication method configured in n8n.
• The node makes HTTP GET requests to the /transactions/{transactionId} endpoint of the FireFly III API.

Troubleshooting

• Missing or invalid Transaction ID: The operation requires a valid transaction ID. If omitted or incorrect, the API will return an error indicating the transaction was not found.
• Authentication errors: Ensure the API credentials are correctly set up and have sufficient permissions to access transaction data.
• Network or connectivity issues: Verify that the FireFly III API endpoint is reachable from your n8n instance.
• X-Trace-ID usage: If using the optional X-Trace-ID, ensure it is a valid UUID string to aid in debugging; otherwise, omit it.

Common error messages:

• 404 Not Found: The specified transaction ID does not exist.
• 401 Unauthorized or 403 Forbidden: Authentication failed or insufficient permissions.
• 400 Bad Request: Invalid parameters passed to the API.

Resolving these usually involves verifying input parameters, checking credentials, and ensuring network connectivity.

Links and References

• FireFly III API Documentation
• FireFly III Official Site
• UUID Format Reference