izapp - WhatsApp icon

izapp - WhatsApp

Interação com a Plataforma de Relacionamento via WhatsApp - IZapp
Join our community

Actions58

Overview

This node integrates with a WhatsApp relationship platform (IZapp) to perform various contact and communication management operations. Specifically, the "Contato - Encaminhar" (Contact - Forward) operation allows forwarding a contact to a specified department or operator within the platform. This is useful in scenarios where contacts need to be reassigned or routed to different teams or agents for handling.

Practical examples:

  • Automatically forward a customer inquiry contact to the sales department.
  • Route a support contact to a specific operator specialized in the issue.
  • Reassign contacts dynamically based on workload or availability.

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. The exact structure depends on the platform's API response but generally confirms that the contact was successfully forwarded.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential to authenticate with the IZapp WhatsApp platform.
  • The node depends on the external IZapp 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 not configured 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.
    • 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 as needed.
    • Check and update the API key credential in n8n settings.
    • Confirm network connectivity to the IZapp platform.

Links and References

Discussion