Clientes Online - WhatsApp icon

Clientes Online - WhatsApp

Interação com a Plataforma de Relacionamento via WhatsApp - Clientes.Online

Actions59

Overview

This node integrates with the "Clientes Online - WhatsApp" platform, enabling interaction with various WhatsApp-related services and data management features. Specifically, the "Recados - Pesquisar" operation allows users to search for a message or note ("recado") by its protocol identifier. This is useful in scenarios where you need to retrieve detailed information about a specific message or communication tracked by a protocol number.

Practical examples include:

  • Fetching the status or content of a customer support message using its protocol.
  • Automating workflows that require looking up message details before taking further actions.
  • Integrating message tracking into broader CRM or helpdesk systems.

Properties

Name Meaning
Protocolo The protocol number of the message ("recado") you want to search for. This is a required string input.

Output

The node outputs JSON data containing the details of the searched message associated with the given protocol. The exact structure depends on the API response from the Clientes Online platform but typically includes fields such as message content, sender/receiver info, timestamps, status, and other metadata related to the protocol.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authentication with the Clientes Online platform.
  • The node depends on the external Clientes Online WhatsApp service API.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing protocol number will likely cause the search to fail or return no results.
    • Authentication errors if the API key credential is not set or invalid.
    • Network connectivity problems may prevent access to the Clientes Online API.
  • Error messages and resolutions:

    • "Authentication failed" — Verify that the API key credential is correctly configured and valid.
    • "Protocol not found" or empty results — Confirm the protocol number entered exists and is correct.
    • Timeout or network errors — Check internet connection and API endpoint availability.

Links and References

Discussion