izapp - WhatsApp icon

izapp - WhatsApp

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

Actions58

Overview

This node integrates with a WhatsApp Relationship Platform called IZapp, enabling interaction with various aspects of WhatsApp contacts, protocols (conversations), groups, marketing campaigns, and more. Specifically, the "Protocolo - Consultar" operation allows users to query the history of a specific protocol (conversation) by its unique protocol ID.

Common scenarios for this node include:

  • Retrieving detailed conversation history for customer support or auditing purposes.
  • Accessing protocol data to analyze interactions made via WhatsApp on the platform.
  • Integrating WhatsApp conversation data into workflows for CRM, reporting, or automation.

For example, a user can input a protocol number to fetch all messages and metadata related to that conversation, which can then be used to trigger follow-up actions or generate reports.

Properties

Name Meaning
ID Do Protocolo The unique identifier number of the protocol (conversation) you want to consult. This is the record ID of the WhatsApp interaction made through the Relationship Platform.

Output

The node outputs JSON data representing the queried protocol's history. This typically includes details such as messages exchanged, timestamps, participants, and any associated metadata from the WhatsApp conversation.

If the node supports binary data output (not explicitly shown in the provided code), it would represent media or attachments related to the protocol messages.

Dependencies

  • Requires an API key credential to authenticate with the IZapp WhatsApp Relationship Platform.
  • The node depends on internal action modules (./actions) that implement the actual API calls.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid protocol ID: Ensure the "ID Do Protocolo" property is correctly set and corresponds to an existing protocol in the platform.
  • Authentication errors: Verify that the API key credential is valid and has the required permissions.
  • Network or API issues: Check connectivity to the IZapp platform and confirm the service is operational.
  • Unexpected empty results: Confirm that the protocol ID actually has associated history; some IDs may not have messages if they are incorrect or incomplete.

Common error messages will likely relate to authentication failures, invalid parameters, or network timeouts. Resolving these involves checking credentials, input values, and network status.

Links and References

Discussion