GitHub integration
Developer tools connector, available on Zeplik
GitHub is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect GitHub and Zeplik can act on your software development for you: Read repositories, issues and pull requests, and open new ones. You stay in the conversation while the assistant does the work in GitHub directly.
Zeplik exposes 14 read actions and 86 write actions for GitHub. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in GitHub without your consent.
Try GitHub on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
What Zeplik can do with GitHub
Read from GitHub (14)
Runs automatically in any conversation.
Check a token
Checks if a github app or oauth access token is valid for the specified client id and retrieves its details, typically to verify its active status and grants.
Check if a gist is starred
Checks if a gist, identified by `gist id`, is starred by the authenticated user, returning an empty response (204) if starred, or a 404 error if not starred or not found.
Check if a person is followed by the authenticated user
Checks if the authenticated github user follows a target github user; an http 204 status indicates the user is followed, while an http 404 status indicates the user is not followed or the target user does not exist.
Check if a pull request has been merged
Checks if a specified github pull request has been merged, indicated by a 204 http status (merged) or 404 (not merged/found).
Check if a repository is starred by the authenticated user
Use to determine if the authenticated user has starred a specific github repository, which is confirmed by an http 204 status (resulting in an empty dictionary in the response data); the action fails (e.g., http 404) if the repository is not starred or does not exist.
Check if a user can be assigned
Verifies if a github user can be assigned to issues in a repository; assignability is confirmed by an http 204 (no content) response, resulting in an empty 'data' field in the response.
Check if a user can be assigned to a issue
Checks if a specified github user can be assigned to a given issue within a repository.
Check if a user follows another user
Checks if a github user `username` follows `target user`; returns a 204 http status if true, 404 if not or if users are invalid.
Check if a user is a repository collaborator
Checks if a user is a collaborator on a specified github repository, returning a 204 status if they are, or a 404 status if they are not or if the repository/user does not exist.
Check if a user is blocked by an organization
Checks if a github user is blocked by an organization; a successful response (204 no content) indicates the user is blocked, while a 404 not found error indicates the user is not blocked.
Check if a user is blocked by the authenticated user
Checks if the specified github user is blocked by the authenticated user; a 204 no content response indicates the user is blocked, while a 404 not found indicates they are not.
Check private vulnerability reporting status
Checks if private vulnerability reporting is enabled for the specified repository.
and 2 more.
Act in GitHub (86)
Runs only after you enable write access.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Activity list repo s starred by authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
Activity list stargazers for repo
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Activity star repo for authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add an email address for the authenticated user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Add a selected repository to a user secret
Grants a specified repository access to an authenticated user's existing codespaces secret, enabling codespaces created for that repository to use the secret.
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Add org runner labels
Adds new custom labels to an existing self-hosted runner for an organization; existing labels are not removed, and duplicates are not added.
and 74 more.
How to connect GitHub
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try GitHub immediately.
Connect GitHub
Open Settings and go to Connectors, then press Connect on GitHub. You can also connect from the GitHub page in the app.
Approve access to GitHub
Approve access on GitHub's secure consent screen. You are returned to Zeplik and can start giving instructions that use GitHub.
Frequently asked questions
- Can I use GitHub with Zeplik?
- Yes. GitHub is available as an integration on Zeplik. Connect it once and the AI assistant can work with your GitHub account inside any conversation.
- What can Zeplik do with GitHub?
- Once connected, Zeplik has 14 read and 86 write actions for GitHub. Read repositories, issues and pull requests, and open new ones.
- How do I connect GitHub to Zeplik?
- You connect GitHub with a secure one-click sign-in (OAuth): press Connect in Settings under Connectors and approve access on GitHub's consent screen.
- Does Zeplik change things in GitHub without asking?
- No. Zeplik reads from GitHub by default. Any action that changes data in GitHub requires write access, which stays off until you enable it in Settings under Connectors.
- How much does connecting GitHub cost?
- Connecting GitHub is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.
Related developer tools integrations
- AblyAbly is a real-time messaging platform helping developers build live features, including chat and data synchronization, with global scalability and.
- AbstractAbstract API provides a suite of APIs for developers to automate various tasks, including data validation, enrichment, and more.
- AddressfinderA reliably smart, reliably accurate data quality platform for address, email, and phone verification
- AddresszenAddressZen provides address autocomplete and verification services, offering real-time address suggestions and validation to ensure accurate and.
- Agility CMSAgility CMS is a headless content management system that allows developers to build and manage digital experiences across various platforms.
- AlchemyAlchemy is a blockchain development platform that provides powerful APIs and developer tools for building and scaling Ethereum applications
Connect GitHub to your AI assistant
Every model, one chat. Bring GitHub into Zeplik and let the assistant do the work.