Developer Guide to the CRM Webhook Logs Dashboard
What is the Webhook Logs Dashboard?
The Webhook Logs Dashboard is a developer tool that provides a detailed record of every outbound webhook sent from your CRM integrations. It serves as a central hub for monitoring, debugging, and verifying the data your system sends to external services. By offering real-time visibility into payloads, status codes, and delivery attempts, this dashboard empowers you to troubleshoot integration issues independently and efficiently.
Accessing the Dashboard
To access the Webhook Logs Dashboard, log into your CRM developer portal. From there, navigate to the Insights section and select Logs. This will open the dashboard where you can monitor all webhook activity.
Key Features and Benefits
Comprehensive Event Tracking
The dashboard captures a complete history for each webhook event. For every entry, you can view:
- Webhook ID: A unique identifier for the event.
- Event Name: The type of trigger that initiated the webhook.
- Timestamps: The exact time the webhook was created, delivered, and any subsequent retry attempts.
- HTTP Response Code: The status code returned by the receiving server.
- Delivery Status: Whether the delivery was successful, failed, or is being retried.
Full Payload Inspection
You can review the complete JSON payload and headers sent with each webhook. This is essential for confirming that the correct data is being transmitted to your external systems. A one-click copy function allows you to easily export the payload for further analysis in other tools.
Advanced Search and Filtering
Quickly locate specific webhook events using the powerful search and filtering tools. The global search bar supports substring matching, letting you find events based on partial values within the payload, such as an email address or contact ID. You can further refine your results using filters for:
- Webhook ID
- Event type
- Time range
- HTTP status code
Retry Behavior and Timeline
The dashboard clearly displays the retry history for failed webhooks. Understanding the retry logic is crucial for diagnosing delivery issues. The system uses different retry strategies depending on the type of failure:
- Failures with an HTTP 429 status code follow a specific retry pattern.
- Other types of failures use an exponential backoff strategy and may continue retrying for up to three days.
This extended visibility helps you determine if a temporary issue with your endpoint was later resolved by a subsequent retry.
Timezone Controls
All timestamps in the dashboard are displayed according to your personal timezone preference. A selector at the top of the page allows you to choose your local timezone. Your selection is remembered for future sessions, ensuring a consistent and intuitive auditing experience.
Data Retention
Webhook logs are retained for 30 days. This provides a sufficient window for investigating recent activity and conducting extended debugging. After 30 days, logs are permanently deleted. It is recommended that you copy and save any payloads you need for long-term records or compliance purposes.
How to Use the Dashboard for Troubleshooting
- Navigate to the Webhook Logs Dashboard via the developer portal.
- Use the search bar to look for a specific event by entering a unique identifier like an email or contact ID.
- Apply filters to narrow down the results by event type, time, or status code.
- Click on a log entry to open the detail panel and inspect the full payload and response history.
- Use the copy function to save the payload for external testing or to share with your team.
Frequently Asked Questions
Does the dashboard show failed delivery attempts?
Yes. Every delivery attempt, including failures and retries, is logged with its corresponding HTTP response code and timestamp.
Can I export the logs?
There is no bulk export feature. However, you can copy individual payloads directly from the detail panel for analysis.
What happens to logs after 30 days?
Logs older than 30 days are automatically and permanently deleted from the system.
Is the timezone setting user-specific?
Yes. The timezone you select only affects your own view of the dashboard and is saved to your user profile.
Are the payloads shown in full?
Yes. The payload data is displayed in its entirety, exactly as it was sent, and is not masked or truncated.