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 sessions among other resources. Specifically, for the "Sessão WhatsApp" resource and the "Excluir" (Delete) operation, it deletes a WhatsApp session identified by its session ID.
Common scenarios where this node is useful include automating the management of WhatsApp sessions in customer support or communication platforms, such as removing obsolete or inactive WhatsApp sessions programmatically.
Practical example: Automatically deleting a WhatsApp session when a user logs out or when a session expires, helping maintain clean session data and avoid stale connections.
Properties
| Name | Meaning |
|---|---|
| ID do WhatsApp | The identifier of the WhatsApp connection associated with the session. |
| ID da Sessão WhatsApp | The unique identifier of the WhatsApp session to be deleted. |
Output
The output is a JSON array containing the response from the Press Ticket® API after attempting to delete the specified WhatsApp session. Typically, this will include confirmation of deletion or an error message if the operation failed.
Example output structure:
[
{
"success": true,
"message": "WhatsApp session deleted successfully",
// ...additional fields depending on API response
}
]
If the deletion fails, the output will contain an error description.
Dependencies
- Requires an API key credential for authenticating with the Press Ticket® API.
- The node uses the base URL and token from these credentials to make HTTP requests.
- No additional external dependencies are required beyond the configured API access.
Troubleshooting
Common issues:
- Invalid or missing WhatsApp session ID or WhatsApp connection ID.
- Authentication failures due to incorrect or expired API tokens.
- Network connectivity problems preventing access to the Press Ticket® API.
Error messages:
- If the session ID does not exist, the API may return a 404 or similar error indicating the session was not found.
- Authentication errors will typically indicate invalid credentials; verify the API token configuration.
- If the node throws an error about missing parameters, ensure both IDs are provided and correctly formatted.
Resolution tips:
- Double-check that the WhatsApp session ID and WhatsApp connection ID are correct.
- Verify that the API key credential is valid and has necessary permissions.
- Ensure network access to the API endpoint is available from the n8n environment.
Links and References
- Press Ticket® API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes