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
This node interacts with the "Clientes Online - WhatsApp" platform, providing various operations related to customer relationship management via WhatsApp. Specifically, the operation "Protocolo - Observações - Listar" (List Protocol Observations) retrieves observations or notes associated with a specific service protocol number.
Use cases include:
- Fetching all notes or comments linked to a particular customer support protocol.
- Monitoring and auditing communication history for a given protocol.
- Integrating protocol observation data into automated workflows for reporting or follow-up actions.
For example, a support team could use this node to automatically gather all observations made on a customer's support ticket and send a summary report.
Properties
| Name | Meaning |
|---|---|
| ID Do Protocolo | The unique identifier (protocol number) of the service protocol whose observations are to be retrieved. This is a required string input. |
Output
The node outputs JSON data containing the list of observations associated with the specified protocol. Each item in the output typically represents an individual observation or note linked to that protocol.
The exact structure depends on the API response but generally includes fields such as observation text, timestamps, author information, and possibly status or type of observation.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Clientes Online platform.
- The node depends on the external Clientes Online WhatsApp platform API to fetch protocol observations.
- Proper configuration of the API credentials within n8n is necessary for successful execution.
Troubleshooting
- Missing or invalid protocol ID: If the "ID Do Protocolo" property is empty or incorrect, the node will likely fail to retrieve observations. Ensure the protocol number is valid and correctly entered.
- Authentication errors: Failure to authenticate with the Clientes Online API due to missing or invalid API credentials will cause errors. Verify that the API key credential is properly set up.
- API rate limits or downtime: If the external service is unavailable or rate-limited, the node may throw errors or return empty results. Check the service status and retry later.
- Unexpected response format: Changes in the external API might cause parsing issues. Review error messages and update the node or credentials accordingly.
Links and References
- Clientes Online Platform Documentation (example placeholder, replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General info on WhatsApp Business API integration and CRM workflows.