Clientes Online - WhatsApp icon

Clientes Online - WhatsApp

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

Actions59

Overview

This node integrates with the "Clientes Online - WhatsApp" platform, enabling interaction with its relationship management system via WhatsApp. Specifically, the Protocolo - Consultar operation allows users to query detailed information about a specific protocol (conversation record) identified by its unique protocol number.

Typical use cases include:

  • Retrieving the history or details of a customer support conversation conducted through WhatsApp.
  • Auditing or reviewing interactions linked to a particular protocol number.
  • Automating workflows that depend on fetching protocol data for further processing or reporting.

For example, a customer service automation might use this node to fetch the full conversation history of a given protocol number to analyze customer issues or escalate tickets.

Properties

Name Meaning
ID Do Protocolo The unique identifier number of the protocol (conversation record) in the WhatsApp Relationship Platform. Required to specify which protocol's data to retrieve.

Output

The node outputs JSON data representing the queried protocol's details and history. This typically includes metadata and messages associated with the specified protocol number from the WhatsApp relationship platform.

No binary data output is indicated for this operation.

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 within n8n is necessary for successful execution.

Troubleshooting

  • Common Issues:

    • Missing or invalid protocol number input will cause the operation to fail.
    • Authentication errors if the API key credential is not set up correctly.
    • Network connectivity problems may prevent access to the external API.

  • Error Messages:

    • Errors related to "protocol not found" indicate the provided protocol ID does not exist or is incorrect.
    • Authentication failures suggest checking the API key credential configuration.
    • Timeout or connection errors require verifying network access and API endpoint availability.

Resolving these usually involves verifying input parameters, ensuring valid credentials, and confirming network connectivity.

Links and References

Discussion