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 WhatsApp sessions. Specifically for the Tag resource with the Obter (Get) operation, it retrieves detailed information about a specific tag by its ID.
Common scenarios where this node is beneficial include automating customer support workflows, managing contact tags for segmentation, and synchronizing tag data between systems. For example, you can use this node to fetch tag details to apply conditional logic in your workflow or to update UI elements based on tag properties.
Properties
| Name | Meaning |
|---|---|
| ID da Tag | The unique identifier of the tag to retrieve details for. This is a required string input. |
Output
The output is a JSON object representing the details of the requested tag. It typically includes fields such as the tag's ID, name, color (in hexadecimal format), and possibly other metadata returned by the Press Ticket® API.
Example output structure (simplified):
{
"id": "123",
"name": "Important",
"color": "#FF0000"
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Press Ticket® API.
- The node expects the API URL and token to be configured in the credentials.
- Network access to the Press Ticket® API endpoint is necessary.
Troubleshooting
- Invalid or missing tag ID: Ensure that the "ID da Tag" property is provided and corresponds to an existing tag in the system.
- Authentication errors: Verify that the API token credential is correctly set up and has sufficient permissions.
- API response format issues: If the API returns unexpected data, check the API status and version compatibility.
- Network connectivity problems: Confirm that the n8n instance can reach the Press Ticket® API endpoint.
If the node throws an error related to the request, inspect the error message for clues such as HTTP status codes or API error messages to guide resolution.
Links and References
- Press Ticket® API Documentation (example placeholder, replace with actual if available)
- n8n Documentation: Creating Custom Nodes
- General REST API concepts: REST API Tutorial