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 contact and messaging operations. Specifically, the "Contato - Remover Etiqueta" operation allows users to remove all tags from a specified contact by providing the contact's ID. This is useful for managing contact metadata, cleaning up outdated or incorrect tags, and maintaining organized contact records.

Practical scenarios include:

  • Removing all labels from a contact who no longer fits certain marketing segments.
  • Resetting contact tags before reapplying new categorizations.
  • Automating tag removal as part of a workflow triggered by external events.

Properties

Name Meaning
ID Do Contato The unique identifier of the contact from which all tags will be removed. This is required.

Output

The node outputs JSON data representing the result of the tag removal operation. Typically, this includes confirmation of success or details about the updated contact state after tag removal.

If the node supports binary data output (not indicated here), it would represent related media or files, but for this operation, the output is purely JSON.

Dependencies

  • Requires an API key credential to authenticate with the external customer relationship platform.
  • The node depends on the platform's API to perform contact tag management.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common Issues:

    • Invalid or missing contact ID: The operation requires a valid contact identifier; ensure the ID is correct and exists in the system.
    • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
    • Network or API downtime: Temporary connectivity issues may cause failures; retry after some time.
  • Error Messages:

    • Errors indicating "contact not found" suggest the provided ID does not match any existing contact.
    • Authentication failure messages imply invalid or expired credentials.
    • API rate limit exceeded errors require waiting or adjusting usage patterns.

Resolving these typically involves verifying input parameters, checking credential validity, and ensuring stable network connectivity.

Links and References

  • Refer to the external platform’s official API documentation for detailed information on contact and tag management endpoints.
  • Consult n8n documentation on setting up API credentials and handling node errors for best practices.

Discussion