Clear update signals
We show release type and critical flags.
Integration guide
DepLog.dev notifications in Slack
Post dependency updates to the channels your team watches. Use an incoming webhook URL and keep alerts short.
At a glance
- Unique incoming webhook URL
- Per monitor routing to channels
- Changelog highlights and risk hints
Why teams use DepLog.dev with Slack
Short alerts that explain what changed and why it matters.
Changelog highlights
We scan release notes and surface the key lines.
Ecosystem coverage
Popular or niche packages across supported registries, even with messy changelogs.
Slack webhook setup
Create one incoming webhook and reuse it across monitors.
Step 1
Create a Slack app
Open api.slack.com/apps and create an app for your workspace.
Step 2
Enable Incoming Webhooks
In the app settings, enable Incoming Webhooks and add one to a channel.
Step 3
Copy the webhook URL
Slack shows a unique URL that starts with https://hooks.slack.com/services/. Keep it private.
Step 4
Paste it into DepLog.dev
In a monitor, enable Slack alerts and paste the URL.
Step 5
Send a test and save
Use the Slack test button, then save your monitor.
Permissions and access
- You need permission to add apps to the workspace or channel.
- Incoming Webhooks must be enabled for the Slack app.
- Keep the webhook URL private because it can post to the channel.
Slack webhook FAQ
Do I need a Slack webhook URL?
Yes. Slack gives you a unique incoming webhook URL. Treat it as a secret.
Can I post to multiple channels?
Yes. Create one webhook per channel and assign it to each monitor.
What does the alert include?
We send the package, versions, release type and changelog highlights when available.
What if the webhook stops working?
Update the URL and send a test. Failed deliveries show in the log.
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.