n8n
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
- 211k
- TypeScript
- 3 h ago
GitHub Action for creating a GitHub App Installation Access Token
Repo actions/create-github-app-token, read from GitHub 1 min ago. actions has not joined Take My Repo.
actions/create-github-app-token is a public repo on GitHub by actions. GitHub Action for creating a GitHub App Installation Access Token. It declares the MIT license on GitHub. It is written mainly in JavaScript, has 920 stars and last changed on 2026-11-18. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-19.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
GitHub Action for creating a GitHub App installation access token.
In order to use this action, you need to:
APP_CLIENT_ID).APP_PRIVATE_KEY).Important
An installation access token expires after 1 hour. Please see this comment for alternative approaches if you have long-running processes.
name: Run tests on staging on: push: branches: - main jobs: hello-world: runs-on: ubuntu-latest steps: - uses: actions/create-github-app-token@v3 id: app-token with: client-id: ${{ vars.APP_CLIENT_ID }} private-key: ${{ secrets.APP_PRIVATE_KEY }} - uses: ./actions/staging-tests with: token: ${{ steps.app-token.outputs.token }}
actions/checkouton: [pull_request] jobs: auto-format: runs-on: ubuntu-latest steps: - uses: actions/create-github-app-token@v3 id: app-token with: # required client-id: ${{ vars.APP_CLIENT_ID }} private-key: ${{ secrets.APP_PRIVATE_KEY }} - uses: actions/checkout@v6 with: token: ${{ steps.app-token.outputs.token }} ref: ${{ github.head_ref }} # Make sure the value of GITHUB_TOKEN will not be persisted in repo's config persist-credentials: false - uses: creyD/prettier_action@v6 with: github_token: ${{ steps.app-token.outputs.token }}
on: [pull_request] jobs: auto-format: runs-on: ubuntu-latest steps: - uses: actions/create-github-app-token@v3 id: app-token with: # required client-id: ${{ vars.APP_CLIENT_ID }} private-key: ${{ secrets.APP_PRIVATE_KEY }} - name: Get GitHub App User ID id: get-user-id run: echo "user-id=$(gh api "/users/${{ steps.app-token.outputs.app-slug }}[bot]" --jq .id)" >> "$GITHUB_OUTPUT" env: GH_TOKEN: ${{ steps.app-token.outputs.token }} - id: committer run: echo "string=${{ steps.app-token.outputs.app-slug }}[bot] <${{ steps.get-user-id.outputs.user-id }}+${{ steps.app-token.outputs.app-slug }}[bot]@users.noreply.github.com>" >> "$GITHUB_OUTPUT" - run: echo "committer string is ${{ steps.committer.outputs.string }}"
on: [pull_request] jobs: auto-format: runs-on: ubuntu-latest steps: - uses: actions/create-github-app-token@v3 id: app-token with: # required client-id: ${{ vars.APP_CLIENT_ID }} private-key: ${{ secrets.APP_PRIVATE_KEY }} permission-contents: write - name: Get GitHub App User ID id: get-user-id run: echo "user-id=$(gh api "/users/${{ steps.app-token.outputs.app-slug }}[bot]" --jq .id)" >> "$GITHUB_OUTPUT" env: GH_TOKEN: ${{ steps.app-token.outputs.token }} - run: | git config --global user.name '${{ steps.app-token.outputs.app-slug }}[bot]' git config --global user.email '${{ steps.get-user-id.outputs.user-id }}+${{ steps.app-token.outputs.app-slug }}[bot]@users.noreply.github.com' gh auth setup-git env: GH_TOKEN: ${{ steps.app-token.outputs.token }} # Git commands like commit and push work using the bot user - run: | git add . git commit -m "Auto-generated changes" git push
Tip
The <BOT USER ID> is the numeric user ID of the app's bot user, which can be found under https://api.github.com/users/<app-slug>%5Bbot%5D.
For example, we can check at https://api.github.com/users/dependabot[bot] to see the user ID of Dependabot is 49699333.
Alternatively, you can use the octokit/request-action to get the ID.
on: [workflow_dispatch] jobs: hello-world: runs-on: ubuntu-latest steps: - uses: actions/create-github-app-token@v3 id: app-token with: client-id: ${{ vars.APP_CLIENT_ID }} private-key: ${{ secrets.APP_PRIVATE_KEY }} owner: ${{ github.repository_owner }} - uses: peter-evans/create-or-update-comment@v4 with: token: ${{ steps.app-token.outputs.token }} issue-number: ${{ github.event.issue.number }} body: "Hello, World!"
on: [issues] jobs: hello-world: runs-on: ubuntu-latest steps: - uses: actions/create-github-app-token@v3 id: app-token with: client-id: ${{ vars.APP_CLIENT_ID }} private-key: ${{ secrets.APP_PRIVATE_KEY }} owner: ${{ github.repository_owner }} repositories: | repo1 repo2 - uses: peter-evans/create-or-update-comment@v4 with: token: ${{ steps.app-token.outputs.token }} issue-number: ${{ github.event.issue.number }} body: "Hello, World!"
You can include the current repository in the list with ${{ github.repository }}:
repositories: ${{ github.repository }},repo2
on: [issues] jobs: hello-world: runs-on: ubuntu-latest steps: - uses: actions/create-github-app-token@v3 id: app-token with: client-id: ${{ vars.APP_CLIENT_ID }} private-key: ${{ secrets.APP_PRIVATE_KEY }} owner: another-owner - uses: peter-evans/create-or-update-comment@v4 with: token: ${{ steps.app-token.outputs.token }} issue-number: ${{ github.event.issue.number }} body: "Hello, World!"
on: [workflow_dispatch] jobs: hello-world: runs-on: ubuntu-latest steps: - uses: actions/create-github-app-token@v3 id: app-token with: client-id: ${{ vars.APP_CLIENT_ID }} private-key: ${{ secrets.APP_PRIVATE_KEY }} enterprise: my-enterprise-slug - name: Call enterprise management REST API with gh run: | gh api /enterprises/my-enterprise-slug/apps/installable_organizations env: GH_TOKEN: ${{ steps.app-token.outputs.token }}
Note
Selected permissions must be granted to the specified app installation. Setting a permission that the installation does not have will result in an error.
on: [issues] jobs: hello-world: runs-on: ubuntu-latest steps: - uses: actions/create-github-app-token@v3 id: app-token with: client-id: ${{ vars.APP_CLIENT_ID }} private-key: ${{ secrets.APP_PRIVATE_KEY }} owner: ${{ github.repository_owner }} permission-issues: write - uses: peter-evans/create-or-update-comment@v4 with: token: ${{ steps.app-token.outputs.token }} issue-number: ${{ github.event.issue.number }} body: "Hello, World!"
You can use a matrix strategy to create tokens for multiple user or organization accounts.
Note
See this documentation for information on using multiline strings in workflows.
on: [workflow_dispatch] jobs: set-matrix: runs-on: ubuntu-latest outputs: matrix: ${{ steps.set.outputs.matrix }} steps: - id: set run: echo 'matrix=[{"owner":"owner1"},{"owner":"owner2","repos":["repo1"]}]' >>"$GITHUB_OUTPUT" use-matrix: name: "@${{ matrix.owners-and-repos.owner }} installation" needs: [set-matrix] runs-on: ubuntu-latest strategy: matrix: owners-and-repos: ${{ fromJson(needs.set-matrix.outputs.matrix) }} steps: - uses: actions/create-github-app-token@v3 id: app-token with: client-id: ${{ vars.APP_CLIENT_ID }} private-key: ${{ secrets.APP_PRIVATE_KEY }} owner: ${{ matrix.owners-and-repos.owner }} repositories: ${{ join(matrix.owners-and-repos.repos) }} - uses: octokit/request-action@v2.x id: get-installation-repositories with: route: GET /installation/repositories env: GITHUB_TOKEN: ${{ steps.app-token.outputs.token }} - run: echo "$MULTILINE_JSON_STRING" env: MULTILINE_JSON_STRING: ${{ steps.get-installation-repositories.outputs.data }}
on: [push] jobs: create_issue: runs-on: self-hosted steps: - name: Create GitHub App token id: create_token uses: actions/create-github-app-token@v3 with: client-id: ${{ vars.GHES_APP_CLIENT_ID }} private-key: ${{ secrets.GHES_APP_PRIVATE_KEY }} owner: ${{ vars.GHES_INSTALLATION_ORG }} github-api-url: ${{ vars.GITHUB_API_URL }} - name: Create issue uses: octokit/request-action@v2.x with: route: POST /repos/${{ github.repository }}/issues title: "New issue from workflow" body: "This is a new issue created from a GitHub Action workflow." env: GITHUB_TOKEN: ${{ steps.create_token.outputs.token }}
This action relies on Node.js native proxy support.
If you set HTTP_PROXY or HTTPS_PROXY, also set NODE_USE_ENV_PROXY: "1" on the action step so Node.js honors those variables. If you need proxy bypass rules, set NO_PROXY alongside them.
- uses: actions/create-github-app-token@v3 id: app-token env: HTTPS_PROXY: http://proxy.example.com:8080 NO_PROXY: github.example.com NODE_USE_ENV_PROXY: "1" with: client-id: ${{ vars.APP_CLIENT_ID }} private-key: ${{ secrets.APP_PRIVATE_KEY }}
client-id or app-idRequired: GitHub App Client ID.
Note
The legacy app-id input is also accepted, but client-id is recommended.
private-keyRequired: GitHub App private key. Escaped newlines (\\n) will be automatically replaced with actual newlines.
Some other actions may require the private key to be Base64 encoded. To avoid recreating a new secret, it can be decoded on the fly, but it needs to be managed securely. Here is an example of how this can be achieved:
steps: - name: Decode the GitHub App Private Key id: decode run: | private_key=$(echo "${{ secrets.APP_PRIVATE_KEY }}" | base64 -d | awk 'BEGIN {ORS="\\n"} {print}' | head -c -2) &> /dev/null echo "::add-mask::$private_key" echo "private-key=$private_key" >> "$GITHUB_OUTPUT" - name: Generate GitHub App Token id: app-token uses: actions/create-github-app-token@v3 with: client-id: ${{ vars.APP_CLIENT_ID }} private-key: ${{ steps.decode.outputs.private-key }}
ownerOptional: The owner of the GitHub App installation. If empty, defaults to the current repository owner.
repositoriesOptional: Comma or newline-separated list of repositories to grant access to.
Note
If owner is set explicitly and repositories is empty, access will be scoped to all repositories in the provided repository owner's installation. If owner and repositories are empty, access will be scoped to only the current repository.
Repository entries may include an owner, for example owner/repo1. The owner portion must match the owner input, or the current repository owner if owner is unset.
enterpriseOptional: The slug of the enterprise account to generate a token for an enterprise installation.
Note
The enterprise input is mutually exclusive with owner and repositories. Use it when the GitHub App is installed on an enterprise account. Enterprise installation tokens can call enterprise APIs, but do not grant organization or repository access.
permission-<permission name>Optional: The permissions to grant to the token. By default, the token inherits all of the installation's permissions. We recommend to explicitly list the permissions that are required for a use case. This follows GitHub's own recommendation to control permissions of GITHUB_TOKEN in workflows. The documentation also lists all available permissions, just prefix the permission key with permission- (e.g., pull-requests → permission-pull-requests).
The reason we define one permision-<permission name> input per permission is to benefit from type intelligence and input validation built into GitHub's action runner.
skip-token-revokeOptional: If true, the token will not be revoked when the current job is complete.
github-api-urlOptional: The URL of the GitHub REST API. Defaults to the URL of the GitHub Rest API where the workflow is run from.
tokenGitHub App installation access token.
installation-idGitHub App installation ID.
app-slugGitHub App slug.
The action creates an installation access token using the POST /app/installations/{installation_id}/access_tokens endpoint.
The token target depends on the inputs: enterprise creates a token for an enterprise installation, owner without repositories creates a token for all repositories in the owner's installation, repositories scopes the token to those repositories, and no target inputs scopes the token to the current repository.
token which can be used in subsequent steps.skip-token-revoke input is set to true, the token is revoked in the post step of the action, which means it cannot be passed to another job.Note
Installation permissions can differ from the app's permissions they belong to. Installation permissions are set when an app is installed on an account. When the app adds more permissions after the installation, an account administrator will have to approve the new permissions before they are set on the installation.
actions/create-github-app-token is a public repo on GitHub by actions. GitHub Action for creating a GitHub App Installation Access Token.
It declares the MIT license on GitHub.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-11-18. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.

Run your GitHub Actions locally 🚀

why use many token when few token do trick. Skill + local proxy for coding agents: shorter answers, smaller tool output, every original recoverable.
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.
Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD

Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Kubernetes controller for GitHub Actions self-hosted runners


This page is also available as structured data, with the same sources and dates.
Take My Repo has not tested this on your machine. Requirements come from the project's own documentation.