GitHub
+
Konnectify
GitHub Integration with Konnectify
Automate GitHub development workflows in Konnectify—track repositories, commits, issues, pull requests, releases, and notifications, then
route updates to downstream systems.
Repositories
Commits
Issues
Pull Requests
Releases
Gists
Milestones
Organizations
Teams
Notifications
16 Triggers
23 Actions
What is GitHub?
GitHub is a platform for version control, collaboration, and software development, built around Git repositories and a rich set of workflows
like issues, pull requests, releases, and code review.
Connecting GitHub to Konnectify lets you automate operational steps around engineering events—triage issues, track pull request changes,
synchronize repository metadata, and trigger downstream actions when activity happens in your repos.
New to GitHub?
Create an account and organize your code, issues, and pull requests.
Go to GitHub →
New to Konnectify?
Build workflows that connect GitHub to the rest of your tools—without brittle scripts.
Try Konnectify free →
What you can automate
• Create and update issue or pull request comments
• Monitor new or updated commits and repository events
• Detect new issues and route them for triage
• Track pull request updates and trigger reviews
• Watch releases and notifications for changes
• Create branches and manage labels/locks on issues
API & Authentication
Authentication method: OAuth 2.0 authorization
When you connect GitHub to Konnectify, you’ll be redirected to GitHub to approve access. Konnectify exchanges the authorization code for an
access token and uses it to make API calls on your behalf. Your GitHub password is never shared with Konnectify.
Requested permissions (scopes):
repo, gist, read:user, user:email, user:follow. These scopes typically enable reading repository data and activity, working with gists, and
reading basic user profile information (including email, if available).
- Read repository activity such as commits, pull requests, issues, releases, and events
- Manage issue interactions such as comments, labels, and lock/unlock state
- Create and delete branches (where your GitHub permissions allow it)
- Create gists under the authenticated account
- Check organization membership and find public org/user details
Important: rate limits & plan/permission constraints
GitHub enforces API rate limits and permission checks. If a workflow runs frequently (especially polling triggers), you may hit rate limits or
see missing data when the connected user doesn’t have access to a repository or organization. Consider using lower polling frequencies and
narrowing repository scope where possible.
How to connect GitHub to Konnectify
Prerequisites
- A Konnectify account with permission to create/edit workflows
- A GitHub account (and access to the repos/orgs you want to automate)
- GitHub OAuth App credentials: Client ID and Client Secret
- Popups allowed in your browser (for the OAuth authorization window)
Add GitHub to a Workflow
- Create a new workflow (or open an existing one) in Konnectify.
- Select GitHub as your trigger app or action app.
Authorize via OAuth 2.0
- Click Connect and enter your GitHub OAuth Client ID and Client Secret.
- Complete the GitHub consent screen and approve the requested scopes.
Configure the Trigger or Action
- Select the trigger (for example, a new issue) or an action (for example, create a comment).
- Fill in required fields such as repository owner/name, issue number, or pull request number—depending on the step.
- Map dynamic fields from previous steps to keep workflows flexible.
Tip: Repository identifiers must match GitHub exactly (owner + repo). If a step fails, confirm the connected user has
access and that the repo exists.
Test the Workflow
- Run a test to confirm Konnectify can read from GitHub and perform the action successfully.
- Verify output fields (IDs, URLs, titles, states) for mapping into later steps.
Activate the Workflow
- Turn the workflow ON.
- Monitor initial runs and adjust polling frequency and filters to match your team’s needs.
Triggers
16
This integration includes 16 polling triggers. Polling triggers check GitHub at regular intervals and emit new events as they
appear.
Commits & Comments
2 triggers
New or Updated Commit
Monitors GitHub for new commits or updates to existing commits in a repository.
New Commit Comment
Polls GitHub to detect newly created commit comments in a repository.
Issues & Milestones
4 triggers
New Issue
Polls GitHub to detect newly created issues in a repository.
New or Updated Issue
Monitors GitHub for newly created or updated issues in a repository.
New Milestone
Polls GitHub to detect newly created milestones in a repository.
New Fork
Polls GitHub to detect when a repository is forked.
Pull Requests
2 triggers
New Pull Request
Polls GitHub to detect newly created pull requests.
Updated Pull Request
Polls GitHub to detect newly created or updated pull requests.
Releases
2 triggers
New Release
Polls GitHub to detect newly published releases in a repository.
Updated Release
Polls GitHub to detect updated releases in a repository.
Gists
2 triggers
New Gist
Polls GitHub to detect newly created gists for the authenticated user.
New or Updated Gist
Polls GitHub to detect newly created or updated gists for the authenticated user.
Repositories & Events
4 triggers
New Repository
Polls GitHub to detect when a new repository becomes available to the authenticated user.
Updated Repository
Polls GitHub to detect when an existing repository is updated for the authenticated user.
New Repo Event
Polls GitHub to detect new activity events in a repository.
New or Updated Notification
Polls GitHub to detect new or updated notifications for the authenticated user.
Organizations & Teams
2 triggers
New Team Created
Polls GitHub to detect newly created teams in an organization.
This module focuses on organization-level changes (teams and related org data).
Actions
23
Use GitHub actions to look up entities (users, repos, issues, pull requests, releases) and to manage collaboration tasks like comments,
branches, and reviews.
Users
1 actions
Find User
Retrieves public GitHub user details using the GitHub username.
Use this to enrich workflows with profile data (login, URLs, public info).
Organizations
2 actions
Find Organization
Retrieves public GitHub organization details using organization name or ID.
Check Organization MemberShip
Checks whether a GitHub user is a member of a specific organization.
Repositories & Branches
5 actions
Find Repository
Retrieves GitHub repository details using the repo owner/name or a GitHub repository ID.
Find Branch
Retrieves details of a specific branch in a repository.
Create Branch
Creates a new branch from an existing branch.
Delete Branch
Deletes a branch from a GitHub repository.
Find Label
Retrieves details of a specific label from a GitHub repository.
Issues & Comments
10 actions
Find Issue
Retrieves public GitHub issue details using the repository name and issue number.
Lock Issue
Locks a GitHub issue in a specified repository, preventing new comments and interactions.
Unlock Issue
Unlocks a previously locked GitHub issue in a specified repository, allowing users to comment again.
Remove Label From Issue
Removes a specific label from a GitHub issue.
Remove All Labels From Issue
Removes every label from the specified GitHub issue.
Create Comment
Creates a new comment on a specified GitHub issue or pull request.
Update Comment
Updates the content of a specific comment on a GitHub issue or pull request.
Delete Comment
Deletes a specific comment from a GitHub issue or pull request using the comment identifier.
Find Comment
Retrieves details of a specific comment from a GitHub issue or pull request using the repository and comment identifier.
Combine comment actions with issue/pull request triggers to build automated triage and review workflows.
Pull Requests & Reviews
2 actions
Find Pull Request
Fetches details of a specific pull request in a repository.
Submit Review
Submits a review for a GitHub pull request, including approval, request for changes, or general comments.
Releases
1 actions
Find Release
Retrieves a GitHub release by release ID or tag name.
Use release metadata (tag, name, URL) for downstream announcements or change logs.
Gists
2 actions
Find Gist
Retrieves details of a GitHub Gist by its ID.
Create Gist
Creates a new GitHub Gist under the authenticated user.
Milestones
1 actions
Find Milestone
Retrieves milestone details from a GitHub repository.
Milestones are useful for sprint/release tracking across issues and pull requests.
Popular automations
Examples of common GitHub workflows you can build with Konnectify using the triggers and actions above.
Auto-acknowledge new issues
When a new issue is created, automatically add a comment acknowledging receipt and sharing next steps.
New Issue
→
Create Comment
Review workflow on pull request updates
When a pull request is updated, fetch PR details and automatically submit a review (for example, a checklist comment or approval).
Updated Pull Request
→
Find Pull Request
→
Submit Review
Release monitoring and enrichment
When a release is published, look up the full release metadata by tag/ID and pass it to the next steps in your workflow.
New Release
→
Find Release
Create a working branch when a repo changes
When repository metadata is updated, validate the repository and automatically create a new branch from a base branch for maintenance or
automation.
Updated Repository
→
Find Repository
→
Create Branch
FAQ
How does Konnectify authenticate with GitHub?
GitHub uses OAuth 2.0. You connect by approving access in GitHub, and Konnectify uses the granted token to call GitHub APIs.
Your GitHub password is never stored in Konnectify.
Which GitHub plans are supported?
Konnectify works with GitHub accounts that can access the relevant endpoints. Availability depends on your GitHub plan and repository/org
permissions (for example, private repo access requires appropriate permissions). If an action fails, verify the connected user’s access.
Are the GitHub triggers polling or webhook-based?
All triggers in this version are polling triggers. Konnectify checks GitHub on a schedule and emits new events since the
last run. For high-volume repositories, consider a longer polling interval to avoid rate limits.
How does Konnectify prevent duplicates?
These triggers use cursor-based polling to track what was already processed. To avoid duplicate downstream actions, also add guards in your
workflow (for example, check the issue/PR ID, updated timestamp, or state before posting a comment).
What happens if we hit GitHub API rate limits?
If GitHub rate limits are reached, steps may temporarily fail until the limit resets. To reduce the chance of this, decrease polling
frequency, scope triggers to specific repositories, and avoid unnecessary “find” lookups in the same run unless required.
Can I connect multiple GitHub accounts or organizations?
Yes. You can create multiple GitHub connections in Konnectify (for example, one per user or service account) and select the right
connection per workflow step.
Why do comment, branch, or review actions fail with “not found” or “forbidden”?
This usually indicates one of the following:
- The repository owner/name is incorrect, or the issue/PR/comment ID doesn’t exist.
- The connected GitHub user does not have permission (private repo access, write access, or review permissions).
- The workflow is targeting the wrong repo (for example, a fork instead of the upstream repository).
Ready to automate your GitHub workflows?
Connect GitHub to Konnectify to orchestrate engineering events across your toolchain.
Get started free →
