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 various features of a customer relationship system via WhatsApp. Specifically, the operation "Protocolo - Mensagem - Listar" (List Messages by Protocol) retrieves all messages associated with a given service protocol number.

Use cases include:

  • Fetching the conversation history or message log related to a specific customer support protocol.
  • Auditing or monitoring communication threads linked to a particular service request.
  • Automating workflows that require access to protocol-related messages for further processing or analysis.

For example, a support team could use this node to automatically gather all messages tied to a customer's protocol number and then trigger follow-up actions based on the content or status of those messages.

Properties

Name Meaning
ID Do Protocolo The unique identifier (protocol number) of the service protocol whose messages you want to retrieve. This is a required string input.

Output

The node outputs JSON data containing the list of messages associated with the specified protocol number. Each item in the output typically represents a message record with details such as sender, timestamp, message content, and possibly message status.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential to authenticate with the Clientes Online platform.
  • The node depends on the Clientes Online API being accessible and properly configured within n8n credentials.
  • No additional external services are explicitly required beyond the authenticated API access.

Troubleshooting

  • Common issues:

    • Providing an invalid or empty protocol number will likely result in no messages returned or an error from the API.
    • Network connectivity problems or incorrect API credentials can cause authentication failures.
    • If the protocol number does not exist or has no messages, the output may be empty.

  • Error messages and resolutions:

    • Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
    • "Protocol not found" or similar API errors: Confirm the protocol number is correct and exists in the system.
    • Timeout or network errors: Check internet connection and API endpoint availability.

Links and References

Discussion