• Instructions to Ask a Question

    Click on the "Ask a Question" button and select the application for which you would like to ask questions.

    We have 5 different products namely - Pabbly Connect, Pabbly Subscription Billing, Pabbly Email Marketing, Pabbly Form Builder, Pabbly Email Verification.

    The turnaround time is 24 hrs (Business Hours - 10.00 AM to 6.00 PM IST, Except Saturday and Sunday). So your kind patience will be highly appreciated!

    🚀🚀Exclusive Discount Offer

    Just in case you're looking for any ongoing offers on Pabbly, you can check the one-time offers listed below. You just need to pay once and use the application forever -
     

    🔥 Pabbly Connect One Time Plan for $249 (🏆Lifetime Access) -  View offer 

    🔥 Pabbly Subscription Billing One Time Plan for $249 (🏆Lifetime Access) - View offer

What is the Event Right-Side Modal View in Pabbly Hook?

Event Modal View in Pabbly Hook​

The Event Right-Side Modal in Pabbly Hook provides detailed information about a selected webhook event. This modal appears when a user clicks on an request from the Events table. Below is a detailed description of its components and functionalities.

Overview

The right-side modal view allows users to analyze the details of a specific webhook event, including its status, metadata, request details, and failure reasons (if applicable). It is especially useful for debugging failed events or understanding the payload sent to a destination.


Components of the Modal

1. Header Section

  • Event Name: Displays the name or title of the webhook event, such as testing hook.
  • Request ID: Shows the unique request ID associated with the event. It can be copied using the copy icon button beside it.
  • Event ID: Displays the unique event ID. It also has a copy icon button for easy copying.

2. Event History Section

This section provides detailed metadata and status information about the webhook event:
  • Status:
    • Indicates the current status of the event (e.g., Scheduled, Success, or Failed).
    • Failed statuses are highlighted in red for better visibility.
  • Created At:
    • Displays the date and time the event was created.
  • Failed Cause(if applicable):
    • Provides details about the reason for failure (e.g., "Failed with status code of 404").
      • Failed Cause status codes are grouped into two classes:
        • 200: Successful responses
        • 400: Client error responses
  • Content-Length:
    • Displays the size of the content sent in the request.
  • Content-Type:
    • Specifies the type of content sent, such as application/JSON.
  • Method:
    • Indicates the HTTP method used for the event, such as POST or GET.

3. Request Details Section

This section provides a detailed view of the payload and parameters sent in the request.

Body:​

  • Displays the JSON body of the request. For example:
    {
    "name": "testing"
    }

Query Params:​

  • Displays the query parameters passed in the request, if any. For example:
    {
    "checking": "hook"
    }

Functionalities

Copy Buttons

  • Users can easily copy the Request ID and Event ID using the provided copy icons next to these fields.

Error States and Styling​

  1. Failed Status
    • Displayed prominently in red to indicate an error state.
  2. JSON Body Formatting
    • The body content is displayed in a structured, indented format for readability.
  3. Empty States
    • Fields like Query Parameters display "NA" when no data is available.

How to Access the Modal​

  1. Navigate to the Event page in the Pabbly Hook dashboard.
  2. Click on any request in the table to open its detailed modal view.
    1733737807960.png
    1733737939722.png


Use Cases

  1. Debugging Failed Events:
    • Understand why a webhook failed by reviewing the Failed Cause and verifying the request payload.
  2. Validating Payloads:
    • Confirm the correctness of the data sent in the request by analyzing the Body and Query Params sections.
  3. Event Metadata Reference:
    • Use the Request ID and Event ID as references when reaching out to support or for logging purposes.

Tips for Effective Use

  • Cross-Check Payloads: Compare the Body and Query Params with the expected format of the destination server to identify mismatches.
  • Monitor Status Codes: Use the Failed Cause and status code to pinpoint the type of error (e.g., authentication failure, endpoint not found, etc.).
  • Leverage Copy Functionality: Quickly copy the Request ID or Event ID for use in other tools or when reporting issues.

This modal serves as a powerful tool for analyzing webhook events and improving troubleshooting efficiency within the Pabbly Hook platform.
 
Last edited:
Top