Actions16
- Contact Actions
- Contact Tagging Actions
- Data Field Actions
- Opt-In Process Actions
- Tag Actions
Overview
The node provides functionality to manage "Tags" within a system, specifically supporting the deletion of tags. The "Delete Tag" operation allows users to remove a tag by specifying its identifier. This is useful in scenarios where tags are used for categorization or segmentation and need to be cleaned up or removed when no longer relevant.
For example, if you have a list of tags assigned to contacts or items and want to delete obsolete or incorrect tags, this operation facilitates that action programmatically within an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Tag | Choose the tag to delete from a dynamically loaded list of existing tags, or specify the tag ID directly using an expression. |
Output
The output structure is not explicitly detailed in the provided source code. However, typically for a "Delete Tag" operation, the output JSON would confirm the success or failure of the deletion request, possibly including the ID of the deleted tag or an error message if the deletion failed.
No binary data output is indicated.
Dependencies
- The node depends on external methods and routing logic imported from bundled dependencies (
./methods,./actions/node.description, and./actions/router). - It requires access to an API or service that manages tags, authenticated via an API key or similar credential (not explicitly named here).
- The property
tagIdoptions are dynamically loaded via a method calledgetTags, indicating a dependency on an API call to fetch available tags.
Troubleshooting
Common issues:
- Specifying an invalid or non-existent tag ID may result in an error or no action.
- Failure to authenticate with the external service will prevent tag deletion.
- Network or API errors could cause the operation to fail.
Error messages:
- Errors related to missing or invalid tag IDs should prompt users to verify the tag exists.
- Authentication errors require checking the configured API credentials.
- General API errors might suggest retrying or checking service status.
Links and References
- n8n Expressions Documentation — for guidance on specifying dynamic values such as tag IDs.
- Relevant API documentation for the external service managing tags (not provided here).