Actions32
- Mensagem Actions
- Contato Actions
- Ticket Actions
- Setor Actions
- Tag Actions
- WhatsApp Actions
- Sessão WhatsApp Actions
Overview
This node integrates with the Press Ticket® API to manage various resources such as messages, contacts, tickets, queues, tags, WhatsApp connections, and sessions. Specifically for the Tag resource with the Create operation, it allows users to create new tags by specifying a name and a color in hexadecimal format.
Common scenarios where this node is beneficial include automating customer support workflows, organizing contacts or tickets with tags, and synchronizing tag data between systems. For example, you can automatically create tags to categorize customer issues or label contacts based on their preferences or status.
Properties
| Name | Meaning |
|---|---|
| Nome | The name of the tag to be created. |
| Cor | The color of the tag in hexadecimal format (e.g., #FF0000 for red). |
Output
The output JSON contains the response from the Press Ticket® API after creating the tag. Typically, this includes details of the newly created tag such as its ID, name, color, and possibly metadata returned by the API.
Example output structure (simplified):
{
"id": 123,
"name": "Urgent",
"color": "#FF0000"
}
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Press Ticket® API.
- The node uses the base URL and token from the configured credentials to make HTTP requests.
- No additional external dependencies are required beyond the API access.
Troubleshooting
- Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
- Invalid color format: The color property must be a valid hexadecimal color string (e.g.,
#000000). Invalid formats may cause API errors. - API connectivity issues: Verify network connectivity to the Press Ticket® API endpoint.
- Error responses from API: The node throws errors if the API returns invalid responses or if required parameters are missing.
If the node fails and "Continue On Fail" is not enabled, execution will stop with the error message. Enabling "Continue On Fail" allows processing subsequent items even if one fails.
Links and References
- Press Ticket® Official Website (for general product info)
- Press Ticket® API documentation (not publicly linked here; refer to your API provider for details)