Relacio - WhatsApp icon

Relacio - WhatsApp

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

Actions58

Overview

This node integrates with a WhatsApp-based customer relationship platform called "Relacio." It provides various operations to interact with contacts, protocols (support tickets or cases), messages, groups, marketing campaigns, and other related entities within the platform.

Specifically, the operation "Protocolo - Mensagem - Listar" (List Messages by Protocol) retrieves all messages associated with a given protocol number. This is useful for scenarios where you want to fetch the conversation history or message log tied to a specific support ticket or customer interaction protocol.

Practical examples include:

  • Fetching all messages exchanged in a particular customer support case.
  • Auditing communication history for compliance or quality assurance.
  • Displaying message threads in custom dashboards or reports.

Properties

Name Meaning
ID Do Protocolo The protocol number of the customer service case whose messages you want to retrieve. This is required.

Output

The node outputs JSON data containing the list of messages linked to the specified protocol number. Each item in the output array represents a message with details such as sender, timestamp, content, and possibly metadata related to the message.

If the platform supports binary data (e.g., images or attachments in messages), those would be included in the output's binary field, representing the actual media content.

Dependencies

  • Requires an API key credential to authenticate with the Relacio WhatsApp platform.
  • The node depends on the external Relacio API endpoints to perform actions like fetching messages by protocol.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid protocol number: Since the protocol ID is required, ensure it is provided and correctly formatted. Errors may occur if this parameter is empty or incorrect.
  • Authentication errors: If the API key or credentials are missing or invalid, the node will fail to connect. Verify that the API credentials are set up properly in n8n.
  • API rate limits or downtime: The external platform might throttle requests or be temporarily unavailable. Retry after some time or check the platform status.
  • Unexpected response structure: If the platform changes its API, the node might not parse responses correctly. Updating the node or checking for updates from the provider may help.

Links and References

Discussion