Relacio - WhatsApp icon

Relacio - WhatsApp

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

Actions58

Overview

The node "Relacio - WhatsApp" integrates with a WhatsApp relationship platform, enabling various operations related to contacts, messaging, protocols, groups, marketing campaigns, and more. Specifically, the operation Contato - Encaminhar ("forwardContact") allows forwarding a contact to a specified department or operator within the platform.

This node is beneficial in scenarios where automated routing of customer contacts is needed, such as directing incoming WhatsApp conversations to appropriate departments or agents for handling. For example, a support chatbot could forward a contact to the billing department when a payment issue is detected, or route VIP customers directly to senior operators.

Properties

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

Output

The node outputs JSON data representing the result of the forwarding action. This typically includes confirmation details about the forwarding operation, such as success status or updated contact information. The exact structure depends on the platform's API response but generally confirms that the contact was successfully routed.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Relacio WhatsApp platform.
  • The node depends on the external Relacio platform API 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 if the API key is invalid or expired.

  • Error messages:

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

  • Resolutions:

    • Verify the contact ID exists and is correctly entered.
    • Ensure either department ID or operator ID is provided if required by your routing logic.
    • Check and update the API key credential in n8n settings.
    • Confirm network connectivity to the Relacio platform.

Links and References

Discussion