Event listeners Webhook Listeners are groovy scripts which are executed when a specific event(s) are executed within FlexDeploy. Each event listener Webhook Listener is associated with one or more event types and more than one event listener can be executed on one event execution.
...
multiple Listeners can be listening to the same event. For example you could have one Listener that sends a Slack notification and another that sends an email for the ‘Workflow Completed’ event.
View Webhook Listeners
Access event listeners by navigating to Administration → Integrations → EventsOutgoing Webhooks.
...
Creating/Editing
...
Webhook Listeners
To create a new event listenerWebhook Listener, click the [insert button pic here] button Create Listener button. To view or edit a event listenerWebhook Listener, click on the name of the event listener.
Field | Description |
|---|---|
Name | The name of the listener |
Description | The description of the listener |
Active | Whether or not the listener is active (Defaults to Yes) |
Events | The events you want your listener to subscribe to |
Groovy Script
The groovy script for the listener will be executed when a corresponding even type is executed within FlexDeploy. The editing window has capabilities for undo, redo, find, find and replaereplace, and go to line. There are a variety of context variables and methods available to use in this script. Type ‘Ctrl + space’ in the editor for suggestions on variables and methods that can be used. See more example examples of listeners on our Sample Event Listeners page.
...
Filter
Event listeners Webhook Listeners also allow you to filter which events that the listener will process by using groovy script. The groovy script will return true when the listener should process the event and false otherwise. You are able to use all of the Event Context Variables and Methods that can be used in the event listener groovy script. This allows the filter to be very robust and ___ your listener to only process the exact events that you want. For example, you can specify that you want your workflow completed listener to only process a workflow that has failed a deployment on your Dev environment and ignore all other workflow events.
...