Skip to main content




Webhooks are an industry standard way for internet applications to communicate with each other. Rundeck Webhooks are an entry point to automation with Rundeck. A Webhook can be configured to accept incoming payloads and trigger Rundeck Job(s). Webhook events are handled by Webhook Event Rundeck plugins.

Webhook Administration

Released in version 4.0

Click on Webhooks to go to the webhook administration page to add, configure, and remove webhooks for a project.

Webhook Administration
Webhook Administration

The Webhook API or using the rd cli tool can also manage webhooks.

Webhook HTTP Authorization String

Webhooks have an an optional HTTP Authorization String feature, when used, can increase the the security of the webhook. To enable the feature check the Use Authorization Heeader box when creating or editing a webhook. When the Webhook is saved a box will be shown below the check box with the Authorization string assigned to the webhook. Note: This will only be shown once! After navigating away from the webhook it will no longer be visible.

Include the string as an Authorization header when making a call to the webhook.

curl --location --request POST 'http://your.rundeck.domain:4440/api/40/webhook/wvNE6e1R06eqCQSl5jwXgXy3IUgt5vxS#Advanced_Webhook' \
--header 'Authorization: the-authorization-string' \
--header 'Content-Type: application/json' \
--data-raw '{
    "messages": {
        "field1": "value1",
        "sub1": {
            "subfield": "subval"

It is possible to regenerate the Authorization String by clicking the Regenerate button on the Webhook. The new value will be displayed after saving.

Webhook Handlers

Webhook Event Handlers are custom handlers that can be developed as Rundeck Plugins to interact with external systems. They can respond to authentication calls, pre-process inputs, and provide configuration defaults for specific systems.

Rundeck includes the following Webhook Handlers:

For a full tutorial on creating a Webhook follow our How To Use Webhooks guide.

Webhook Tips


Please note that after the webhook has been created, it is not possible to change the Webhook User. This field will become read only.


When configuring a user on a Webhook ensure that the user has logged into Rundeck at least once. If the user has never logged in to Rundeck before a validation error will occur saying that the user cannot be found. Once that users logs in one time it is possible to specify the user in the webhook form.

Webhook Debugging

“Why didn’t my webhook do X?!”

Process Automation includes a Webhook Debugger integrated with the Webhook builder. The Debugger makes troubleshooting incoming webhooks and why they did (or did not) trigger certain rules in the Advanced Rule Processing Handlers.

Debug Panel
Debug Panel

Alternatively, use the configuration below to send events and log messages generated by the webhook activity to the $RD_LOGS_DIR/rundeck.webhooks.log file.

Default log4j configuration,webhook

log4j.appender.webhook.layout.ConversionPattern=[%d{ISO8601}] %-5p %c{2} - %m%n

Disable Webhooks


Webhooks are on by default as of 3.2.0. They can be disabled by following the following instructions.


To disable the use of webhooks for your Rundeck server add the following configuration property to your or equivalent.



Set the following environment variable: