Clientes Online - WhatsApp icon

Clientes Online - WhatsApp

Interação com a Plataforma de Relacionamento via WhatsApp - Clientes.Online
Join our community

Actions59

Overview

This node integrates with the "Clientes Online - WhatsApp" platform, enabling interaction with WhatsApp-based customer relationship management features. Specifically, the "Contato - Encaminhar" (Contact - Forward) operation allows users to forward a contact to another department or operator within the platform.

Typical use cases include:

  • Automatically routing incoming WhatsApp contacts to the appropriate department for handling.
  • Assigning contacts to specific operators based on workload or expertise.
  • Streamlining customer support workflows by programmatically managing contact assignments.

For example, a support automation workflow could receive a new contact and then forward it to the sales department or a particular sales representative using this node.

Properties

Name Meaning
ID Do Contato The unique identifier of the contact to be forwarded.
ID Do Departamento The identifier of the department to which the contact should be forwarded (optional).
ID do Operador The identifier of the operator to whom the contact should be forwarded (optional).

Output

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

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential to authenticate with the Clientes Online platform.
  • The node depends on the Clientes Online API service to perform contact forwarding.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common Issues:

    • Missing or invalid contact ID will cause the forwarding to fail.
    • Providing both department ID and operator ID incorrectly may lead to ambiguous routing.
    • Network or authentication errors due to misconfigured API credentials.

  • Error Messages:

    • Errors related to "contact not found" indicate the provided contact ID does not exist.
    • Authentication failures suggest issues with the API key or credential setup.
    • Validation errors may occur if required parameters are missing or malformed.

  • Resolutions:

    • Verify that the contact ID is correct and exists in the system.
    • Ensure API credentials are correctly configured and have sufficient permissions.
    • Provide either a department ID or operator ID as the forwarding target; avoid conflicting inputs.

Links and References

Discussion