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-based customer relationship platform, enabling users to send various types of messages linked to a specific service protocol. The "Protocolo - Mensagem - Enviar" operation allows sending messages such as text, images, videos, audio, files, location maps, and vCards directly associated with a protocol number that identifies a customer service interaction.

Common scenarios include:

  • Sending updates or responses to customers within an ongoing support protocol.
  • Sharing multimedia content (images, videos, audio) relevant to the service case.
  • Providing contact information via vCard or location details via map messages.
  • Automating communication flows in customer support or sales processes tied to protocols.

Practical example:
A support agent can use this node to send a text message confirming a scheduled appointment linked to a protocol number, or send an image of a product manual to the customer within the same protocol context.

Properties

Name Meaning
ID Do Protocolo The unique protocol number identifying the customer service interaction to which the message will be sent. (Required)
Tipo Da Mensagem Type of message to send. Options: Arquivo (file), Áudio (audio), Imagem (image), Mapa (map), Texto (text), VCard (vcard), Vídeo (video). Default is Texto (text).
Texto Da Mensagem Text content of the message, applicable for text, image, and video message types.
URL Da Mídia URL of the media file to send, used for image, video, audio, or file message types.
Nome Do Contato (VCard) Contact name to include in a vCard message.
Telefone (VCard) Phone number to include in a vCard message.
Nome Do Lugar (Mapa) Name of the place to send in a map message.
Latitude (Mapa) Latitude coordinate for the map location message.
Longitude (Mapa) Longitude coordinate for the map location message.

Output

The node outputs JSON data representing the result of the message sending operation. This typically includes confirmation details such as message IDs, status, timestamps, or error information if the sending failed.

If the message involves media, the output confirms successful upload or linking of the media resource.

No binary data output is indicated by the source code; all outputs are JSON structured.

Dependencies

  • Requires connection to the external WhatsApp-based customer relationship platform via an API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The node depends on internal action modules (not detailed here) that handle the actual API calls.

Troubleshooting

  • Missing or invalid protocol ID: The node requires a valid protocol number to send messages. Ensure the "ID Do Protocolo" property is correctly set.
  • Incorrect media URLs: For media messages, the URL must be accessible and valid. Invalid URLs may cause failures.
  • Unsupported message type combinations: Some properties only apply to certain message types; setting incompatible fields may lead to errors.
  • Authentication errors: If the API key or token is missing or invalid, the node will fail to authenticate.
  • Network issues: Connectivity problems with the external platform can cause timeouts or errors.

To resolve errors:

  • Verify all required fields are filled according to the message type.
  • Check API credentials and permissions.
  • Confirm media URLs are reachable and properly formatted.
  • Review error messages returned in the output JSON for specific API error codes.

Links and References

  • No direct external links provided in the source code.
  • Users should refer to the official documentation of the integrated WhatsApp customer relationship platform for API details and message format specifications.

Discussion