Integration
Connect GitHub and Skyvern
When New Branch fires in GitHub, your agent runs Create and Run a Task in Skyvern, or New or Updated Skyvern Workflow in Skyvern to Add Labels to Issue in GitHub. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want GitHub and Skyvern to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What GitHub and Skyvern can do together
From GitHub to Skyvern
When New Branch in GitHub
then Create and Run a Task in Skyvern
When New Collaborator in GitHub
then Create and Run Task V2 in Skyvern
From Skyvern to GitHub
When New or Updated Skyvern Workflow in Skyvern
then Add Labels to Issue in GitHub
When New or Updated Skyvern Workflow in Skyvern
then Create Issue in GitHub
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with GitHub and Skyvern
Triggers and actions 16 triggers · 34 actions
Trigger
Issue ClosedTriggers when an issue in a repository is closed.
Trigger
New BranchTriggers when a new branch is created in a GitHub repository.
Trigger
New CollaboratorTriggers when a new collaborator is added to a GitHub repository.
Trigger
New CommitTriggers when a new commit is pushed to a GitHub repository's default branch.
Trigger
New Commit CommentTriggers when someone comments on a commit in a repository.
Trigger
New GistTriggers when you create a new gist on GitHub.
Trigger
New Global EventTriggers when a new public event happens anywhere on GitHub, such as a push, fork, or new issue.
Trigger
New IssueTriggers when a new issue is created in a repository.
Trigger
New LabelTriggers when a new label is added to a GitHub repository.
Trigger
New MilestoneTriggers when a new milestone is created in a repository.
Trigger
New Pull RequestTriggers when a new pull request is opened in a repository.
Trigger
New ReleaseTriggers when a new release is published in a GitHub repository.
Trigger
New Repo EventTriggers when new activity (pushes, issues, pull requests, releases and more) happens in a GitHub repository.
Trigger
New RepositoryTriggers when a new public repository appears under a GitHub user or organization.
Trigger
New WatcherTriggers when someone starts watching a repository.
Action
Add Labels to IssueAdds labels to an issue or pull request in a GitHub repository, keeping its existing labels.
Action
Check Organization MembershipChecks whether a GitHub user is a member of an organization and returns true or false.
Action
Create BranchCreates a new branch in a repository, starting from the commit you choose.
Action
Create CommentAdds a comment to an issue or pull request in a GitHub repository.
Action
Create GistCreates a new gist with one file on the connected GitHub account.
Action
Create IssueCreates a new issue in a GitHub repository.
Action
Create or Update FileCreates a new file in a repository, or replaces an existing file's contents, as a commit.
Action
Create Pull RequestOpens a pull request asking to merge one branch into another.
Action
Delete BranchDeletes a branch from a repository. Any open pull request from that branch is closed.
Action
Find BranchFinds a branch in a GitHub repository by name and returns its latest commit and protection status.
Action
Find IssueFinds an issue in a GitHub repository by its number and returns its title, body, state, author and labels.
Action
Find OrganizationFinds a GitHub organization by its login and returns its profile details.
Action
Find Pull RequestFinds a pull request in a GitHub repository by its number and returns its title, state, branches and merge status.
Action
Find RepositoryReturns a GitHub repository by its owner and name, including its description, visibility, default branch and counts.
Action
Find UserFinds a GitHub user by username and returns their public profile.
Action
Get File ContentsReturns a file from a GitHub repository, with its base64-encoded content, at the default branch or a chosen branch, tag or commit.
Action
Submit ReviewSubmits a review on a pull request: approve it, request changes, or leave a review comment.
Action
Update IssueUpdates an existing issue in a GitHub repository, such as its title, text, state, labels or assignees.
Action
Update Pull RequestChanges a pull request's title, description, target branch, or open/closed state.
Trigger
New or Updated Skyvern WorkflowTriggers when a Skyvern workflow (agent) is created or a new version of it is saved.
Action
Add browser sessionCreates a Skyvern browser session that persists across multiple task and workflow runs, and returns its session id and live-view link.
Action
Add credentialCreates a new stored credential (login, credit card or secret) in your Skyvern organization for use by tasks and agents.
Action
Add workflowCreates a new Skyvern workflow (agent) from a JSON or YAML definition and returns the saved workflow.
Action
Cancel runCancels a running Skyvern task run or workflow run by its id.
Action
Create and Run a TaskStarts a Skyvern browser-automation task from a plain-language prompt and returns the new run, including its id, status and link in the Skyvern app.
Action
Create and Run Task V2Starts a Skyvern 2.0 browser task from a natural-language prompt and returns the new run's id and status.
Action
Delete workflowDeletes a Skyvern workflow (agent) by its ID.
Action
Get a Browser SessionReturns the details of a Skyvern browser session, including its status, browser address for connecting, downloaded files and recordings.
Action
Get a TaskReturns a Skyvern task run by its id, including its status, extracted output, downloaded files, recording and screenshots.
Action
Get a Task V2Returns the status, output, recording and screenshots of a Skyvern task run.
Action
Get a WorkflowReturns a Skyvern workflow (agent) by its permanent id, including its blocks, parameters and settings.
Action
List credentialsReturns the credentials stored in your Skyvern organization, optionally filtered by vault, type or search text. Secrets are never included.
Action
List runsReturns your organization's task and agent runs, newest first, optionally filtered by status, run type, agent, tags, failure category or a search term.
Action
List workflowsReturns the workflows (agents) in your Skyvern organization, optionally filtered by search text, folder, status or tags. Returns up to 100 workflows.
Action
Run a WorkflowStarts a run of one of your Skyvern workflows (agents) with the parameters you supply, and returns the new run's id, status and link.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from GitHub
GitHub to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
GitHub to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
GitHub to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
GitHub to Google SheetsGoogle Sheets
GitHub to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
GitHub to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Skyvern
HubSpot to SkyvernHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SkyvernSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SkyvernGoogle Sheets
Gmail to SkyvernGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SkyvernGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SkyvernGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
GitHub and Skyvern, answered
What can start an automation from GitHub?
Any of GitHub's 15 triggers in the catalog, including New Branch, New Collaborator, New Commit and New Commit Comment. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Skyvern when something happens in GitHub?
Any of Skyvern's 15 actions, including Create and Run a Task, Create and Run Task V2, Add browser session and Add credential. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Skyvern to GitHub?
Yes. When something happens in Skyvern, your agent can act in GitHub too. This page covers both directions: Skyvern's triggers and GitHub's actions are listed here as well.
Do I have to build a connector for GitHub or Skyvern?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.