Actions34
- Activity Actions
- Deal Actions
- Funnel Actions
- Organization Actions
- Person Actions
- Product Actions
- Tag Actions
- User Actions
Overview
This node allows you to create a new tag in the Agendor CRM system. Tags are useful for categorizing and organizing items such as products, contacts, or deals within your CRM. By creating tags, you can easily filter, group, and manage related records.
Common scenarios:
- Adding a new category or label to classify products or services.
- Creating color-coded tags to visually distinguish different types of entries.
- Organizing CRM data by tagging contacts, deals, or activities for better segmentation.
Practical example:
You want to add a tag named "Software de CRM" with a specific color to identify all software-related products in your catalog. This node will send the necessary data to Agendor's API to create that tag.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the tag to be created (e.g., "Software de CRM"). |
| Color | The color of the tag in hexadecimal format (e.g., "#000000" for black). |
| Additional Fields | Not applicable for Tag creation operation (present in other resources but not used here). |
Output
The node outputs JSON data representing the newly created tag object returned from the Agendor API. This typically includes fields such as the tag's unique ID, name, color, creation timestamp, and any other metadata provided by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Agendor CRM API.
- The node sends HTTP POST requests to
https://api.agendor.com.br/v3/tagsendpoint. - Proper configuration of the API token in n8n credentials is necessary.
Troubleshooting
- Missing or invalid API token: The request will fail authentication. Ensure the API key credential is correctly set up and valid.
- Required field "Name" missing: The API will reject the request if the tag name is empty. Always provide a non-empty string for the tag name.
- Invalid color format: The color must be a valid hexadecimal string (e.g., "#FF0000"). Invalid formats may cause errors or default to black.
- API rate limits or connectivity issues: Network problems or hitting API limits can cause failures. Check network connectivity and API usage quotas.
Links and References
- Agendor API Documentation — Official API docs for reference on tags and other resources.
- n8n Documentation — For general guidance on using and configuring nodes and credentials.