Turn training events into automations in the platform you already run.
A tech fails a phishing knowledge check on Tuesday. Their manager hears about it at the next one-on-one, if someone remembers to pull the report. By then, the best moment to coach has passed.
When a training event happens, such as failing a knowledge check or completing a course, the follow-up is often manual. A manager gets a nudge, a client record gets updated, a ticket gets closed by hand. None of it is hard work, but it all depends on someone noticing at the right time.
If your MSP already runs an automation platform, it can do the noticing for you. Empath webhooks give it the signal, so you can automate employee training follow-up with the tools you already use.
A webhook is a small, automatic message one system sends to another when something happens. Empath sends a signed one for each training event, and your platform decides what comes next.
The rest of this article shows what you can build with it.
Because no two MSPs automate the same way. Some run everything through Rewst. Some build in n8n or Power Automate. Some have a homegrown endpoint that does exactly what their team needs, and smaller teams might lean on a general-purpose tool like Zapier or Make.
A fixed, point-to-point integration can only fit one shop. Everyone else keeps handling training follow-up by hand, usually by whoever has a spare minute.
Empath webhooks start from the stack you already have. When something happens in Empath Learn, Empath sends a signed event to the address you choose, and your automation platform takes it from there. That could mean changing access in Entra, creating a coaching task for a manager, updating a client's compliance log, posting to Teams, or opening and closing a ticket in your PSA.
You build the integration that fits how your MSP works.
If you only want people notified, Slack needs no automation platform: paste a Slack incoming webhook URL into Empath, and it formats the message for you. Slack posts the update, and someone still acts on it.
Empath's job ends at sending a reliable, signed event. Everything after that happens in your automation platform.
You choose which events a webhook listens for. There are four today:
Each event is sent as soon as it happens, never held for the email digest. It's signed, so your platform can confirm it came from Empath before acting on it.
Any tool that can receive a webhook can receive an Empath event, and your PSA fits in through that platform. A PSA needs something in the middle to turn an event into a ticket on the right board.
Each event says what happened and identifies the person and the course or knowledge check involved. It doesn't include a manager, client, or due date. Your platform adds that context with your own rules, so the automation works the way your MSP does.
The person's email and name are included only when you turn on personal details for the webhook. Most identity and PSA lookups need the email, so turn it on for those workflows. The same setting controls whether names appear in Slack messages. Slack doesn't check Empath's signature, so keep the channel private if messages include names.
These are examples of what MSPs can build in their own automation platform. The exact steps depend on your tools and how your team and clients are set up.
Unlock access when onboarding training is done. When a new hire completes your required security onboarding course, your platform can look them up in Entra by email and add them to the group that grants access to line-of-business apps. Training becomes a control, not a report.
Turn a failed check into a coaching task. When someone fails a knowledge check, your platform can create a coaching task for their manager or send the manager a Teams message with the course name. Follow up while the material is still fresh. If you've already decided who owns training follow-up, this puts that decision into practice without anyone remembering to.
Keep audit records current. On each completion, your platform can add a row to a per-client list or spreadsheet, or record the training date on the contact in IT Glue or Hudu. When a cyber insurance questionnaire or QBR comes around, the record is already there.
Announce new training once. When a course or learning pathway goes live, send one message to the company channel instead of having someone email the team.
Open and close PSA tickets. If your team runs on tickets, your platform can open one on your training board when a course is assigned and close it when the course is completed. This works with ConnectWise, Autotask, HaloPSA, or Syncro through your automation platform. The assigned event doesn't include a due date, so set one in your workflow. For teams that already keep training in the ticket flow, this keeps those tickets current without manual updates.
Webhooks follow your company's settings, and individual inbox preferences don't affect them. That's what makes them dependable enough to build automations on.
A tech who unsubscribes from training emails still generates events. So does a company that pauses all notifications during a busy week. Unticking email or bell alerts for a notification type doesn't stop webhooks either. Whether a webhook sends depends on whether webhook delivery is on for your company and which events it subscribes to.
When a delivery fails, Empath tries again, up to four attempts per event. Each webhook shows a health label so you can see how it's doing at a glance:
When a webhook turns Unhealthy, managers and admins get an email and a bell notification, as long as webhook and account alerts are switched on. Empath keeps trying the endpoint; it doesn't switch the webhook off. One successful delivery puts it back to Healthy.
Events that failed every attempt aren't resent, so a broken receiver can leave gaps. After you fix it, check recent assignments and completions in Empath to catch up on anything your system missed.
You don't need all four events on day one. Pick the one follow-up your team still handles manually, whether that's coaching after a failed check or updating records after a completion, and automate that first.
To see the full set of jobs webhooks can handle, read What Empath webhooks are for in the Herd Help Hub. When you're ready to build, start with Before you start and the Go-live checklist, then set up your first webhook in three steps: Endpoint, Events, and Review & test. The test sends a sample event, so you can build your workflow against the real payload before going live.
Want to see how webhooks could fit your automations? Book a demo.