Missing Github Trigger Webhook Events

Feature Requests
1

The idea

I noticed that the GitHub Trigger node doesn’t expose quite a few webhook events that GitHub supports. The current list covers the common ones like push, pull_request, issues, release, etc., but there are a number of newer events that aren’t available.

Some examples include:

  • CI/CD: workflow_run or workflow_job
  • Community & Collaboration: discussion, discussion_comment
  • Security & Admin: code_scanning_alert, dependabot_alert, secret_scanning_alert, repository_ruleset
  • Package & Registry: registry_package

These are just a few examples though. I’m not specifically asking for all of these to be added. I was more curious to hear what the community thinks is missing from the GitHub Trigger node and which webhook events would be the most valuable to support.

Personally, the CI/CD events seem like the most impactful place to start. GitHub Actions is widely used now, and being able to react to events like workflow_run, workflow_job, or merge_group, or something else would make it much easier to build GitHub-native automation in n8n. But I’d love to hear if there are other events people have been wishing for.

My use case

I don’t have one specific workflow that’s blocked right now. I came across this while setting up some GitHub automation and noticed the gap in the available trigger events.

Some examples that come to mind are sending notifications on Slack when a deployment workflow fails, triggering a follow-up workflow after a GitHub Actions run succeeds, with an approval step in Slack or Telegram before continuing, automating merge queue workflows, or reacting to activity in GitHub Discussions. I’m sure there are plenty of other use cases depending on how people use GitHub.

I think it would be beneficial to add this because

  1. GitHub has continued to add new webhook events over the years, but the GitHub Trigger node hasn’t kept up with all of them.

  2. GitHub Actions has become the default CI platform for many projects, so support for CI/CD-related events would benefit a large number of users.

  3. Merge queues are becoming more common, especially in larger open source repositories. Supporting related events would make it easier to automate workflows around them.

  4. There maybe people in fields of CI/CD and Github Actions or DevOps with their own use case (another reason to open this thread is to know different and unique use cases of of different people)

  5. It would make the GitHub Trigger node more complete and reduce the need to fall back to a generic Webhook node for newer GitHub features.

I’m interested in hearing which events the community would find the most useful.

Any resources to support this?

Are you willing to work on this?

Yes. I’d be happy to contribute a PR for whichever webhook events the community feels would be the most useful. If there seems to be broad interest in the CI/CD events, those would probably be my starting point, I guess.