GitHub is the perfect place to share code and work collaboratively on private and open source software.
Changelog
13 versions
v3.4.0
Latest
- Find Project Items: each item now also returns Added To Project At (createdAt) and Updated In Project At (updatedAt) — when the item was added to or last changed in the project, as opposed to the issue's or pull request's own dates. Lets a flow pick out items added recently.
v3.3.2
- Added missing output examples to GetProject, GetProjectItem, FindIssue, FindPullRequest and ListPullRequests. The item ID emitted by FindIssue, FindPullRequest and ListPullRequests is now declared as an integer, which is what GitHub returns.
v3.3.1
- Fixed a crash when a Find/List component saved an EMPTY result set to a CSV file — the header row was built from the first record without checking there was one, so a search that legitimately matched nothing failed the flow instead of writing an empty file.
v3.3.0
- Added pull request comment triggers: NewPullRequestReviewComment (inline comments on the diff, repository-wide, with pull request / author / bots-vs-humans filters), NewIssueComment (conversation comments on pull requests and issues, with a 'comment on' filter because GitHub's repository-wide payload does not say which of the two it is) and NewReview (a submitted review with its state, the only way to catch an approval that carries a body but no inline comments).
- Added pull request review actions: ReplyToReviewComment (reply inside a review thread), CreateReviewComment (comment on a line of the diff or on a whole file), FindReviewComments and ListReviews.
- Added GraphQL review thread components: ListReviewThreads (thread ID, isResolved, isOutdated, path, filterable by resolved state) plus ResolveReviewThread and UnresolveReviewThread. Thread resolution has no REST equivalent.
- Author filters match logins case-insensitively as substrings: one account is reported under a different login per endpoint, and the two REST endpoints disagree with each other - Copilot's reviewer (user id 175728472) is 'Copilot' on /pulls/comments, 'copilot-pull-request-reviewer[bot]' on /pulls/{n}/reviews and 'copilot-pull-request-reviewer' in GraphQL, so an exact-match filter would silently match nothing.
- Clarified the descriptions of CreateComment, ListComments, UpdateComment, SubmitReview and NewCommitComment so the three unrelated things GitHub calls a 'comment' (issue, review and commit comments) can be told apart.
- NewReview scans recently updated pull requests in any state, not only open ones: approving a pull request and merging it is the most common review event, and an open-only scan lost that review for good because the pull request left the window before the next tick. NewPullRequestReviewComment now emits pull_request_number alongside the raw payload, so its output feeds ReplyToReviewComment and CreateReviewComment directly.
v3.2.0
- Added Projects (v2) board-driven workflow components: project/OnProjectItemChanged (organization webhook trigger for projects_v2_item), project/GetNodeById, project/UpdateProjectItemField, list/RepositoryDispatch, list/UpdateComment and list/ListComments. The new components declare the 'project' and 'admin:org_hook' scopes; existing components and their scopes are unchanged.
- Added NewAssignedIssue trigger: fires when a new issue is assigned to the authenticated user (optionally scoped to a repository).
- Added NewMention trigger: fires when the authenticated user is mentioned in an issue, pull request or comment (optionally filtered by repositories).
- Repository inputs (repositoryId) in all 30 components are now free-text in owner/repo format with the dynamically loaded repository list kept as typeahead suggestions, so any accessible repository can be used, not only the user's own.
- Added output examples and schemas to output port options across all components.
- Polling triggers now cap the stored known-IDs state at 500 entries.
- Raised the requests-projects quota (GraphQL, Projects v2) from 5 to 60 calls per minute; the old limit was exhausted by the designer's schema calls alone.
v3.1.0
- Added test() (Flow Test Mode) to all triggers: NewStargazer, NewCommitComment, NewTeam, NewOrganization, NewMilestone, NewNotification, NewBranch, NewWatcher, NewRelease, NewRepository, NewCollaborator, NewGist, NewReviewRequest, NewPullRequest, NewIssue, NewGlobalEvent, NewCommit, NewLabel, NewEvent.
v3.0.0
- (breaking change) MakeApiCall: headers and parameters changed to key-value array inputs (body remains textarea/JSON to support nested structures) per standard #1459 — existing flows that used the old string/textarea headers or parameters must be updated
v2.1.2
- Added output examples to component schemas.
v2.1.1
- Implemented multiselect input normalization for assignees and labels fields in CreateIssue, FindIssue, FindPullRequest, NewIssue, and UpdateIssue components.
v2.1.0
- Added support for GitHub Projects API with new components: ListProjects, GetProject, GetProjectItem.
v2.0.1
- Removing unneeded dependencies.
v2.0.0
- [Breaking Change]: Revamped Github connector with new and improved components.
v1.0.3
- Removed 'None' empty string value from ListAssignees, ListLabels and ListMilestones.
Authentication
| Type | Details |
|---|---|
| OAuth 2 |
Authentication Hub
Verified
This connector is globally authenticated and verified by Appmixer and is ready to use without registering your own OAuth application with the provider. Appmixer's Authentication Hub acts as an authentication proxy, so all OAuth-based connectors work out of the box. You can still use your own OAuth credentials (clientId and clientSecret) for enhanced customization or compliance — see the Connector Configuration section of the documentation. The Authentication Hub is enabled for all hosted Appmixer tenants; on self-managed installations it has to be explicitly set.
Auth URL:
https://github.com/login/oauth/authorize
|
Triggers
27
Get Organization By Name
Fetches an organization by name.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Assigned Issue
Triggers whenever a new issue is assigned to the authenticated user. Optionally filter by a specific repository.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Branch
Triggered when a new branch is created.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Collaborator
Triggered when you add a new collaborator.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Commit
Triggered when a new commit is created.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Commit Comment
Triggers when a comment is posted on a commit — a comment attached to a commit outside any pull request. For comments on a pull request use New Issue Comment (conversation) or New Pull Request Review Comment (inline on the diff).
Additional Scopes:
user
public_repo
repo
notifications
gist
New Event
Triggered when anything happens on a repo. Note that according to the DOCs: This API is not built to serve real-time use cases. Depending on the time of day, event latency can be anywhere from 30s to 6h.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Gist
Triggered when a new gist is created (public or private).
Additional Scopes:
user
public_repo
repo
notifications
gist
New Global Event
Triggers when a new global event occurs to or from the authenticated user on GitHub. Note that according to the DOCs: This API is not built to serve real-time use cases. Depending on the time of day, event latency can be anywhere from 30s to 6h.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Issue
Triggered when a new issue is created.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Issue Comment
Triggers when a new conversation comment is posted on an issue or on a pull request anywhere in a repository. GitHub calls both of these 'issue comments'; use the 'Comment On' input to keep only one kind. This is not the same as an inline comment on a diff (use New Pull Request Review Comment) nor a comment on a commit (use New Commit Comment).
Additional Scopes:
public_repo
repo
New Label
Triggers when a new label is created in a GitHub repository.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Mention
Triggers whenever the authenticated user is mentioned in an issue, pull request, or comment on GitHub. Optionally filter by one or more repositories.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Milestone
Triggers when a new milestone is created in a GitHub repository.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Notification
Triggers whenever a new notification is received in your GitHub account.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Organization
Triggers when a new organization is created in your github account.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Pull Request
Triggered when a new pull request is created.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Pull Request Review Comment
Triggers when a new review comment — a comment anchored to a line of a pull request diff — is posted anywhere in a repository. Optionally filter by pull request, author login or bots vs. humans. This is not the same as a comment in the pull request conversation (use New Issue Comment) nor a comment on a commit (use New Commit Comment).
Additional Scopes:
public_repo
repo
New Release
Triggers when a new release is done in your repository.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Repository
Triggered when a new repository is created.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Review
Triggers when a pull request review is submitted, with its state (Approved, Changes Requested or Commented). This is the only way to catch a review that carries a body but no inline comments — an approval with a note — which a trigger built on review comments cannot see. GitHub has no repository-wide reviews endpoint, so open pull requests touched since the last check are scanned one by one.
Additional Scopes:
public_repo
repo
New Review Request
Triggers whenever a new review request is created for the specified username in the selected repository.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Stargazer
Triggered when a new user starred a repo.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Team
Triggers whenever user is added to a new team.
Additional Scopes:
user
public_repo
repo
notifications
gist
New Watcher
Triggered when a new watcher is added to a repo.
Additional Scopes:
user
public_repo
repo
notifications
gist
On Project Item Changed
Triggers when a card on an organization's Projects (v2) board changes. Registers an organization webhook for the projects_v2_item event and emits the payload including the changed field value.
Additional Scopes:
admin:org_hook
read:org
read:project
repo
Actions
31
Create Comment
Post a comment to the conversation timeline of an issue or a pull request. This is not an inline comment on a line of a diff (use Create Review Comment), nor a reply inside a review thread (use Reply To Review Comment), nor a comment on a commit.
Additional Scopes:
user
public_repo
repo
notifications
gist
Create Pull Request
Create a new pull request.
Additional Scopes:
user
public_repo
repo
notifications
gist
Create Review Comment
Add an inline review comment to a line of a pull request diff. This is the line-anchored counterpart of Submit Review, which comments on the pull request as a whole, and of Create Comment, which posts to the pull request conversation. When no Commit SHA is given, the head commit of the pull request is used.
Additional Scopes:
public_repo
repo
Find Issue
Finds issues that match the search criteria.
Additional Scopes:
user
public_repo
repo
notifications
gist
Find Pull Request
Finds pull requests that match the search criteria.
Additional Scopes:
user
public_repo
repo
notifications
gist
Find Repository
Finds repositories that match the search criteria.
Additional Scopes:
user
public_repo
repo
notifications
gist
Find Review Comments
Search the inline review comments of a repository — the ones anchored to a line of a pull request diff. Give a pull request number to search a single pull request, or leave it empty to search the whole repository. Optionally filter by author login and by bots vs. humans.
Additional Scopes:
public_repo
repo
Get Pull Request By Number
Fetches a single pull request based on the provided PR number.
Additional Scopes:
user
public_repo
repo
notifications
gist
List Comments
List the conversation comments of an issue or a pull request. Useful for finding a 'sticky' comment by an HTML marker before updating it. These are not the inline comments on the diff (use Find Review Comments) nor comments on a commit.
Additional Scopes:
public_repo
repo
List Pull Requests
Returns a list of pull requests from a repository.
Additional Scopes:
user
public_repo
repo
notifications
gist
List Review Threads
List the review threads of a pull request with their thread ID, resolved and outdated flags, file path and first comment. Thread resolution exists only in GitHub's GraphQL API — a review comment fetched over REST has no resolved field — so this is the only way to see which threads are still open. Feed the thread ID into Resolve Review Thread.
Additional Scopes:
public_repo
repo
List Reviews
List every review submitted on a pull request, with its state (Approved, Changes Requested, Commented or Dismissed) and body. GitHub has no repository-wide reviews endpoint, so reviews are always listed for one pull request at a time.
Additional Scopes:
public_repo
repo
Make Api Call
Generic method for making API calls to GitHub API.
Additional Scopes:
user
public_repo
repo
notifications
gist
Reply To Review Comment
Post a reply inside an existing pull request review thread, under the review comment given by its ID. Use this to answer a reviewer (or a code review bot) on the exact line they commented on, instead of adding a new comment to the pull request conversation.
Additional Scopes:
public_repo
repo
Repository Dispatch
Trigger a repository_dispatch event in a repository, starting any GitHub Actions workflow that listens for it.
Additional Scopes:
repo
Resolve Review Thread
Mark a pull request review thread as resolved, the same as clicking 'Resolve conversation' in GitHub. Thread resolution exists only in GitHub's GraphQL API, so the input is the GraphQL thread ID emitted by List Review Threads, not a review comment ID.
Additional Scopes:
public_repo
repo
Submit Review
Submit a review on a pull request as a whole — approve it, request changes, or leave a comment. To anchor a comment to a line of the diff use Create Review Comment instead.
Additional Scopes:
user
public_repo
repo
notifications
gist
Unresolve Review Thread
Reopen a resolved pull request review thread, the same as clicking 'Unresolve conversation' in GitHub. Thread resolution exists only in GitHub's GraphQL API, so the input is the GraphQL thread ID emitted by List Review Threads, not a review comment ID.
Additional Scopes:
public_repo
repo
Update Comment
Update the body of an existing conversation comment on an issue or a pull request. This does not update an inline review comment on a diff, which GitHub stores separately.
Additional Scopes:
public_repo
repo
Update Pull Request
Update a pull request.
Additional Scopes:
user
public_repo
repo
notifications
gist
Find Projects
Retrieve all projects accessible to the authenticated user (either via organization or personal projects) using GitHub's GraphQL API. Supports filtering by project name using the query parameter.
Additional Scopes:
read:project
Get Node By ID
Resolve a GitHub global node ID (issue, pull request or draft issue) to its number, title, URL, state, repository and labels.
Additional Scopes:
read:project
repo
Get Project
Retrieve detailed information for a specific GitHub project.
Additional Scopes:
read:project
Get Project Fields
Retrieve all field definitions and configurations for a specified project, including custom fields.
Additional Scopes:
read:project
Get Project Item
Retrieve detailed information about a specific project item including its field values and metadata.
Additional Scopes:
read:project
repo
Update Project Item Field
Set a single-select, number, text, date or iteration field on a Projects (v2) card. Single-select values are given by option name and resolved to the option ID.
Additional Scopes:
project
repo
Find Project Items
Retrieve items from a GitHub project that match a specific status and/or content type. Returns both Issues and Pull Requests linked to the project. Can filter by status (e.g., 'Todo', 'In Progress', 'Done') and by content type (Issue, PullRequest, or DraftIssue). Each item includes its content details (title, URL, number, repository) and custom field values.
Additional Scopes:
read:project
repo