izapp - WhatsApp icon

izapp - WhatsApp

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

Actions58

Overview

This node integrates with the IZapp WhatsApp Relationship Platform, enabling various operations related to contacts, protocols, messages, groups, marketing campaigns, and more. Specifically, for the operation "Protocolo - Observações - Adicionar" (Add Observation to Protocol), it allows users to add a textual observation or note to an existing protocol by specifying the protocol number and the observation content.

Common scenarios where this node is beneficial include:

  • Customer support workflows where agents need to append notes or comments to ongoing service tickets (protocols).
  • Automated systems that log additional information or status updates to protocols based on external triggers.
  • Enhancing protocol records with contextual observations for better tracking and auditing.

Example use case:

  • A customer service automation adds an observation like "Customer requested callback tomorrow" to protocol number "12345" after a phone interaction.

Properties

Name Meaning
Protocolo The protocol number to which you want to add an observation.
Observação The text of the observation/note to be added to the specified protocol.

Output

The node outputs JSON data representing the result of adding the observation to the protocol. This typically includes confirmation details such as success status, updated protocol information, or error messages if the operation failed.

No binary data output is indicated for this operation.

Dependencies

  • Requires connection to the IZapp WhatsApp Relationship Platform API.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • The node depends on internal action implementations imported from bundled dependencies to perform the actual API calls.

Troubleshooting

  • Common issues:

    • Invalid or missing protocol number: Ensure the "Protocolo" property is correctly set and corresponds to an existing protocol.
    • Authentication errors: Verify that the API key or authentication credentials are properly configured and valid.
    • Network or API downtime: Check connectivity and platform status if requests fail unexpectedly.
  • Error messages:

    • Errors related to missing required parameters will occur if either "Protocolo" or "Observação" is empty.
    • API response errors may indicate invalid protocol IDs or permission issues; review API documentation and credentials.

Resolving these usually involves verifying input values, checking credentials, and ensuring the target protocol exists and is accessible.

Links and References

Discussion