# Support GitHub Apps as Credential for GitHub Trigger Node

**URL:** <https://community.n8n.io/t/support-github-apps-as-credential-for-github-trigger-node/159117>\
**Category:** Feature Requests\
**Tags:** node, github-trigger\
**Created:** [July 30, 2025, 12:52pm UTC](https://community.n8n.io/t/support-github-apps-as-credential-for-github-trigger-node/159117 "2025-07-30T12:52:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pete.praewpun](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/pete.praewpun/32/105348_2.png) [@pete.praewpun](https://community.n8n.io/u/pete.praewpun)\
**Post date:** [July 30, 2025, 12:52pm UTC](https://community.n8n.io/t/support-github-apps-as-credential-for-github-trigger-node/159117/1 "2025-07-30T12:52:13Z")

</div>

## The idea is:

Add support for using GitHub Apps as a credential option for the GitHub Trigger node in n8n. Currently, the node only allows authentication via OAuth apps or personal access tokens, but not GitHub Apps.

## My use case:

My organization uses GitHub Apps for automation and integrations due to their improved security and granular permission management. We want to trigger n8n workflows based on GitHub events, but are unable to use GitHub Apps as a credential method with the current GitHub Trigger node. This limits us to using less secure or less manageable authentication methods.

## I think it would be beneficial to add this because:

Supporting GitHub Apps would allow organizations to follow best practices for security and access control. It would also make n8n more flexible and enterprise-friendly, enabling more teams to integrate it into their GitHub-based workflows.

## Any resources to support this?

- [About authentication with a GitHub App](https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/about-authentication-with-a-github-app)

- [About creating GitHub Apps](https://docs.github.com/en/apps/creating-github-apps/about-creating-github-apps/about-creating-github-apps)

## Are you willing to work on this?

I am not able to contribute code at this time, but I am happy to provide feedback or help with testing.

---

<div class="post-metadata">

**Author:** ![ivser](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ivser/32/188030_2.png) [@ivser](https://community.n8n.io/u/ivser)\
**Post date:** [September 10, 2026, 10:26am UTC](https://community.n8n.io/t/support-github-apps-as-credential-for-github-trigger-node/159117/2 "2026-09-10T10:26:53Z")

</div>

I second this feature request. Github recommends using GitHub Apps over OAuth apps (which are currently supported in N8N) for a number of reasons and it would be really great if it was supported.

Looks like a feature request for this has been submitted as a the Github issue years ago, but the requestor has been recommended to move it to this forum:

> <https://github.com/n8n-io/n8n/issues/32886>
>
> \## Is your feature request related to a problem?
> 
> n8n Source Control (Environmen…ts) currently authenticates to the Git remote with either an \*\*SSH deploy key\*\* or \*\*HTTPS username/password\*\*. For HTTPS, the password is a static token (PAT). Static tokens have two problems for org-managed deployments:
> 
> 1. \*\*They expire.\*\* When a static HTTPS token expires, source control breaks — and per #28311 an expired token can even \*\*prevent n8n from starting after a restart\*\*. Someone has to manually rotate the secret.
> 2. \*\*They're coarse / long-lived.\*\* PATs are tied to a user account and are broadly scoped; SSH deploy keys are per-repo but are long-lived static secrets with no built-in rotation.
> 
> For organizations syncing workflows to GitHub, a \*\*GitHub App\*\* is the standard, recommended auth model: org-installable, fine-grained repo permissions, and \*\*short-lived installation access tokens (~1h) that are minted on demand\*\* rather than stored long-term.
> 
> \## Describe the solution you'd like
> 
> Add a third source-control connection type for \*\*GitHub App\*\* authentication. n8n would store the App credentials (App ID, Installation ID, App private key) encrypted in the existing source-control settings, and \*\*mint a fresh installation access token at git-client initialization\*\*, feeding it into the Git remote over HTTPS.
> 
> This fits the existing architecture with minimal new plumbing:
> 
> \- The HTTPS path already injects credentials via a git \`credential.helper\` (\`username\` / \`password\`). A GitHub App installation token slots straight in as \`username=x-access-token\`, \`password=\<installation-token\>\`.
> \- The git client is already rebuilt per operation, so minting the token at init avoids any long-lived refresh daemon — and the ~1h TTL is never a problem because every operation gets a fresh token.
> \- Encrypted secret storage already exists (SSH key + HTTPS creds use the same \`Cipher\` + Settings pattern); the App private key would reuse it.
> 
> Sketch of the changes: extend the \`connectionType\` enum (\`'ssh' | 'https'\` → add \`'github\_app'\`), add App fields to the preferences DTO/service, and in the git service mint the installation token (JWT signed with the App key → \`POST /app/installations/{id}/access\_tokens\`) before building the existing HTTPS credential helper. Plus a settings-UI form for the App credentials.
> 
> \## Describe alternatives you've considered
> 
> \- \*\*Static HTTPS PAT\*\* (works today) — but expires and breaks sync/startup (#28311), and needs manual rotation.
> \- \*\*SSH deploy key\*\* (works today) — long-lived static secret, no rotation, per-repo management overhead at org scale.
> \- A GitHub App's auto-refreshed installation tokens avoid both: no stored long-lived credential to leak, automatic expiry/rotation, and fine-grained org-level control.
> 
> \## Additional context
> 
> Directly addresses the failure mode in #28311 (expired HTTPS token blocks startup) — installation tokens are minted fresh per operation, so there's no static token to expire.

---

<div class="post-metadata">

**Author:** ![ivser](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ivser/32/188030_2.png) [@ivser](https://community.n8n.io/u/ivser)\
**Post date:** [September 10, 2026, 10:47am UTC](https://community.n8n.io/t/support-github-apps-as-credential-for-github-trigger-node/159117/3 "2026-09-10T10:47:33Z")

</div>

Nevermind, I just realized that this capability has already been added to a newer version (2.29) that I’m running.
