Clear update signals
We include release type and critical flags.
Integration guide
DepLog.dev webhook notifications
Use one webhook URL to deliver dependency alerts to Slack, Teams and your own system.
At a glance
- Single webhook per monitor
- Auto-detects Slack and Teams
- Standard JSON payload for custom endpoints
Why teams use the DepLog.dev webhook
One destination, clear updates and consistent payloads.
Changelog highlights
We scan release notes and surface the key lines.
Ecosystem coverage
Popular or niche packages across supported registries, even with messy changelogs.
Webhook setup
Connect one webhook per monitor and keep routing simple.
Step 1
Create a destination webhook
Generate a webhook URL in Slack, Teams or your own service. Keep any secret or signature intact.
Step 2
Paste it into DepLog.dev
Enable webhook alerts and add the URL in the monitor settings. We send to the exact URL so keep any secret in place.
Step 3
Confirm destination
If auto-detection is unsure pick Slack, Teams and Custom. This helps with self-hosted domains.
Step 4
Send a test
Use the webhook test button to verify delivery.
Step 5
Save and monitor
Save the monitor and watch updates flow in.
Standard payload format
Custom webhooks receive a stable JSON payload with package, version and changelog context.
Example payload
{
"event": "dependency.update",
"channel": "webhook",
"summary": "nuxt 3.12.4 -> 3.13.0 (minor)",
"occurredAt": "2025-01-15T10:04:00.000Z",
"monitor": {
"id": "mon_123",
"name": "Production"
},
"dependency": {
"name": "nuxt",
"label": "frontend"
},
"versions": {
"current": "3.12.4",
"latest": "3.13.0",
"releaseType": "minor",
"isCritical": false
},
"changelog": {
"highlights": [
"Added runtime config for Nitro",
"Fixed build caching regressions"
]
}
}Webhook FAQ
Can I use one webhook for Slack or Teams?
Yes. Add the URL and we format the alert for Slack or Teams when detected or when you choose the destination.
What if the webhook domain is custom?
Select the destination manually. This is common for self-hosted Slack or Teams deployments.
What does the payload include?
Event name, summary, monitor info, dependency details, versions and changelog data when available.
Can I reuse the same webhook across monitors?
Yes. You can reuse one webhook, but only one destination can be active per monitor.
Do you support private packages or private repositories?
No. DepLog.dev monitors public packages and public release notes only. Private registries are not supported yet.