Actions34
- Activity Actions
- Deal Actions
- Funnel Actions
- Organization Actions
- Person Actions
- Product Actions
- Tag Actions
- User Actions
Overview
This node operation updates an existing tag in the Agendor CRM system. It allows users to modify the tag's name and color by specifying the tag's unique identifier. This is useful for maintaining organized and visually distinct tags that categorize or label CRM entities such as contacts, deals, or products.
Typical use cases include:
- Renaming a tag to better reflect its purpose.
- Changing the color of a tag to improve visual identification in the CRM interface.
- Automating tag updates based on external triggers or workflows.
For example, you might update a tag named "Prospect" to "Qualified Prospect" and change its color from gray to green after a lead reaches a certain stage.
Properties
| Name | Meaning |
|---|---|
| Tag ID | The unique identifier of the tag to update (required). |
| Name | The new name for the tag. Leave empty to keep the current name unchanged. |
| Color | The new color of the tag in hexadecimal format (e.g., #FF0000 for red). |
Output
The node outputs the updated tag data in JSON format. The output typically includes fields such as the tag's ID, updated name, color, and possibly timestamps or other metadata returned by the API.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Agendor CRM API.
- The node makes HTTP PUT requests to the endpoint
/tags/{tagId}on the Agendor API base URL (https://api.agendor.com.br/v3). - Proper configuration of the API token in n8n credentials is necessary.
Troubleshooting
- Missing or invalid Tag ID: The operation requires a valid tag ID. Ensure the Tag ID field is filled correctly; otherwise, the API will return an error indicating the tag was not found.
- Invalid color format: The color must be a valid hexadecimal string. Invalid formats may cause the API to reject the request.
- Empty name field: Leaving the name empty will not change the tag's name. If you intend to rename the tag, provide a non-empty string.
- Authentication errors: Verify that the API token credential is correctly set up and has sufficient permissions.
- API rate limits or downtime: If requests fail unexpectedly, check the Agendor API status and ensure you are not exceeding rate limits.
Links and References
- Agendor API Documentation (for detailed API endpoints and data models)
- Hex Color Codes (for understanding color formatting)