Clear update signals
We show release type and critical flags.
Integration guide
DepLog.dev notifications in Microsoft Teams
Send dependency updates to the Teams channels your team watches. Use an incoming webhook URL and add the Incoming Webhook app to the channel.
At a glance
- Unique incoming webhook URL
- Per monitor routing to channels
- Changelog highlights and risk hints
Why teams use DepLog.dev with Teams
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.
Microsoft Teams webhook setup
Create one incoming webhook and reuse it across monitors.
Step 1
Open the Teams channel
Pick the channel for alerts and open its menu.
Step 2
Add Incoming Webhook
Select Apps, add Incoming Webhook and confirm you have permission to add it.
Step 3
Copy the webhook URL
Teams shows the URL after setup. Keep it private.
Step 4
Paste it into DepLog.dev
In a monitor, enable Teams alerts and paste the URL.
Step 5
Send a test and save
Use the Teams test button, then save your monitor.
Permissions and access
- You need permission to add Incoming Webhook to the channel.
- Your Teams admin may need to allow Incoming Webhook.
- Keep the webhook URL private because it can post to the channel.
Teams webhook FAQ
Do I need a Teams webhook URL?
Yes. Teams gives you a unique webhook URL. Treat it as a secret.
Can I send 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 Incoming Webhook is blocked?
Ask your Teams admin to allow it for your organization.
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.