SacNews - Relacionamento icon

SacNews - Relacionamento

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

Actions59

Overview

The node "SacNews - Relacionamento" integrates with a customer relationship platform via WhatsApp, enabling various operations related to contacts, protocols, messages, and more. Specifically, the Protocolo - Finalizar operation allows users to finalize (close) a service protocol or ticket within the platform.

This operation is useful in scenarios where a customer support or service interaction tracked by a protocol number needs to be marked as completed. For example, after resolving a customer's issue, an agent can use this node to close the protocol and optionally notify the contact about the closure.

Practical examples:

  • Closing a customer support ticket once the issue is resolved.
  • Automatically notifying the customer that their request has been finalized.
  • Integrating protocol finalization into automated workflows for service management.

Properties

Name Meaning
ID Do Protocolo The protocol number of the service interaction you want to finalize.
Notificar O Contato Boolean option to enable or disable notification to the contact about the protocol closure.
Texto De Notificação The notification text sent to the contact if notification is enabled. Supports variables like %PROTOCOLO%.
Aviso Informational notice indicating that this action will finalize the service protocol.

Output

The node outputs JSON data representing the result of the protocol finalization operation. This typically includes confirmation details such as success status, updated protocol information, or error messages if the operation failed.

No binary data output is indicated for this operation.

Dependencies

  • Requires connection to the SacNews customer relationship platform via WhatsApp.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • The node depends on internal action implementations imported from bundled dependencies to perform the protocol finalization.

Troubleshooting

  • Common issues:

    • Providing an incorrect or non-existent protocol number will likely cause the operation to fail.
    • Missing or invalid API credentials will prevent successful communication with the platform.
    • If notification is enabled but the notification text is empty or malformed, the message may not send properly.

  • Error messages:

    • Errors related to "protocol not found" indicate the specified protocol ID does not exist; verify the ID.
    • Authentication errors suggest problems with the API key or token; check credential configuration.
    • Network or timeout errors may occur if the platform is unreachable; ensure network connectivity.

To resolve these issues, verify input parameters carefully, confirm API credentials are valid, and ensure the platform service is operational.

Links and References

Discussion