Clientes Online - WhatsApp
Actions59
- Acesso - Credenciais
- Canais - Listar
- Contato - Adicionar Etiqueta
- Contato - Adicionar Informações
- Contato - Consultar
- Contato - Editar Perfil
- Contato - Encaminhar
- Contato - Importar
- Contato - Importar - Lote
- 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/TSV - 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 "Clientes Online - WhatsApp" integrates with a WhatsApp-based customer relationship platform to perform various operations related to contacts, protocols (support tickets), messaging, groups, marketing campaigns, and more.
Specifically, the Protocolo - Pesquisar (Protocol - Search) operation allows users to search for support protocols (tickets) using different filters such as contact information, status, date ranges, assigned operators, departments, or tags. This is useful for retrieving relevant protocol data for reporting, monitoring, or further processing in automated workflows.
Practical examples:
- Retrieve all open protocols assigned to a specific operator.
- Search protocols linked to a particular contact by name or number.
- Find protocols created within a certain date range.
- Filter protocols by department or tag to analyze workload distribution.
Properties
| Name | Meaning |
|---|---|
| Paginação (page) | Page number for paginated protocol search results. |
| Filtros (filter) | Selects the filter type to apply on the protocol search. Options: |
| - Protocolos De Auto Atendimento (Self-service protocols) | |
| - Protocolos Com Filtros De Contatos (Protocols filtered by contacts) | |
| - Protocolos Com Status (Abertos Ou Fechados) (Protocols filtered by open/closed status) | |
| - Protocolos De Atendimentos Abandonados (Abandoned service protocols) | |
| - Protocolos Durante Um Período (Protocols during a period) | |
| - Protocolos Vinculados A Um Atendente (Protocols linked to an operator) | |
| - Protocolos Vinculados A Um Departamento (Protocols linked to a department) | |
| - Protocolos Vinculados A Uma Etiqueta (Protocols linked to a tag) | |
| - Protocolos Não Atendidos (Unattended protocols) | |
| Nome Ou Número Do Contato (search) | Contact name or number used to search protocols (only shown when filter = 3). |
| Protocolos Abertos (open) | Boolean indicating whether to filter protocols that are open (only shown when filter = 4). |
| Relacionamentos Humanizado (att) | Boolean indicating if the protocol is operational service or self-service (only when filter=4). |
| Data Inicial (start_at) | Start date (YYYY-MM-DD) for filtering protocols by creation date (only when filter = 7). |
| Data Final (finish_at) | End date (YYYY-MM-DD) for filtering protocols by creation date (only when filter = 7). |
| Identificador Do Operador (operator) | Operator identifier to filter protocols assigned to a specific operator (only when filter=8). |
| Identificador Do Setor (department) | Department identifier to filter protocols linked to a department (only when filter=9). |
| Identificador Da Etiqueta (tag) | Tag identifier to filter protocols linked to a specific tag (only when filter=10). |
Output
The node outputs JSON data representing the list of protocols matching the search criteria. Each item typically contains protocol details such as protocol ID, status, associated contact info, timestamps, assigned operator or department, tags, and other metadata relevant to the protocol.
If the node supports binary data output (not indicated here), it would represent attachments or media related to protocols, but this operation primarily returns structured JSON data about protocols.
Dependencies
- Requires an API key credential to authenticate with the Clientes.Online WhatsApp platform.
- The node depends on the external Clientes.Online API service to fetch protocol data.
- Proper configuration of the API credentials in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect filter values or missing required parameters for certain filters may result in empty responses or errors.
- Pagination parameters out of range might return no data.
Error messages:
- Authentication errors indicate invalid or expired API keys; reconfigure credentials.
- Parameter validation errors suggest missing or incompatible input properties; verify property values especially those conditional on the selected filter.
- Network or API downtime errors require checking connectivity and API service status.
Links and References
- Clientes.Online Official Website (general reference)
- Documentation for the Clientes.Online API (if available, consult for detailed protocol search parameters and response structure)
- n8n documentation on creating and configuring API credential nodes