SacNews - Relacionamento icon

SacNews - Relacionamento

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

Actions59

Overview

This node integrates with a WhatsApp-based Relationship Platform called SacNews, enabling interaction with various aspects of customer relationship management via WhatsApp. Specifically, the "Protocolo - Consultar" operation allows users to query the history of a specific protocol (conversation record) by providing its unique protocol ID.

Common scenarios for this node include:

  • Retrieving the full conversation history of a customer support or service interaction identified by a protocol number.
  • Auditing or reviewing past communications linked to a particular protocol.
  • Automating workflows that require fetching detailed protocol data from the WhatsApp Relationship Platform.

Example use case: A customer support team wants to automatically fetch and analyze the entire chat history of a given protocol number to assess the quality of service or to continue a previous conversation seamlessly.

Properties

Name Meaning
ID Do Protocolo The unique identifier number of the protocol (conversation record) you want to retrieve. This is the registered record of the conversation made through the WhatsApp Relationship Platform.

Output

The node outputs JSON data representing the details and history of the specified protocol. This typically includes all messages, timestamps, participants, and any metadata related to the conversation identified by the protocol ID.

If the platform supports binary data (e.g., media files in the conversation), such data would be included accordingly, but based on the static analysis, the primary output is structured JSON detailing the protocol's conversation history.

Dependencies

  • Requires an API key credential to authenticate with the SacNews WhatsApp Relationship Platform.
  • The node depends on the external SacNews API endpoints to fetch protocol history data.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid protocol ID: If the "ID Do Protocolo" property is empty or incorrect, the node will likely fail to retrieve data. Ensure the protocol number is accurate and corresponds to an existing conversation.
  • Authentication errors: Failure to provide valid API credentials or expired tokens will result in authentication errors. Verify that the API key credential is correctly set up and active.
  • API connectivity issues: Network problems or API downtime can cause request failures. Check network connectivity and the status of the SacNews platform.
  • Unexpected response format: If the API changes its response structure, the node might not parse the data correctly. In such cases, updating the node or contacting support may be necessary.

Links and References

Discussion