SacNews - Relacionamento icon

SacNews - Relacionamento

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

Actions59

Overview

This node integrates with a customer relationship platform via WhatsApp, enabling various operations related to contacts, protocols, messages, groups, marketing campaigns, and more. Specifically, the "Protocolo - Encaminhar - Recado" operation allows forwarding a service protocol (a ticket or case number) to an inbox within the platform.

Use cases include:

  • Automatically routing a customer support protocol to a specific inbox for follow-up.
  • Integrating protocol forwarding into automated workflows to ensure timely handling of customer requests.
  • Managing communication flows by programmatically sending protocol notifications to designated inboxes.

Example: Forwarding a protocol number "12345" to the inbox so that the responsible team can take action on it.

Properties

Name Meaning
ID Do Protocolo The service protocol number you want to forward to the inbox. This is a required string.
Atenção: Insira O Número Do Protocolo A notice prompting the user to enter the protocol number before forwarding.

Output

The node outputs JSON data representing the result of the forwarding operation. This typically includes confirmation details such as success status, any returned identifiers, or error messages from the platform API.

No binary data output is indicated in the source code.

Dependencies

  • Requires connection to the external customer relationship platform via WhatsApp.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • Depends on internal action modules (./actions) which implement the actual API calls for each operation.

Troubleshooting

  • Missing or invalid protocol number: Ensure the "ID Do Protocolo" property is provided and correctly formatted; otherwise, the forwarding will fail.
  • Authentication errors: Verify that the API credentials are correctly set up and have sufficient permissions.
  • API connectivity issues: Check network access to the external platform and confirm the platform's API endpoint is reachable.
  • Unexpected response or empty output: Review the platform's API documentation and logs to diagnose possible changes or errors in the API behavior.

Common error messages would likely relate to invalid protocol IDs, unauthorized access, or network timeouts.

Links and References

  • Refer to the external platform’s official API documentation for detailed information on protocol forwarding endpoints and expected parameters.
  • Consult n8n documentation on setting up API credentials and using custom nodes for integration.

Discussion