Skip to main content

GitHub Webhook Plugin (Enterprise)

GitHub Webhook Plugin (Enterprise)

Available in PagerDuty Process Automation Commercial products.

This plugin provides simplified integration with Github Webhooks and includes support for the confirmation ping event. When a new webhook is setup in GitHub a ping event is sent to confirm the webhook. The Rundeck Github Webhook will receive the ping event and return a success response, but will not run the related jobs. The jobs will only run for valid events configured on the webhook.

This plugin expects the payload from GitHub to be JSON


Create a webhook in Rundeck and choose GitHub Webhook as the event plugin.

The job property is the only required property.

All other properties may be supplied with data substitutions. See the following examples for details.

Data substitution examples

Example raw payload

  "action": "created",
  "issue": {
    "url": "",
    "repository_url": "",
    "labels_url": "{/name}",
    "comments_url": "",
    "events_url": "",
    "html_url": "",
    "id": 486590337,
    "node_id": "MDU6SXNzdWU0ODY1OTAzMzc=",
    "number": 1,
    "title": "Webhook test",
    "user": {
      "login": "youraccount",
  "repository": {
    "name": "YourProject",

-repo ${} -action ${data.action} -issue_title ${data.issue.title}

You can also get the following webhook context properties:

#a uniquely generated id for the webhook event

#the project that owns the webhook

#the ip that sent the event

#epoch timestamp when event was received

#GitHub payload signature

#GitHub event type

#GitHub delivery

Raw payload

To send the raw payload to your job you can pass it like this:

-githubraw ${raw}

GitHub Secret

If you want to validate the payloads that GitHub is sending, you can configure the GitHub secret in your webhook configuration. If you add the secret, every payload received by the webhook will validate the payload using the secret.