Wazend API icon

Wazend API

Interact with Wazend API

Actions59

Overview

This node integrates with the "Wazend API" to manage event webhooks. Specifically, for the Evento resource and Webhook operation, it allows users to either define a new webhook or verify an existing webhook configuration.

Common scenarios include:

  • Setting up webhooks to receive real-time notifications about various events such as message updates, group changes, contact updates, and more.
  • Verifying if a webhook is correctly configured and active before relying on it in production workflows.

Practical examples:

  • Automatically triggering downstream n8n workflows when a new message arrives or a group participant changes.
  • Monitoring connection status or QR code updates via webhook events.
  • Enabling or disabling webhook integration dynamically based on workflow logic.

Properties

Name Meaning
Nombre De La Instancia The name of the instance that will send the webhook messages. This identifies the source instance for the webhook events.
Qué Desea Hacer Choose between defining a new webhook (Definir Webhook) or verifying an existing webhook (Verificar Webhook).
Activar Webhook Enable or disable the webhook integration. Only applicable when defining a webhook.
URL Del Webhook The URL endpoint that will receive the webhook event payloads. Required when defining a webhook.
Webhook Por Eventos Whether to create a separate route for each event by appending the event name to the webhook URL. This allows handling different events on distinct URLs.
Base64 en El Webhook Whether media data sent in the webhook should be encoded in base64 format. Useful for transmitting binary content safely over JSON.
Eventos Select one or multiple event types to subscribe to for the webhook. Events include: CALL, CHATS_DELETE, CHATS_SET, CHATS_UPDATE, CHATS_UPSERT, CONNECTION_UPDATE, CONTACTS_SET, CONTACTS_UPDATE, CONTACTS_UPSERT, GROUP_PARTICIPANTS_UPDATE, GROUP_UPDATE, GROUPS_UPSERT, LABELS_ASSOCIATION, LABELS_EDIT, MESSAGES_DELETE, MESSAGES_SET, MESSAGES_UPDATE, MESSAGES_UPSERT, PRESENCE_UPDATE, QRCODE_UPDATED, SEND_MESSAGE, TYPEBOT_CHANGE_STATUS, TYPEBOT_START.

Output

The node outputs a JSON array containing the response from the Wazend API after performing the webhook operation. The structure depends on whether the user chose to set or find a webhook but generally includes:

  • Confirmation details of the webhook setup or verification status.
  • Information about subscribed events and webhook URLs.
  • Any error or status messages returned by the API.

If media data is involved and base64 encoding is enabled, the webhook payloads will contain media content encoded in base64 format.

No binary output is produced directly by this node.

Dependencies

  • Requires an API key credential for authenticating with the Wazend API.
  • The node uses the base URL https://docs.wazend.net/wazend for API requests.
  • Proper network access to the specified webhook URL is necessary for receiving events.
  • No additional external dependencies beyond the API and credentials.

Troubleshooting

  • Common Issues:

    • Incorrect webhook URL leading to failed event delivery.
    • Missing or invalid API authentication causing authorization errors.
    • Selecting no events when defining a webhook results in no triggers.
    • Network connectivity issues preventing webhook registration or verification.

  • Error Messages:

    • "Operação não suportada." — Indicates the selected operation is not supported for the resource; ensure you choose a valid operation.
    • API errors related to authentication or permissions usually mean the API key credential is missing or incorrect.
    • Validation errors if required properties like instance name or webhook URL are empty.

  • Resolutions:

    • Double-check all required input fields.
    • Verify API credentials and permissions.
    • Ensure the webhook URL is publicly accessible and can accept POST requests.
    • Confirm that at least one event type is selected when setting a webhook.

Links and References

Discussion