Actions45
- General Actions
- About API Actions
- Accounts API Actions
- Transactions API Actions
- Categories API Actions
- Tags API Actions
- Rules & Groups API Actions
Overview
This node integrates with the FireFly III API, a personal finance manager, to perform various operations on financial data. Specifically, for the Accounts API resource and the Delete Account operation, the node deletes an account identified by its unique ID from the user's FireFly III instance.
Common scenarios where this node is beneficial include:
- Automating cleanup of obsolete or closed accounts in your financial system.
- Integrating account management workflows where accounts need to be programmatically removed based on external triggers or conditions.
- Maintaining synchronization between FireFly III and other financial tools by removing accounts that no longer exist elsewhere.
Example use case:
- A user wants to delete an account after it has been closed in their bank system. This node can be used in an automation workflow to remove that account from FireFly III automatically by providing the account's ID.
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 in logs. |
Account ID | The unique identifier of the account to delete. This is a required string input. |
Output
The output of the node is a JSON object representing the response from the FireFly III API after attempting to delete the specified account. Typically, this will contain confirmation of deletion or any relevant status messages returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to a FireFly III instance via an API key or OAuth2 authentication token configured in n8n credentials.
- The node uses the FireFly III REST API endpoints; thus, the FireFly III server must be accessible from the environment where n8n runs.
- Proper permissions are needed on the API token to allow deleting accounts.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Account ID will likely result in an error response from the API.
- Insufficient permissions on the API token may cause authorization errors.
- Network connectivity issues to the FireFly III server will prevent the request from completing.
Error messages and resolutions:
- 404 Not Found: The specified Account ID does not exist. Verify the ID is correct.
- 401 Unauthorized or 403 Forbidden: The API token lacks permission to delete accounts. Check credential scopes and permissions.
- 400 Bad Request: The request parameters might be malformed. Ensure the Account ID is correctly formatted.
- Timeouts or network errors: Confirm the FireFly III server URL is reachable and there are no firewall restrictions.