Relacio - WhatsApp icon

Relacio - WhatsApp

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

Actions58

Overview

The node "Relacio - WhatsApp" integrates with a WhatsApp-based customer relationship platform called Relacio. Specifically, the operation Protocolo - Pesquisar (searchProtocol) allows users to search for communication protocols (tickets or cases) within the platform using various filters and pagination.

This node is useful in scenarios where you want to programmatically retrieve protocol data from the Relacio platform based on specific criteria such as contact information, status, date ranges, assigned operators, departments, or tags. For example, a support team could use this node to fetch all open protocols assigned to a particular operator or all protocols related to a certain contact.

Properties

Name Meaning
Paginação (page) Page number for paginated protocol search results.
Filtros (filter) Filter type to apply when searching protocols. 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 date range)
- 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 to search for (only shown if filter = Protocolos Com Filtros De Contatos).
Protocolos Abertos (open) Boolean indicating whether to filter protocols that are open (only shown if filter = Protocolos Com Status).
Relacionamentos Humanizado (att) Boolean indicating whether to filter operational vs self-service protocols (only shown if filter = Protocolos Com Status).
Data Inicial (start_at) Start date (YYYY-MM-DD) for filtering protocols during a period (only shown if filter = Protocolos Durante Um Período).
Data Final (finish_at) End date (YYYY-MM-DD) for filtering protocols during a period (only shown if filter = Protocolos Durante Um Período).
Identificador Do Operador (operator) Operator identifier to filter protocols linked to a specific operator (only shown if filter = Protocolos Vinculados A Um Atendente).
Identificador Do Setor (department) Department identifier to filter protocols linked to a specific department (only shown if filter = Protocolos Vinculados A Um Departamento).
Identificador Da Etiqueta (tag) Tag identifier to filter protocols linked to a specific tag (only shown if filter = Protocolos Vinculados A Uma Etiqueta).

Output

The output of the node is an array of JSON objects representing the protocols matching the search criteria. Each object contains details about a protocol such as its ID, status, associated contact, timestamps, assigned operator or department, tags, and other metadata relevant to the protocol's lifecycle and context within the Relacio platform.

The exact structure depends on the API response from the Relacio platform but generally includes:

  • Protocol identifiers
  • Contact information
  • Status flags (open/closed)
  • Assignment details (operator, department)
  • Tags and labels
  • Timestamps (creation, update, etc.)

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Relacio platform via an API key credential configured in n8n.
  • The node depends on the external Relacio API endpoints to perform protocol searches.
  • Proper API credentials must be set up in n8n to authenticate requests.

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 results.
    • Date format errors for start_at and finish_at fields can cause request failures.

  • Error messages:

    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • Validation errors may occur if required parameters for a selected filter are not provided; ensure all necessary inputs are filled.
    • Network or timeout errors suggest connectivity issues with the Relacio API; check network access and API availability.

Links and References

Discussion