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 Contato (Contact) resource with the Excluir (Delete) operation, it allows users to delete a contact by its ID.
Common scenarios where this node is beneficial include automating customer relationship management tasks, such as removing outdated or incorrect contact records from the system. For example, when a contact unsubscribes or requests data removal, this node can be used in an automation workflow to delete that contact from the Press Ticket® platform.
Properties
| Name | Meaning |
|---|---|
| ID do Contato | The unique identifier of the contact to be deleted |
Output
The output is a JSON array containing the response from the Press Ticket® API after attempting to delete the specified contact. Typically, this will include confirmation of deletion or details about any error encountered.
Example output structure:
[
{
"success": true,
"message": "Contact deleted successfully",
// ... other possible response fields
}
]
If the deletion fails, the output will contain an error message describing the issue.
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
Common issues:
- Invalid or missing contact ID: Ensure the "ID do Contato" property is correctly set and corresponds to an existing contact.
- Authentication errors: Verify that the API token credential is valid and has sufficient permissions.
- Network connectivity problems: Confirm that the n8n instance can reach the Press Ticket® API URL.
Error messages:
"Formato de resposta inválido ao listar contatos": Indicates unexpected API response format; check API availability and version compatibility.- Errors returned from the API during deletion will be passed through; review the error message for specifics (e.g., contact not found).
To handle errors gracefully, enable the "Continue On Fail" option in the node settings to allow workflows to proceed even if deletion fails.
Links and References
- Press Ticket® Official Website (for general product info)
- Press Ticket® API documentation (not publicly linked here; consult your API provider for access)