Relacio - WhatsApp icon

Relacio - WhatsApp

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

Actions58

Overview

This node integrates with a WhatsApp-based customer relationship platform called "Relacio." Specifically, the operation Protocolo - Mensagem - Enviar (Protocol - Message - Send) allows sending various types of messages to a specific service protocol identified by its protocol number. This is useful in scenarios where automated or manual communication needs to be sent within the context of a customer support or service ticketing system.

Typical use cases include:

  • Sending text updates or notifications related to a customer support protocol.
  • Sharing media files such as images, videos, audio, or documents relevant to the ongoing service interaction.
  • Sending contact cards (vCards) or location maps to provide additional information.
  • Enhancing customer engagement by automating message dispatches tied to specific protocols.

For example, a support agent can automatically send a status update text message or an image attachment to a customer's protocol after resolving an issue.

Properties

Name Meaning
ID Do Protocolo The unique protocol number identifying the customer service ticket to which the message will be sent. (Required)
Tipo Da Mensagem Type of message to send. Options: Arquivo (file), Áudio (audio), Imagem (image), Mapa (map), Texto (text), VCard, Vídeo (video). Default is text.
Texto Da Mensagem Text content of the message, applicable for message types: text, image, and video.
URL Da Mídia URL of the media file to send, applicable for image, video, audio, or file message types.
Nome Do Contato (VCard) Contact name to include in a vCard message.
Telefone (VCard) Phone number to include in a vCard message.
Nome Do Lugar (Mapa) Name of the place to send in a map message.
Latitude (Mapa) Latitude coordinate for the map location message.
Longitude (Mapa) Longitude coordinate for the map location message.

Output

The node outputs JSON data representing the result of the message sending operation. This typically includes confirmation details such as message IDs, status, timestamps, or error information if the sending failed.

If the message involves media, the output confirms successful upload or linking of the media resource.

No binary data output is indicated by the source code; all outputs are structured JSON responses from the platform's API.

Dependencies

  • Requires connection to the Relacio WhatsApp platform via an API key credential configured in n8n.
  • The node depends on the external Relacio API endpoints to perform actions like sending messages.
  • Proper authentication credentials must be set up in n8n to authorize API calls.

Troubleshooting

  • Common issues:

    • Invalid or missing protocol ID: The node requires a valid protocol number to send messages. Ensure this is correctly provided.
    • Incorrect media URLs: For media messages, the URL must be accessible and valid; otherwise, the message may fail.
    • Authentication errors: If the API key or credentials are invalid or expired, the node will not be able to send messages.
    • Unsupported message type combinations: Some properties only apply to certain message types; providing irrelevant fields might cause errors.

  • Error messages:

    • Errors related to missing required parameters (e.g., protocol ID).
    • API response errors indicating invalid credentials or permission issues.
    • Media upload failures due to inaccessible URLs or unsupported formats.

To resolve these, verify input parameters, ensure valid credentials, and confirm media URLs are reachable.

Links and References

  • Relacio Platform Documentation (Assumed official site, please replace with actual docs if available)
  • WhatsApp Business API concepts for message types and media handling (for general understanding)
  • n8n documentation on creating and configuring API credentials

Discussion