Wazzap Trigger icon

Wazzap Trigger

Handle events from Wazzap
Join our community

Overview

This node acts as a trigger for events from the Wazzap service, allowing workflows to start when specific Wazzap-related events occur. It listens for incoming webhook calls corresponding to selected event types such as receiving a message, adding a tag, or creating a group.

Common scenarios where this node is beneficial include:

  • Automating responses or processing when a new message arrives in Wazzap.
  • Triggering actions when tags are added to messages or contacts.
  • Initiating workflows upon creation of new groups within Wazzap.

For example, you could use this node to automatically log incoming messages into a CRM system, notify team members when a tag is added, or update a database when a new group is created.

Properties

Name Meaning
Event The type of Wazzap event to listen for. Options:
- 📩 Message Received: Triggered when a message is received
- 🏷️ Tag Added: Triggered when a tag is added
- 👥 Group Created: Triggered when a group is created

Output

The node outputs JSON data representing the payload received from the Wazzap webhook event. This data is accessible in the workflow as an array with one element containing the full body of the webhook request.

No binary data output is produced by this node.

Example output structure (simplified):

[
  {
    "body": {
      /* event-specific data sent by Wazzap */
    }
  }
]

Dependencies

  • Requires an API key credential for authenticating with the Wazzap API.
  • The node uses webhooks and requires proper configuration of webhook URLs in both n8n and Wazzap.
  • The node depends on utility functions (createWebHookFromTrigger and apiRequest) from its internal utils module to manage webhook registration and API communication.

Troubleshooting

  • Webhook registration failures: If the node cannot register or verify the webhook with Wazzap, ensure that the API key credential is valid and has sufficient permissions.
  • Webhook URL issues: Make sure the webhook URL generated by n8n is publicly accessible and correctly configured in Wazzap.
  • Event mismatch: Confirm that the selected event matches the webhook path and that Wazzap sends events accordingly.
  • API errors: The node throws errors if the Wazzap API returns non-success HTTP status codes or error messages. Check network connectivity and API credentials.
  • Deleting webhooks: If webhook deletion fails, verify that the stored webhook URL exists and that the API key allows deleting webhooks.

Links and References

Discussion