Actions10
- Blocklet Actions
- Tag Actions
- User Actions
Overview
This node interacts with a Blocklet Service API to manage tags among other resources. Specifically, the "Update Tag" operation allows users to modify an existing tag's properties such as its title, color, and description by providing the tag's ID. This is useful in scenarios where you want to keep your tagging system up-to-date, for example, renaming tags, changing their color coding for better visual organization, or updating descriptions to reflect new information.
Practical examples:
- Updating a tag's title from "Urgent" to "High Priority".
- Changing the color of a tag to visually distinguish it in a UI.
- Adding or modifying the description of a tag to provide more context.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the tag to update. Optional but usually required to specify which tag to update. |
| Title | The new title/name of the tag. This is a required field when updating a tag. |
| Color | The color associated with the tag, represented as a hex color code (e.g., #4B5563). |
| Description | A textual description providing additional details about the tag. |
Output
The output is a JSON array containing the updated tag object returned from the API. Each item corresponds to one input item processed. The structure typically includes the tag's ID, title, color, description, and possibly other metadata as returned by the Blocklet Service API.
No binary data output is involved in this operation.
Dependencies
- Requires connection to the Blocklet Service API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- Uses internal helper functions to make API requests and handle pagination or sorting if applicable.
Troubleshooting
- Missing or invalid ID: If the tag ID is not provided or incorrect, the API will likely return an error indicating that the tag cannot be found or updated. Ensure the correct tag ID is supplied.
- Required fields missing: The "Title" property is mandatory; omitting it will cause the request to fail.
- API authentication errors: If the API key or token is invalid or expired, the node will throw authentication errors. Verify and update credentials accordingly.
- Network issues: Connectivity problems can cause timeouts or failed requests. Check network access to the Blocklet Service API endpoint.
- Unexpected errors: The node throws descriptive error messages from the API. Use these messages to diagnose issues or enable "Continue On Fail" to process multiple items without stopping on errors.
Links and References
- Blocklet Service API Documentation (example placeholder link)
- n8n Documentation on Creating Custom Nodes
- Color Picker Reference for choosing hex color codes