ZAPIN icon

ZAPIN

Interact with Zapin EVO

Actions64

Event → Webhook

AI-generated

Overview

This node interacts with the Zapin EVO Events API to manage webhooks. It allows users to either set a new webhook or check the status of an existing webhook for a specified instance. This is useful for integrating external systems to receive real-time event notifications from the Zapin EVO platform, such as message updates, contact changes, or group events.

Use Case Examples

  1. Setting a webhook URL to receive event notifications for a specific instance.
  2. Checking if a webhook is already set for an instance to verify integration status.

Properties

Name Meaning
Instance Name The name of the instance that will send the message, used to identify the source of events.
What Do You Want To Do Choose between setting a new webhook or checking the webhook status.
Enable Webhook Toggle to enable or disable the webhook integration (only when setting a webhook).
Webhook URL The URL that will receive the webhook events (only when setting a webhook).
Webhook By Events Option to create a separate route for each event by appending the event name to the URL (only when setting a webhook).
Base64 In Webhook Option to send media data in base64 format within the webhook payload (only when setting a webhook).
Events Select which events to subscribe to for webhook notifications (only when setting a webhook).

Output

JSON

  • webhookStatus - Status or result of the webhook operation (setting or checking).
  • webhookUrl - The webhook URL configured or checked.
  • enabled - Indicates if the webhook is enabled or disabled.
  • subscribedEvents - List of events subscribed to for webhook notifications.

Dependencies

  • An API key credential for authenticating with the Zapin EVO Events API

Troubleshooting

  • Ensure the instance name is correctly specified to avoid authentication or routing errors.
  • Verify the webhook URL is accessible and correctly formatted to receive events.
  • If setting a webhook, confirm that the selected events are supported and correctly spelled.
  • Common errors may include unsupported operations or missing required parameters; verify the operation and resource selections.

Discussion