Webhook Logs
Monitor and debug incoming webhook deliveries from GitHub, ClickUp, and other integrations.
Overview
Webhook Logs provide visibility into all incoming webhook deliveries. Use them to verify integrations are working, debug issues, and audit activity.
Accessing Webhook Logs
- Go to Settings → Webhook Logs
- View the list of recent webhook deliveries
- Click any entry to see details
Log Entry Information
Each webhook log entry includes:
Summary View
| Field | Description |
|---|---|
| Source | Integration that sent the webhook (GitHub, ClickUp, Clockify) |
| Event | Event type (e.g., push, pull_request, task_updated) |
| Status | Success, Failed, or Pending |
| Timestamp | When the webhook was received |
| Duration | Processing time in milliseconds |
Detail View
Click on an entry to see:
- Request Headers — HTTP headers (sensitive data redacted)
- Request Payload — Full JSON body
- Response Status — HTTP status code returned
- Processing Log — What actions were taken
- Error Message — If processing failed
Filtering Logs
Filter webhook logs by:
By Source
- GitHub
- ClickUp
- Clockify
- All Sources
By Status
- Success — Processed successfully
- Failed — Processing failed
- Pending — Still processing
By Date Range
Select a custom date range to narrow results.
Common Webhook Events
GitHub Events
| Event | Description |
|---|---|
push |
Code pushed to a branch |
pull_request |
PR opened, closed, or updated |
pull_request_review |
Review submitted on a PR |
installation |
GitHub App installed/uninstalled |
repository |
Repository created/deleted |
ClickUp Events
| Event | Description |
|---|---|
taskCreated |
New task created |
taskUpdated |
Task modified |
taskDeleted |
Task deleted |
taskStatusUpdated |
Task status changed |
Clockify Events
| Event | Description |
|---|---|
TIME_ENTRY_CREATED |
New time entry logged |
TIME_ENTRY_UPDATED |
Time entry modified |
TIME_ENTRY_DELETED |
Time entry removed |
TIMER_STOPPED |
Active timer stopped |
Debugging Failed Webhooks
Common Failure Reasons
| Error | Cause | Solution |
|---|---|---|
| Invalid signature | Webhook secret mismatch | Regenerate and update secret |
| Unknown event type | Unhandled event | Event may not require handling |
| Processing error | Internal error during processing | Check error message for details |
| Rate limited | Too many webhooks | Webhooks will retry automatically |
Retrying Failed Webhooks
For some webhook types, you can retry processing:
- Open the failed webhook log entry
- Review the error message
- Click Retry if available
Data Retention
Webhook logs are retained based on your organization's plan:
- Free — 7 days
- Basic — 30 days
- Standard — 90 days
- Premium — 180 days
- Enterprise — 365 days
Security
Webhook logs protect sensitive information:
- Headers — Authorization tokens are redacted
- Signatures — Secret-derived signatures are hidden
- Credentials — Any credential fields are masked
Webhook Health
Monitor webhook health in the summary view:
- Success Rate — Percentage of successful deliveries
- Average Processing Time — How long webhooks take to process
- Recent Failures — Count of failures in the last 24 hours
Tip: If you see a high failure rate, check that your integration credentials and webhook secrets are up to date.
Permissions
| Permission | Description |
|---|---|
webhooks.view |
View webhook subscriptions and logs |
webhooks.manage |
Create and manage webhooks |
webhooks.retry |
Retry failed webhook deliveries |
For outgoing webhooks (sending data from Jasper), see the Webhooks documentation.