GitHub integration

Overview

GitHub is the dominant Git hosting and developer collaboration platform. The Automize GitHub connector covers the operations you actually want in automation: repos, issues, pull requests, Actions workflows, releases, commits, branches, and user lookups.

• Regions: GitHub.com is global. Enterprise Cloud customers use the same API. GitHub Enterprise Server (self-hosted) uses a different base URL – configure it per connection if you're on GHES.
• Plans: Free, Pro, Team, Enterprise – all expose the REST API. Some features (audit log, advanced security) are Enterprise-only.

Setting up the connection

Auth type: Bearer Token.

1. For personal automation: GitHub → Settings → Developer settings → Personal access tokens → Fine-grained tokens.
2. Pick the repos this token should access (single repo or all). Add the required permissions: Repository (contents read/write, issues read/write, pull-requests read/write, actions read), and Account (if needed).
3. Copy the token (starts with github_pat_...).
4. For org-wide automation, install a GitHub App instead and use installation tokens (not covered here – current connector accepts PATs or GitHub App tokens directly).
5. In Automize, open Settings → Connectors → GitHub → Add connection. Paste the token.

Find your credentials at https://github.com/settings/tokens.

Rate limits

GitHub enforces 5,000 requests/hour per authenticated user (15,000/hour for Enterprise Cloud orgs). The connector reads X-RateLimit-Remaining headers and pauses when close to the limit. Search endpoints have a tighter limit (30 req/min). Use conditional requests (ETags) for repeated list calls – saves quota.

Data model

Top-level objects:

    Organization / User ─┬─ Repositories ─┬─ Issues ── Comments
                          │                ├─ Pull Requests ── Reviews ── Comments
                          │                ├─ Branches ── Commits
                          │                ├─ Workflows (Actions) ── Workflow Runs
                          │                ├─ Releases ── Assets
                          │                └─ Webhooks
                          └─ Members / Teams (org only)

owner/repo is the canonical addressing – e.g. "anthropics/claude-code".

Available operations

28 operations available. Click any row to jump to its detail.

Operations

Add Labels

Add labels to an issue or PR

Create comment

Create a comment on a GitHub issue or pull request.

Create issue

Create a GitHub issue.

Tips

• title required. body in Markdown. labels, assignees, milestone optional.

Errors

• Issues are disabled for this repo – Owner has disabled issues. Enable them in repo Settings.

Create pull request

Create a GitHub pull request.

Create release

Create a release on a GitHub repository.

Tips

• tag_name + target_commitish (branch or SHA) + name (release title) + body (release notes in Markdown).

Create Repo

Create a new repository

Tips

• Pass owner ('' for the authenticated user, or an org name for org repos).
• private=true creates a private repo. auto_init=true initialises with a README.

Get issue

Get a GitHub issue by number.

Tips

• issue_number is the per-repo number (the #123 you see in the UI).

Get pull request

Get a GitHub pull request by number.

Get repository

Get a GitHub repository by owner and name.

Tips

• owner + repo. Returns full repo metadata: visibility, default_branch, stars, language, etc.

List workflow runs

List GitHub Actions workflow runs.

List branches

List branches on a GitHub repository.

Tips

• Returns branches + their head SHAs. protected=true filters to protected branches.

List commits

List commits on a GitHub repository.

Tips

• Filter by sha (start commit), path (file), author, since, until.

List Issue Comments

List comments on an issue

Tips

• Newest first. Page via per_page + page.

List issues

List issues on a GitHub repository.

Tips

• state=open / closed / all. labels=bug,help-wanted (comma list).
• GitHub treats pull requests as a type of issue – filter out via pull_request=null if you only want issues.

List Labels

List labels in a repository

List Milestones

List milestones in a repository

List PR reviews

List reviews on a GitHub pull request.

List pull requests

List pull requests on a GitHub repository.

List releases

List releases on a GitHub repository.

Tips

• Returns published + draft releases (auth required for drafts). Newest first.

List repositories

List GitHub repositories.

No input parameters.

Tips

• Lists repos the authenticated user has access to. type=owner / member / all.
• Page via per_page (max 100) + page.

List Workflows

List GitHub Actions workflows

Tips

• Returns Actions workflow definitions (.github/workflows/*.yml files).

Merge pull request

Merge a GitHub pull request.

Request reviewers

Request reviewers for a GitHub pull request.

Search Issues

Search issues and pull requests

No input parameters.

Tips

• GitHub-search syntax: 'repo:owner/name is:open type:issue label:bug'.
• Tighter rate limit than other endpoints (30/min).

Search repositories

Search GitHub repositories.

No input parameters.

Trigger workflow

Trigger a GitHub Actions workflow dispatch event.

Update issue

Update a GitHub issue.

Tips

• PATCH-style. state: 'open' or 'closed'. state_reason for closures: 'completed', 'not_planned'.

Update pull request

Update a GitHub pull request.

FAQ

Personal access token vs GitHub App – which?

PAT for personal automation or single-user bots. GitHub App for org-scale automation – better security (per-repo scopes, no impersonation), higher rate limits. The connector accepts both; for App auth, generate an installation token externally and paste it like a regular bearer token.

Fine-grained vs classic PAT?

Always prefer fine-grained. Scope to specific repos + minimum permissions. Classic PATs are coarse (repo gives access to ALL your repos) and slated for deprecation.

Why does my PR Merge return 405 'Method Not Allowed'?

Either branch protection rules require status checks not yet passing, OR the org has restricted merge methods. Check the repo's Settings → Branches and try a different merge_method.

GHES (Enterprise Server) – how?

Set the GHES base URL on the connection (e.g. https://github.yourcompany.com/api/v3). Everything else works the same.

Webhooks – when?

For event-driven automation (issue opened → run process), use GitHub Webhooks pointed at Automize's webhook ingest URL. This connector handles the API-call side; webhooks are configured separately.

Related connectors

• Gitlab
• Bitbucket
• Jira
• Azure-devops