SacNews - Relacionamento

Overview

This node integrates with the SacNews Plataforma de Relacionamento via WhatsApp, enabling interaction with various aspects of customer relationship management such as contacts, protocols, messages, groups, marketing campaigns, and more. Specifically, the "Recados - Pesquisar" (Messages - Search) operation allows users to search for a message ("recado") by its protocol identifier.

Common scenarios where this node is beneficial include:

• Retrieving detailed information about a specific message or notification using its unique protocol.
• Automating workflows that require fetching message status or content from the SacNews platform.
• Integrating WhatsApp-based customer service interactions into broader automation pipelines.

Practical example:

• A support team uses this node to automatically fetch the details of a customer message by providing its protocol number, then routes the information to the appropriate department or logs it in a CRM system.

Properties

Output

The node outputs JSON data containing the details of the searched message corresponding to the provided protocol. The exact structure depends on the response from the SacNews API but typically includes fields such as message content, sender information, timestamps, status, and related metadata.

If the node supports binary data output (not explicitly shown here), it would represent attachments or media associated with the message.

Dependencies

• Requires an API key credential for authenticating with the SacNews Plataforma de Relacionamento.
• The node depends on the SacNews API endpoints to perform operations.
• Proper configuration of the API authentication token within n8n credentials is necessary.

Troubleshooting

• Common issues:

  • Providing an invalid or empty protocol number will likely result in no data found or an error response.
  • Network connectivity problems can cause request failures.
  • Missing or incorrect API credentials will prevent successful authentication.

• Error messages and resolutions:

  • "Authentication failed": Verify that the API key credential is correctly configured and valid.
  • "Protocol not found" or empty results: Confirm that the protocol number entered exists and is correct.
  • Timeout or network errors: Check internet connection and API endpoint availability.

Links and References

• SacNews Plataforma de Relacionamento Documentation (replace with actual URL if available)
• n8n documentation on Creating Custom Nodes