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 to manage categories within a user's financial data. Specifically, the "Delete Category" operation allows users to remove a category by its unique identifier. This is useful for cleaning up unused or obsolete categories in budgeting and expense tracking workflows.
Common scenarios include:
- Automating cleanup of categories that are no longer relevant.
- Integrating category management into larger financial automation workflows.
- Maintaining an organized set of categories by programmatically deleting unwanted entries.
Example: Automatically delete a category after archiving all transactions associated with it.
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. |
Category ID | The unique identifier of the category to delete. This is required to specify which category will be removed. |
Output
The output JSON contains the response from the FireFly III API after attempting to delete the specified category. Typically, this will be an empty object or confirmation message indicating successful deletion.
No binary data is produced by this operation.
Example output JSON:
{}
Dependencies
- Requires an active connection to the FireFly III API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node uses HTTP DELETE method on the endpoint
/categories/{categoryId}
.
Troubleshooting
- Category Not Found: If the provided Category ID does not exist, the API may return a 404 error. Verify the ID is correct.
- Authentication Errors: Ensure the API key or OAuth2 token is valid and has permissions to delete categories.
- Network Issues: Connectivity problems can cause request failures; check network access to the FireFly III server.
- Invalid UUID for X-Trace-ID: If provided, ensure the X-Trace-ID is a valid UUID format to avoid request rejection.