Using Webhooks with Slack
The Webhooks feature in Flexible User License sends notifications to a configured channel when license automation or API status events occur.
The required URL is a Slack Incoming Webhook URL.
Prerequisites
Before using webhooks, make sure you have the following:
A Slack workspace account
A Slack channel to receive notifications (for example, #appb)
Permission to create Slack apps
Depending on your workspace's security policy, an admin may need to approve the creation of a Slack app or the connection of a webhook. This is because external services gain permissions to perform actions such as posting messages to Slack. If approval is required, contact your Slack workspace admin.
Generate a Webhook URL in Slack
Create a new Slack app, enable Incoming Webhooks, and generate a Webhook URL for the channel where you want to receive notifications.
Go to the Slack API page and sign in.
Click Create New App.
Select From scratch.
On the Name app & choose workspace screen, enter the following:
App Name: Enter a name for the app (for example,
alert-appb).Workspace: Select the Slack workspace where you want to receive notifications.
Click Create App.
On the app's basic information screen, select Incoming Webhooks.
7. Toggle Activate Incoming Webhooks to On.
Scroll down and click Add New Webhook to Workspace to generate a Webhook URL.
Select the Slack channel for webhook notifications.
Click Allow.
Copy the generated Webhook URL and register it in the Flexible User License app.
The generated URL follows this format:
https://hooks.slack.com/services/TXXXXXXXX/BXXXXXXXX/XXXXXXXXXXXXXXXXXXXXXXXX
Anyone who knows the Webhook URL can send messages to that channel. Do not share the URL externally or upload it to a public repository such as GitHub.
Register a Webhook in Flexible User License
Once you have the Webhook URL, register it in Flexible User License. To create a new webhook, click Create webhook. To update an existing webhook, select it from the list.
Log in to your Jira Cloud site.
Go to Apps > Flexible User License in the left sidebar.
Once the Flexible User License app launches, select Settings > Webhooks from the top navigation.
On the Webhooks page, click Create webhook in the upper-right corner.
Fill in the required fields (marked with an asterisk *) in the Create webhook dialog.
Enabled: Toggles the webhook on or off. Use the toggle in the upper-right corner of the screen.
Type: The notification channel type. Select Slack.
Name: A name to identify the webhook. Displayed in the list and in notification messages.
Webhook URL: Paste the Incoming Webhook URL generated from Slack.
Click the Configure an incoming webhook link below the field for instructions on generating a URL.
Language: The language to use for notification messages.
Events: The events for which you want to receive notifications. You can select multiple events.
Schedule: The time window during which notifications are sent.
Events
The events for which you want to receive notifications. Delivery timing varies depending on the event type.
License automation events
Automated license revocation: Sent immediately when a license is automatically revoked, within the configured Schedule window.
License user count exceeds the set limit: Sent once per day when the number of licensed users exceeds 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.
Schedule
Configure the time window during which notifications are delivered.
Always: Receive notifications at any time, regardless of day or time.
Weekdays or custom: Receive notifications only on selected days and within the specified time range (From–To). Notifications outside this window are not sent.
The table below shows when notifications are sent based on the Schedule setting:
Event | Delivery method | Always | Weekdays or custom |
|---|---|---|---|
Automated license revocation | Immediately when event occurs | Sent immediately | Sent immediately if within the configured days and time window |
License user count exceeds the set limit | Once per day | Sent at 9:00 AM | Sent at the configured start time (From) |
Organization API Key & API Token is invalid | Once per day | Sent at 9:00 AM | Sent at the configured start time (From) |
Test the connection and save
Before saving, verify that the connection to Slack is working correctly.
Click Test connection.
Check whether a test message arrives in the connected Slack channel.
Once the test message is successfully received, the Save button becomes active.
Click Save to save your settings.
The Save button remains inactive until Test connection is completed successfully.
Browse the Webhooks Page
Log in to your Jira Cloud site.
Go to Apps > Flexible User License in the left sidebar.
Once the Flexible User License app launches, select Settings > Webhooks from the top navigation.
On the Webhooks page, you can view the list of registered webhooks, create a new webhook, or edit and delete existing webhooks.
The Webhooks page includes the following elements:
Search: Enter part of a name in the search bar above the list to filter results.
Event filter: Filter the list to show only webhooks configured for a specific event.
Name: The webhook name. Click to open the edit screen.
Type: The notification type. Currently, only Slack is supported.
Last Updated: The date the webhook was last modified.
Created by: The user who created the webhook.
Enabled: Toggle the webhook on or off without deleting it.
Actions: Select Delete to delete the webhook.
Edit a Webhook
To update a registered webhook, click its name in the Webhooks list to open the edit screen. You can update the Incoming Webhook URL and any other settings.
To temporarily disable a webhook without deleting it, use the Enabled toggle. When disabled, no notifications are sent regardless of which events occur.
Delete a Webhook
To delete a webhook, click Delete in the Actions column of the Webhooks list.
The Delete button is only active when the webhook is disabled. Toggle Enabled off before deleting.