Actions41
- Склады Продавца Actions
- Остатки На Складах Продавца Actions
- Категории Предметы И Характеристики Actions
- Создание Карточек Товаров Actions
- Карточки Товаров Actions
- Медиафайлы Actions
- Ярлыки Actions
- Цены И Скидки Actions
Overview
This node operation updates (patches) an existing tag by its numeric ID. It allows modifying the tag's name and color properties. This is useful in scenarios where you want to rename a tag or change its visual color coding without creating a new tag, such as updating labels for categorization or status tracking in an application.
Practical examples:
- Changing the label "Sale" to "Discount" with a new color to reflect updated marketing campaigns.
- Adjusting the color of a tag to improve UI clarity or accessibility.
Properties
| Name | Meaning |
|---|---|
| Id | Numeric ID of the tag to update. |
| Color | Color code of the tag, represented as a string (e.g., hex color code like "D1CFD7"). |
| Name | Name of the tag, a string representing the label's display name (e.g., "Sale"). |
Output
The node outputs JSON data representing the updated tag object after the patch operation. This typically includes the tag's ID, updated name, and color fields reflecting the changes made.
No binary data output is involved.
Dependencies
- Requires an API key credential for authentication with the external service managing tags.
- The node uses a base URL configured from an OpenAPI specification bundled within the node.
- HTTP headers include
Accept: application/jsonandContent-Type: application/json.
Troubleshooting
Common issues:
- Providing an invalid or non-existent tag ID will likely result in an error indicating the tag was not found.
- Incorrect color format may cause the API to reject the request.
- Missing required property "Id" will prevent execution.
Error messages:
- "Tag not found" or similar indicates the specified ID does not exist.
- Validation errors on "color" or "name" indicate improper input formatting.
Resolutions:
- Verify the tag ID exists before attempting to patch.
- Use valid color codes (e.g., hexadecimal strings).
- Ensure all required fields are provided.
Links and References
- No direct external links available from the source code.
- Refer to the external API documentation for tag management for detailed field formats and constraints.