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 resource and the Excluir (delete) operation, it allows users to delete a WhatsApp connection by its ID.
Common scenarios where this node is beneficial include automating the management of WhatsApp connections within a customer support or communication platform, such as:
- Removing obsolete or inactive WhatsApp connections.
- Cleaning up WhatsApp integrations programmatically.
- Managing multiple WhatsApp connections dynamically based on business rules.
For example, you might use this node to delete a WhatsApp connection when it is no longer needed or if it was created erroneously.
Properties
| Name | Meaning |
|---|---|
| ID do WhatsApp | The unique identifier of the WhatsApp connection to be deleted. Required for deletion. |
Output
The output is a JSON array containing the response from the Press Ticket® API after attempting to delete the specified WhatsApp connection. The structure typically includes confirmation of deletion or error details if the operation failed.
Example output JSON snippet on success:
{
"success": true,
"message": "WhatsApp connection deleted successfully"
}
If an error occurs, the output will contain an error message describing the issue.
Dependencies
- Requires an active connection to the Press Ticket® API.
- Requires an API token credential configured in n8n for authentication.
- The node uses HTTP requests to the Press Ticket® API endpoints.
- The base URL and API token are retrieved from the configured credentials.
Troubleshooting
Common issues:
- Invalid or missing WhatsApp connection ID will cause the API to return an error.
- Incorrect or expired API token will result in authentication errors.
- Network connectivity problems can cause request failures.
Error messages and resolutions:
"Invalid WhatsApp ID": Verify that the provided WhatsApp ID exists and is correct."Authentication failed": Check that the API token credential is valid and has not expired."Request failed"or timeout errors: Ensure network connectivity and that the Press Ticket® API service is reachable.
To handle errors gracefully, enable the "Continue On Fail" option in the node settings to allow workflow execution to proceed even if deletion fails.
Links and References
- Press Ticket® API Documentation (example placeholder, replace with actual URL if available)
- n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)
- General n8n documentation on Credentials
Note: This summary focuses exclusively on the WhatsApp resource with the Excluir (delete) operation as requested.