Improved Webhook Logs
Improved Webhook Logs and Error Reporting
Released: August 19, 2025
What's New
Webhook logs now display with a cleaner interface and show exact error codes and messages when external webhooks fail, making troubleshooting dramatically easier.
Cleaner Log Display
The webhook logs interface has been redesigned for easier review:
- More organized layout
- Better visual hierarchy
- Easier to scan and find specific calls
- Improved readability
Exact Error Codes and Messages
When external webhooks fail, you now see:
- Exact HTTP Status Codes: Precise error codes from external services (404, 500, etc.)
- Detailed Error Messages: Complete error text from the receiving service
- Response Data: Full response payload when available
- Timing Information: When the error occurred
Why It Matters
- Faster Debugging: Identify issues immediately without guessing
- Better Context: Understand exactly what went wrong and why
- Reduced Support Tickets: Solve webhook issues yourself with clear error information
- Improved Reliability: Fix webhook integrations faster and prevent future failures
Example
Instead of seeing "Webhook failed," you now see: "HTTP 401 - Unauthorized: Invalid API key provided." This tells you exactly what to fix.
Additional Webhook Updates (November 2025)
Further webhook logging improvements were released in November 2025:
- Save Entire Payload: Full webhook payload saved to rich/long text field
- Search by Call ID: Quick webhook search by Call ID
- Details Page: Dedicated details page per webhook with direct link to specific call
- Webhook Timing: Execution time displayed for each webhook
- Retry Attempts: Shows how many attempts were made for successful webhook call
- Webhook Requests Visibility: New Requests column in webhook list table (December 2025)
Source: Tuesdays with Tadabase - August 19, 2025, November 11, 2025, December 16, 2025
We'd love to hear your feedback.