Currently, Nerdio Manager for MSP supports notifications for high CPU, disk and memory usage but only via email. Webhook functionality, while effective for error messages, does not trigger notifications for resource usage alerts.
We would like to request webhook notifications to include high CPU, disk and memory usage alerts.
Enable Webhook Notifications for High CPU/Memory Usage Alerts
Welcome to the community, Mart 🙂!
You're correct. We don't currently have a way to do Webhook notifications, but we do have a way to do Custom API Notifications.
Will that do what you're needing or is your use case a bit different?


Hi Dave,
Sorry for the late repsonse, that is exactly what I mean. While you can set up the Custom API Notification it does not work for the "Usage condition". We have Custom API Notification for errors and those work perfectly, but not for usage condition. We use Power Automate but our workflow does simply not get triggered, while it has been set up in Nerdio.
Below is an overview of the conditions and the actions. The Connectworks - MEM USAGE does not trigger our (test) flow while the endpoint URL is correct.

Also if I change Connectworks - MEM USAGE to send an email it works fine. But we need a API endpoint.
No, problem, Mart.Â
We all get busy and any reply is better than no reply. 🙂
Thanks for adding additional details around your use-case.
It helps-out our product team when adding features.Â
Hi Dave,
Do you have any idea if this is something that can be added any time soon? because otherwise we would need to look at other possibilities
Sorry, Mart.
I wish I could say "it will be released next week", but unfortunately, I'm not sure where this is in the backlog of requests.
The last I checked, our product team hasn't listed the features that are going to be included in the v5.8 release (NMM Product Revisions – Nerdio Help Center), but it's possible they could include this in that.
However, unless you see something specific on our release notes and/or someone from our product team is able to chime-in, I would go ahead and plan on implementing a work-around, for now.
Â
Â
Please sign in to leave a comment.
Comments (5 comments)