WaliChat icon

WaliChat

Interact with WaliChat WhatsApp API

Actions148

Webhooks → Get Webhook Logs

AI-generated

Overview

This node interacts with the WaliChat WhatsApp API, specifically focusing on managing webhooks and retrieving their logs. The "Get Webhook Logs" operation allows users to fetch log entries related to a specific webhook by its ID. This is useful for monitoring webhook activity, debugging webhook integrations, or auditing events triggered by WhatsApp messages or actions.

Practical examples include:

  • Retrieving recent webhook call logs to verify that your webhook endpoint is receiving expected events.
  • Skipping older log entries and fetching only the latest ones for performance or analysis purposes.
  • Debugging webhook failures by examining detailed logs of webhook calls.

Properties

Name Meaning
Webhook ID The unique identifier of the webhook whose logs you want to retrieve.
Options Additional parameters to control the retrieval of logs:
- Maximum Entries (size) The maximum number of log entries to retrieve (default is 20).
- Skip Entries (skip) The number of log entries to skip before starting to collect results (default is 0).

Output

The node outputs an array of JSON objects representing the webhook log entries retrieved from the WaliChat API. Each entry typically contains details about individual webhook calls such as timestamps, status, payloads, or error information (exact structure depends on the API response).

If the node supports binary data output for any operations, it would be summarized here; however, for "Get Webhook Logs," the output is purely JSON-based log data.

Dependencies

  • Requires a valid API key credential for authenticating with the WaliChat WhatsApp API.
  • Network access to the WaliChat API endpoints.
  • Proper configuration of the webhook in WaliChat to generate logs.

Troubleshooting

  • Common Issues:

    • Invalid or missing Webhook ID: Ensure the Webhook ID provided exists and is correct.
    • API authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
    • No logs returned: Check if the webhook has been triggered recently and logs exist.
    • Pagination issues: If too many logs are requested at once, consider using the "Maximum Entries" and "Skip Entries" options to paginate results.
  • Error Messages:

    • "Webhook ID is required": Provide a valid Webhook ID.
    • "Authentication failed": Check API key validity and permissions.
    • "No logs found": Confirm that the webhook has generated logs.

Resolving these usually involves verifying input parameters, credentials, and webhook setup.

Links and References

Discussion