Do you find yourself logging into Flexible User License just to check whether a license was automatically revoked, whether your user count is creeping toward its limit, or whether an API key has expired?
For an admin, that's a surprisingly tedious habit to maintain. License automation keeps running quietly in the background, but checking the results still means someone has to open the app and look. If the person responsible is out for a few days, events go unnoticed; an API key can quietly become invalid, silently halting an automation rule for days before anyone realizes it.
The fix turns out to be simple: let Flexible User License do the checking, and have it deliver the results to the collaboration tool your team already uses. That's exactly what the Webhooks feature introduced here does. It sends license automation events and API status events as notification messages to a Slack or Microsoft Teams channel.
TL;DR: Connect a Flexible User License webhook, and events like license revocation, user-limit warnings, and API key expiration show up directly in your Slack or Teams channel โ no need to open the app at all.
Events You Can Receive via Flexible User License Webhooks
Broadly speaking, webhooks cover two kinds of events.
License automation events
Automated license revocation: Sent immediately when a license is automatically revoked
License user count exceeds the set limit: Sent once per day when licensed users exceed 75% of the configured limit
API information events
Organization API Key & API Token is invalid: Sent once per day when the registered Organization API Key or API Token becomes invalid
The real point here is when you get notified. You can schedule notifications by day of week and time window, so if you set it to only alert during business hours, you'll never be woken up by a 3 a.m. ping. On top of that, timing varies by event type: something that needs an immediate response โ like a license revocation โ arrives the moment it happens, while events you can plan around, like a user-count warning or an invalid API key, are batched into a single notification per day.
Setting Up Slack & Teams Webhooks
Setup is just two steps: generate an Incoming Webhook URL from a Slack or Teams channel, then register that URL in Flexible User License.
1. Generate an Incoming Webhook URL for the channel that should receive alerts, in Slack or Teams.
2. In Flexible User License, go toย Settings > Webhooks, click Create webhook, and set the URL along with the events, notification language, and schedule you want.
3. Click Test connection to confirm a test message arrives, then click Save.
No development work required โ the whole setup is about as much effort as creating a channel and pasting in a URL. Want to pause notifications later? Just flip the Enabled toggle off instead of deleting the webhook. Need to change the channel or events? Reopen the saved webhook and edit it.
๐ก Screen-by-screen steps differ slightly between Slack and Teams โ check the user guide for screenshots of each.ย
๐ Using Webhooks with Slack ยท Using Webhooks with Teams
๐ก Just keep the Webhook URL private; don't share it externally or upload it to a public repository.
Here's What Arrives in the Channel
Let's walk through what an actual notification looks like when it lands in a Slack channel.
When a license is automatically revoked, the channel receives a notification that lays out the site, rule name, result, and number of revoked users at a glance. If the same rule fires more than once, the notifications stack up in order, and each one comes with Action details and Open in Flexible User License buttons โ one click takes you to the full details or straight into the app.
When your user count gets close to the limit, you'll see a notification like this. Current usage and the configured limit are shown side by side as numbers, along with a usage bar โ so you know exactly how much headroom is left at a glance.
๐ก Pro tip: Because the site, result, and revoked-user count all arrive as clearly labeled fields, no one has to log in to check the details โ a glance at the channel message tells you exactly what happened, where, and how many times.
What You Gain from Webhooks
Webhook integration is more than "one more notification channel."ย
It cuts the operational load of admins having to check the app themselves, and it creates a shared awareness across the whole team. Here's the summary in four points.
Wrapping Up
The next step for license automation, we think, isn't just "things get handled automatically" โ it's "the results don't need to be hunted down by a human at all."ย
Webhook integration is what fills in that last step. Connect it to the Slack or Teams channel your team already uses โ it only takes a few minutes โ and license revocations, user-count warnings, and API key issues will surface naturally, without ever opening the app.
If your organization has ever been caught off guard by a missed license event, we'd recommend connecting just one channel in Flexible User License's Webhooks settings today.
๐ย Try Flexible User License for Jira for free
๐ Try Flexible User License for Confluence for free
Do you find yourself logging into Flexible User License just to check whether a license was automatically revoked, whether your user count is creeping toward its limit, or whether an API key has expired?
For an admin, that's a surprisingly tedious habit to maintain. License automation keeps running quietly in the background, but checking the results still means someone has to open the app and look. If the person responsible is out for a few days, events go unnoticed; an API key can quietly become invalid, silently halting an automation rule for days before anyone realizes it.
The fix turns out to be simple: let Flexible User License do the checking, and have it deliver the results to the collaboration tool your team already uses. That's exactly what the Webhooks feature introduced here does. It sends license automation events and API status events as notification messages to a Slack or Microsoft Teams channel.
Events You Can Receive via Flexible User License Webhooks
Broadly speaking, webhooks cover two kinds of events.
License automation events
Automated license revocation: Sent immediately when a license is automatically revoked
License user count exceeds the set limit: Sent once per day when licensed users exceed 75% of the configured limit
API information events
Organization API Key & API Token is invalid: Sent once per day when the registered Organization API Key or API Token becomes invalid
The real point here is when you get notified. You can schedule notifications by day of week and time window, so if you set it to only alert during business hours, you'll never be woken up by a 3 a.m. ping. On top of that, timing varies by event type: something that needs an immediate response โ like a license revocation โ arrives the moment it happens, while events you can plan around, like a user-count warning or an invalid API key, are batched into a single notification per day.
Setting Up Slack & Teams Webhooks
Setup is just two steps: generate an Incoming Webhook URL from a Slack or Teams channel, then register that URL in Flexible User License.
1. Generate an Incoming Webhook URL for the channel that should receive alerts, in Slack or Teams.
2. In Flexible User License, go toย Settings > Webhooks, click Create webhook, and set the URL along with the events, notification language, and schedule you want.
3. Click Test connection to confirm a test message arrives, then click Save.
No development work required โ the whole setup is about as much effort as creating a channel and pasting in a URL. Want to pause notifications later? Just flip the Enabled toggle off instead of deleting the webhook. Need to change the channel or events? Reopen the saved webhook and edit it.
Here's What Arrives in the Channel
Let's walk through what an actual notification looks like when it lands in a Slack channel.
When a license is automatically revoked, the channel receives a notification that lays out the site, rule name, result, and number of revoked users at a glance. If the same rule fires more than once, the notifications stack up in order, and each one comes with Action details and Open in Flexible User License buttons โ one click takes you to the full details or straight into the app.
When your user count gets close to the limit, you'll see a notification like this. Current usage and the configured limit are shown side by side as numbers, along with a usage bar โ so you know exactly how much headroom is left at a glance.
What You Gain from Webhooks
Webhook integration is more than "one more notification channel."ย
It cuts the operational load of admins having to check the app themselves, and it creates a shared awareness across the whole team. Here's the summary in four points.
Wrapping Up
The next step for license automation, we think, isn't just "things get handled automatically" โ it's "the results don't need to be hunted down by a human at all."ย
Webhook integration is what fills in that last step. Connect it to the Slack or Teams channel your team already uses โ it only takes a few minutes โ and license revocations, user-count warnings, and API key issues will surface naturally, without ever opening the app.
If your organization has ever been caught off guard by a missed license event, we'd recommend connecting just one channel in Flexible User License's Webhooks settings today.
๐ย Try Flexible User License for Jira for free
๐ Try Flexible User License for Confluence for free