Actions58
- Acesso - Credenciais
- Canais - Listar
- Contato - Adicionar Etiqueta
- Contato - Adicionar Informações
- Contato - Consultar
- Contato - Editar Perfil
- Contato - Encaminhar
- Contato - Importar
- Contato - Listar Protocolos
- Contato - Listar Todos
- Contato - Mensagem - Enviar
- Contato - Mensagem - Enviar Imagem + Legenda
- Contato - Pesquisar
- Contato - Remover Etiqueta
- Contato - Status De WhatsApp
- Etiquetas - Listar Todos
- Extra - Cep - Pesquisar
- Extra - Cnpj - Pesquisar
- Extra - Coordenadas - Pesquisar
- Extra - Cpf - Pesquisar
- Extra - CSV - Formatar
- Extra - Nome - Pesquisar
- Extra - Titularidade - Pesquisar
- Extra - Transcrição - Documentos
- Extra - Transcrição - Imagem EN
- Extra - Transcrição - Imagem PT
- Grupos - Adicionar Contato
- Grupos - Listar Contatos
- Grupos - Listar Todos
- Grupos - Remover Contato
- Grupos - WhatsApp - Histórico
- Grupos - WhatsApp - Listar
- Grupos - WhatsApp - Membros
- Marketing - Campanha - Listar
- Marketing - Campanha - Resumo
- Marketing - Mensagem - Enviar
- Marketing - Mensagem - Listar
- Marketing - Mensagem - Status
- Produto - Categoria - Listar
- Produto - Listar
- Protocolo - Consultar
- Protocolo - Encaminhar - Recado
- Protocolo - Finalizar
- Protocolo - Listar - Todos
- Protocolo - Mensagem - Enviar
- Protocolo - Mensagem - Listar
- Protocolo - Observações - Adicionar
- Protocolo - Observações - Listar
- Protocolo - Pesquisar
- Recados - Listar - Todos
- Recados - Pesquisar
- Setor - Listar - Todos
- Templates - Listar - Todos
- Usuário - Agenda - Listar
- Usuário - Carteira - Adicionar
- Usuário - Carteira - Listar
- Usuário - Carteira - Remover
- Usuário - Listar - Todos
Overview
The node provides an integration with a WhatsApp-based customer relationship platform, enabling various operations related to contacts, protocols (support tickets), messaging, groups, marketing campaigns, and more. Specifically, the "Protocolo - Finalizar" (Protocol - Finish) operation allows users to finalize or close a customer support protocol (ticket). This is useful in scenarios where a support interaction or service request has been completed and needs to be marked as finished in the system.
Practical examples:
- Automatically closing a customer support ticket after issue resolution.
- Notifying the customer via WhatsApp that their support request has been closed.
- Integrating with workflows that track the lifecycle of customer interactions.
Properties
| Name | Meaning |
|---|---|
| ID Do Protocolo | The unique identifier (number) of the support protocol (ticket) to be finalized. |
| Notificar O Contato | Boolean flag indicating whether to notify the contact about the protocol closure. |
| Texto De Notificação | The notification text message to send to the contact upon protocol closure. Supports variables like %PROTOCOLO%. |
| Aviso | Informational notice warning that this action will finalize the protocol and should be used carefully. |
Output
The node outputs JSON data representing the result of the protocol finalization operation. This typically includes confirmation details such as the protocol ID, status update, and any messages returned by the platform API. The output does not explicitly mention binary data, so it is assumed to be purely JSON structured.
Dependencies
- Requires an API key credential for authenticating with the external WhatsApp customer relationship platform.
- The node depends on internal action modules that implement the actual API calls for each operation.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common issues:
- Providing an incorrect or non-existent protocol ID will likely cause the operation to fail.
- If notification is enabled but the notification text is empty or malformed, the message may not be sent.
- Network or authentication errors can occur if the API key credential is missing or invalid.
Error messages:
- Errors related to "protocol not found" indicate the specified protocol ID does not exist.
- Authentication errors suggest problems with the provided API key or credentials.
- Validation errors may arise if required parameters like protocol ID are missing.
Resolutions:
- Verify the protocol ID before attempting to finalize.
- Ensure the API key credential is correctly configured and valid.
- Provide meaningful notification text if notifications are enabled.
Links and References
- No direct external links were found in the source code.
- For further information, consult the documentation of the integrated WhatsApp customer relationship platform or the n8n community forums for usage examples of this node.