Relacio - WhatsApp icon

Relacio - WhatsApp

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

Actions58

Overview

This node integrates with the "Relacio - WhatsApp" platform, enabling interaction with various WhatsApp-related services and contact management features. Specifically, the "Recados - Pesquisar" operation allows users to search for a message or note ("recado") by its protocol identifier within the inbox system of the platform.

Common scenarios where this node is beneficial include:

  • Retrieving detailed information about a specific message or note using its unique protocol number.
  • Automating workflows that require fetching message status or content based on protocol references.
  • Integrating WhatsApp communication data into broader automation pipelines for customer support or marketing.

For example, a user can input a protocol number to fetch the corresponding message details from the inbox, which can then be used to trigger follow-up actions or logging.

Properties

Name Meaning
Protocolo The protocol number of the message/note ("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/note associated with the provided protocol. The exact structure depends on the platform's API response but typically includes fields such as message content, sender information, timestamps, status, and any related metadata.

If the node supports binary data output (not explicitly shown in the provided code), it would represent attachments or media related to the message.

Dependencies

  • Requires an API key credential for authenticating with the Relacio WhatsApp platform.
  • The node depends on the external "Relacio - WhatsApp" service API to perform operations.
  • Proper configuration of the API authentication token or credentials within n8n is necessary.

Troubleshooting

  • Missing or invalid protocol: If the "Protocolo" property is empty or incorrect, the node will likely fail to retrieve the message. Ensure the protocol number is accurate and exists in the system.
  • Authentication errors: Failure to authenticate with the external API due to missing or invalid credentials will prevent the node from executing successfully. Verify that the API key or authentication token is correctly set up.
  • Network issues: Connectivity problems between n8n and the external service can cause timeouts or errors. Check network settings and service availability.
  • Unexpected API responses: Changes in the external API or unexpected data formats might cause parsing errors. Review API documentation and update the node if needed.

Links and References

Discussion