SacNews - Relacionamento icon

SacNews - Relacionamento

Interação com a Plataforma de Relacionamento via WhatsApp - SacNews

Actions59

Overview

The node "SacNews - Relacionamento" integrates with a customer relationship platform via WhatsApp, enabling various operations related to contacts, protocols, messages, tags, groups, marketing campaigns, and extra data lookups. Specifically, the Protocolo - Pesquisar (Protocol - Search) operation allows users to search for communication protocols using different filters such as contact info, status, date ranges, assigned operators, departments, or tags.

This node is beneficial in scenarios where businesses want to automate or streamline their customer support workflows by programmatically querying protocol records from their WhatsApp-based CRM system. For example, a support team could use it to retrieve all open protocols assigned to a particular operator or find protocols linked to specific contact details within a given time frame.

Properties

Name Meaning
Paginação (page) Page number for paginated protocol search results.
Filtros (filter) Filter type to apply on the protocol search. Options:
- Protocolos De Auto Atendimento
- Protocolos Com Filtros De Contatos
- Protocolos Com Status (Abertos Ou Fechados)
- Protocolos De Atendimentos Abandonados
- Protocolos Durante Um Período
- Protocolos Vinculados A Um Atendente
- Protocolos Vinculados A Um Departamento
- Protocolos Vinculados A Uma Etiqueta
- Protocolos Não Atendidos
Nome Ou Número Do Contato (search) Contact name or number used to filter protocols (only shown when filter = Protocolos Com Filtros De Contatos).
Protocolos Abertos (open) Boolean indicating whether to filter protocols that are open (only shown when filter = Protocolos Com Status).
Relacionamentos Humanizado (att) Boolean indicating if the protocol is operational or self-service (only shown when filter = Protocolos Com Status).
Data Inicial (start_at) Start date (YYYY-MM-DD) for filtering protocols during a period (only shown when filter = Protocolos Durante Um Período).
Data Final (finish_at) End date (YYYY-MM-DD) for filtering protocols during a period (only shown when filter = Protocolos Durante Um Período).
Identificador Do Operador (operator) Operator identifier to filter protocols linked to a specific operator (only shown when filter = Protocolos Vinculados A Um Atendente).
Identificador Do Setor (department) Department identifier to filter protocols linked to a specific department (only shown when filter = Protocolos Vinculados A Um Departamento).
Identificador Da Etiqueta (tag) Tag identifier to filter protocols linked to a specific tag (only shown when filter = Protocolos Vinculados A Uma Etiqueta).

Output

The node outputs JSON data representing the list of protocols matching the search criteria. The structure typically includes protocol metadata such as protocol IDs, statuses, timestamps, associated contacts, operators, departments, tags, and other relevant details returned by the platform's API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the external customer relationship platform via WhatsApp.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • The node depends on internal action modules (imported as a in the source) which implement the actual API calls for each operation.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Using incompatible filter options or missing required parameters for certain filters may result in empty results or errors.
    • Pagination parameters out of range might return no data.
  • Error Messages:

    • Authentication errors usually indicate invalid or expired API keys; reconfigure credentials.
    • Validation errors may occur if required fields for a selected filter are not provided; ensure all necessary inputs are set.
    • Network or timeout errors suggest connectivity issues with the external platform; verify network access and API availability.

Links and References

  • No direct external links were found in the source code.
  • Users should refer to the official documentation of the integrated customer relationship platform for detailed API usage and protocol definitions.

Discussion