FireFly III icon

FireFly III

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

Overview

This node integrates with the FireFly III API, a personal finance manager, to perform various operations across multiple resources such as accounts, transactions, categories, tags, rules, and general system information. Specifically, for the About API resource and the Get Current Authenticated User Info operation, the node fetches detailed information about the currently authenticated user from the FireFly III system.

Common scenarios where this node is beneficial include:

  • Retrieving metadata about the logged-in user to personalize workflows.
  • Auditing or logging user details in automation processes.
  • Integrating user-specific data into broader financial automation pipelines.

Practical example:

  • Automatically fetching the current user's profile info to tag transactions or reports with user-specific identifiers.

Properties

Name Meaning
X-Trace-ID A unique UUID identifier for the request, used for debugging and tracing. Example: 123e4567-e89b-12d3-a456-426614174000

Note: The node also displays a notice linking to the official FireFly III API documentation for further reference.

Output

The output of the Get Current Authenticated User Info operation is a JSON object containing the authenticated user's information as returned by the FireFly III API endpoint /about/user. This typically includes user profile details such as username, email, roles, preferences, and other metadata related to the authenticated session.

No binary data is produced by this operation.

Example output structure (simplified):

{
  "id": "user-id",
  "username": "user123",
  "email": "[email protected]",
  "roles": ["admin", "user"],
  "preferences": {
    "language": "en",
    "timezone": "UTC"
  }
}

Dependencies

  • Requires an active connection to a FireFly III instance with valid API credentials (OAuth2 token or equivalent).
  • The node depends on the FireFly III API being accessible and properly configured.
  • No additional external services are required beyond the FireFly III API.
  • The node expects the user to provide any necessary authentication tokens via n8n credentials configuration.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials leading to authentication errors.
    • Network connectivity problems preventing access to the FireFly III API.
    • Incorrect API base URL or misconfigured FireFly III instance.
  • Error messages and resolutions:

    • 401 Unauthorized: Check that the API credentials are correct and have not expired.
    • 404 Not Found when calling /about/user: Verify the FireFly III API version supports this endpoint and the base URL is correct.
    • Timeouts or network errors: Ensure the FireFly III server is reachable from the n8n environment.
  • To debug requests, use the optional X-Trace-ID property to provide a unique UUID for tracing logs on the FireFly III server side.

Links and References

Discussion