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 to manage tags within a user's financial data. Specifically, the "Delete Tag" operation allows users to remove a tag by specifying its name or ID. This is useful for cleaning up unused or obsolete tags that categorize transactions or other entities in FireFly III.

Common scenarios include:

  • Automating tag cleanup workflows.
  • Removing tags that are no longer relevant after data restructuring.
  • Managing tags programmatically as part of larger financial automation processes.

Example: Automatically delete a tag named "Old Expenses" when it is no longer needed to keep the tagging system tidy.

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.
Target Tag Name/ID The name or ID of the tag to delete. This value is required and used directly in the API path. Note: Using tag names with international (non-ASCII) characters may cause issues.

Output

The output JSON contains the response from the FireFly III API after attempting to delete the specified tag. 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 standard HTTP DELETE requests to the /tags/{tagNameId} endpoint.

Troubleshooting

  • Issue: Deletion fails with a 404 error.

    • Cause: The specified tag name or ID does not exist.
    • Resolution: Verify the tag name/ID is correct and exists in FireFly III.
  • Issue: Deletion fails with a 401 or 403 error.

    • Cause: Authentication failure or insufficient permissions.
    • Resolution: Check API credentials and ensure the token has permission to delete tags.
  • Issue: Problems deleting tags with non-ASCII characters.

    • Cause: Encoding issues in the API path.
    • Resolution: Use tag IDs instead of names when possible to avoid encoding problems.
  • General: Use the optional X-Trace-ID property to help trace and debug requests if supported by the API server.

Links and References

Discussion