izapp - WhatsApp icon

izapp - WhatsApp

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

Actions58

Overview

This node integrates with the IZapp WhatsApp Relationship Platform, providing a wide range of operations related to contacts, messaging, protocols, marketing campaigns, groups, and user management. Specifically, the operation "Usuário - Carteira - Listar" (User - Wallet - List) retrieves the wallet information for a specified operator. This wallet likely contains contacts or items associated with that operator.

Common scenarios where this node is beneficial include:

  • Managing WhatsApp contact lists and their tags.
  • Sending notifications or messages to contacts or groups.
  • Retrieving detailed information about operators, contacts, protocols, and campaigns.
  • Accessing and managing user wallets to see which contacts are assigned to an operator.

Practical example:

  • A customer support manager wants to list all contacts currently assigned to a specific operator's wallet to monitor workload or reassign contacts.

Properties

Name Meaning
ID do Operador The unique identifier of the operator whose wallet you want to query.
Página The page number of the wallet results to display; useful for paginated responses. Default is 1.

Output

The output is an array of JSON objects representing the wallet contents for the specified operator. Each item in the output corresponds to a contact or entity linked to the operator's wallet.

  • The json field contains the structured data retrieved from the platform API.
  • There is no indication that binary data is returned by this operation.

Dependencies

  • Requires an API key credential for the IZapp ClientesOnline platform.
  • The node depends on the bundled actions module (./actions) which implements the actual API calls.
  • Proper configuration of the API credentials within n8n is necessary for authentication.

Troubleshooting

  • Missing or invalid operator ID: If the "ID do Operador" property is empty or incorrect, the API call will fail or return no data. Ensure the operator ID is valid.
  • Pagination issues: Requesting a page number beyond available pages may result in empty results. Verify the total number of pages if supported.
  • Authentication errors: If the API key credential is missing or invalid, the node will throw authentication errors. Check the configured credentials.
  • Network or API downtime: Connectivity problems or platform outages can cause request failures. Retry later or check platform status.

Links and References

Discussion