WassengerInstall

Overview

This node interacts with the Wassenger WhatsApp API, specifically providing operations related to WhatsApp webhooks among many other resources. The Get Webhook Logs operation retrieves log entries for a specified webhook, allowing users to monitor and audit webhook activity.

Common scenarios where this node is beneficial include:

• Debugging webhook events by reviewing recent logs.
• Auditing webhook calls to ensure expected data is received.
• Monitoring webhook performance or failures over time.

For example, a user can fetch the last 20 log entries of a particular webhook to verify that messages are being delivered correctly or to investigate errors.

Properties

Output

The output is an array of JSON objects representing individual webhook log entries. Each entry typically contains details about a single webhook event such as timestamps, status, payload, or error information depending on the webhook's implementation.

No binary data output is indicated for this operation.

Dependencies

• Requires an active connection to the Wassenger WhatsApp API via an API key credential.
• The node depends on the external Wassenger service to fetch webhook logs.
• Proper configuration of the API key credential in n8n is necessary for authentication.

Troubleshooting

• Common issues:

  • Invalid or missing Webhook ID will cause the operation to fail.
  • Insufficient permissions or invalid API key may result in authentication errors.
  • Requesting too many log entries at once might lead to rate limiting or timeout errors.

• Error messages:

  • "Webhook not found": Verify the Webhook ID is correct.
  • "Authentication failed": Check that the API key credential is valid and has required permissions.
  • "Request timed out" or "Rate limit exceeded": Reduce the number of requested entries or add delays between requests.

Links and References

• Wassenger Official API Documentation
• n8n Documentation on Credentials
• Webhooks Concept Overview