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, specifically focusing on transaction-related operations. The "Delete Split From Transaction" operation allows users to delete a split (a part of a transaction journal) by specifying its ID. This is useful in scenarios where a user needs to remove a particular split from a transaction journal, for example, correcting an erroneous entry or cleaning up transaction data.
Practical examples:
- Removing an incorrect split from a transaction journal after importing bank statements.
- Cleaning up transaction splits that were created by mistake during bulk transaction creation.
- Managing and maintaining accurate financial records by deleting obsolete or duplicate splits.
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). |
| Transaction ID | The ID of the transaction journal or the split ID to be deleted. This is required to identify which split to delete. |
Note: There are also informational notices guiding users to the API documentation and clarifying that the ID should correspond to the transaction journal or split ID.
Output
The output JSON contains the response from the FireFly III API after attempting to delete the specified split from the transaction journal. Typically, this will be an empty object or confirmation message indicating successful deletion.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the FireFly III API.
- Requires an API authentication token configured in n8n credentials (OAuth2 or similar).
- The node uses internal helper functions to make HTTP requests to the FireFly III API endpoints.
Troubleshooting
Common issues:
- Providing an invalid or non-existent transaction/split ID will result in an error from the API.
- Missing or incorrect API authentication credentials will cause authorization failures.
- Network connectivity issues can prevent the node from reaching the FireFly III API.
Error messages:
- 404 Not Found: The specified transaction or split ID does not exist. Verify the ID is correct.
- 401 Unauthorized: Authentication failed. Check that the API key or OAuth token is valid and properly configured.
- 400 Bad Request: The request parameters are invalid. Ensure the transaction ID is provided and correctly formatted.
To resolve errors, verify the input parameters, ensure proper API credentials are set up, and confirm network access to the FireFly III API endpoint.