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 WhatsApp connections and other related resources such as messages, contacts, tickets, queues, tags, and WhatsApp sessions. Specifically for the WhatsApp - Obter (Get) operation, it retrieves detailed information about a specific WhatsApp connection by its ID.
Common scenarios where this node is beneficial include:
- Fetching the status and details of a particular WhatsApp connection in your customer support or communication system.
- Monitoring and managing multiple WhatsApp connections programmatically.
- Integrating WhatsApp connection data into automated workflows for reporting or operational purposes.
Practical example:
- You have several WhatsApp connections set up for different departments. Using this node, you can retrieve the current status and configuration of a specific WhatsApp connection by providing its ID, enabling dynamic decision-making in your workflow based on connection state.
Properties
| Name | Meaning |
|---|---|
| ID do WhatsApp | The unique identifier of the WhatsApp connection to retrieve details for. |
Output
The output is a JSON array containing the details of the requested WhatsApp connection. The structure typically includes fields such as connection ID, name, status, whether it is the default connection, and possibly other metadata returned by the Press Ticket® API.
Example output JSON snippet:
{
"id": "123",
"name": "Support WhatsApp Connection",
"status": "CONNECTED",
"isDefault": true,
...
}
No binary data output is involved in this operation.
Dependencies
- Requires an active API key credential for the Press Ticket® API.
- The node uses the Press Ticket® API base URL and token configured in the credentials.
- Network access to the Press Ticket® API endpoints is necessary.
Troubleshooting
- Invalid or missing WhatsApp ID: Ensure that the "ID do WhatsApp" property is correctly provided and corresponds to an existing WhatsApp connection.
- Authentication errors: Verify that the API token credential is valid and has sufficient permissions.
- API connectivity issues: Check network connectivity and the availability of the Press Ticket® API service.
- Unexpected response format: If the API response does not match expected formats, confirm that the API version and endpoint are correct and that the Press Ticket® service is functioning properly.
If the node throws errors related to request failures, inspect the error message for HTTP status codes or API error details to guide resolution.
Links and References
- Press Ticket® Official Website
- Press Ticket® API Documentation (Assumed location; verify actual docs URL)
- n8n Documentation on Creating Custom Nodes