Relacio - WhatsApp icon

Relacio - WhatsApp

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

Actions58

Overview

The node "Relacio - WhatsApp" integrates with a WhatsApp-based Relationship Platform called Relacio. It provides multiple operations to interact with contacts, protocols (conversations), groups, marketing campaigns, and other related data managed via the platform.

Specifically, the Protocolo - Consultar operation (getHistoryProtocol) allows users to query the history of a specific protocol (conversation record) by its unique protocol ID. This is useful for retrieving detailed conversation logs or interaction histories associated with a particular WhatsApp relationship session.

Common scenarios include:

  • Customer support teams retrieving past conversation details for follow-up.
  • Auditing communication history for compliance or quality assurance.
  • Automating workflows that depend on historical message data from WhatsApp interactions.

Example: Given a protocol number, the node fetches all messages and metadata related to that conversation, enabling further processing or reporting in an automation workflow.

Properties

Name Meaning
ID Do Protocolo The unique identifier of the protocol (conversation) to retrieve. This is the record ID of the WhatsApp interaction in the platform.

Output

The node outputs JSON data representing the protocol's history. This typically includes:

  • Messages exchanged within the protocol.
  • Metadata such as timestamps, sender/receiver info, and message status.
  • Possibly additional protocol-related details like observations or tags.

No binary data output is indicated for this operation.

Dependencies

  • Requires connection to the Relacio WhatsApp Relationship Platform API.
  • Needs an API authentication credential configured in n8n to authorize requests.
  • The node depends on internal action modules (imported as a in the code) which implement the actual API calls.

Troubleshooting

  • Missing or invalid protocol ID: The operation requires a valid protocol number; ensure the input is correct and exists in the platform.
  • Authentication errors: Verify that the API key or credentials are correctly set up and have sufficient permissions.
  • Network or API downtime: Connectivity issues or platform outages can cause failures; check network access and platform status.
  • Unexpected empty results: Confirm that the protocol ID corresponds to an existing conversation with history.

Error messages will generally relate to invalid parameters, authorization failures, or API response errors. Resolving them involves validating inputs, checking credentials, and ensuring the platform service is operational.

Links and References

Discussion