Integration
Connect GitHub to Hamsa
When New Branch fires in GitHub, your agent runs Add knowledge base item in Hamsa. 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 Hamsa 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 can start in Hamsa
When New Branch in GitHub
then Add knowledge base item in Hamsa
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 Hamsa
Triggers and actions 15 triggers · 40 actions
- Issue Closed
Triggers when an issue in a repository is closed.
- New Branch
Triggers when a new branch is created in a GitHub repository.
- New Collaborator
Triggers when a new collaborator is added to a GitHub repository.
- New Commit
Triggers when a new commit is pushed to a GitHub repository's default branch.
- New Commit Comment
Triggers when someone comments on a commit in a repository.
- New Gist
Triggers when you create a new gist on GitHub.
- New Global Event
Triggers when a new public event happens anywhere on GitHub, such as a push, fork, or new issue.
- New Issue
Triggers when a new issue is created in a repository.
- New Label
Triggers when a new label is added to a GitHub repository.
- New Milestone
Triggers when a new milestone is created in a repository.
- New Pull Request
Triggers when a new pull request is opened in a repository.
- New Release
Triggers when a new release is published in a GitHub repository.
- New Repo Event
Triggers when new activity (pushes, issues, pull requests, releases and more) happens in a GitHub repository.
- New Repository
Triggers when a new public repository appears under a GitHub user or organization.
- New Watcher
Triggers when someone starts watching a repository.
- Add Labels to Issue
Adds labels to an issue or pull request in a GitHub repository, keeping its existing labels.
- Check Organization Membership
Checks whether a GitHub user is a member of an organization and returns true or false.
- Create Branch
Creates a new branch in a repository, starting from the commit you choose.
- Create Comment
Adds a comment to an issue or pull request in a GitHub repository.
- Create Gist
Creates a new gist with one file on the connected GitHub account.
- Create Issue
Creates a new issue in a GitHub repository.
- Create or Update File
Creates a new file in a repository, or replaces an existing file's contents, as a commit.
- Create Pull Request
Opens a pull request asking to merge one branch into another.
- Delete Branch
Deletes a branch from a repository. Any open pull request from that branch is closed.
- Find Branch
Finds a branch in a GitHub repository by name and returns its latest commit and protection status.
- Find Issue
Finds an issue in a GitHub repository by its number and returns its title, body, state, author and labels.
- Find Organization
Finds a GitHub organization by its login and returns its profile details.
- Find Pull Request
Finds a pull request in a GitHub repository by its number and returns its title, state, branches and merge status.
- Find Repository
Returns a GitHub repository by its owner and name, including its description, visibility, default branch and counts.
- Find User
Finds a GitHub user by username and returns their public profile.
- Get File Contents
Returns a file from a GitHub repository, with its base64-encoded content, at the default branch or a chosen branch, tag or commit.
- Submit Review
Submits a review on a pull request: approve it, request changes, or leave a review comment.
- Update Issue
Updates an existing issue in a GitHub repository, such as its title, text, state, labels or assignees.
- Update Pull Request
Changes a pull request's title, description, target branch, or open/closed state.
- Add knowledge base item
Create a new knowledge base item for a voice agent.
- Add phone number
Add a phone number for a user.
- Add transcription job
Create a new asynchronous job (e.g. transcription).
- Add TTS voice
Create a new text-to-speech voice.
- Add voice agent
Create a new AI voice agent.
- Assign phone number
Assign a phone number to a voice agent.
- Delete knowledge base item
Delete a knowledge base item by ID.
- Delete phone number
Delete a phone number.
- Delete TTS voice
Delete a text-to-speech voice by ID.
- Get campaign
Get a campaign by ID.
- Get conversation
Get a call conversation record by ID.
- Get job
Get a single job's details by ID.
- Get voice agent
Retrieve a specific voice agent by ID.
- Initiate voice agent call
Initiate an outbound call with a voice agent via Twilio.
- List jobs
List jobs.
- List knowledge base items
Return a list of knowledge base items.
- List phone numbers
Return a list of phone numbers for a user.
- List TTS voices
Retrieve the list of available TTS voices.
- List voice agents
Retrieve a list of the account's voice agents.
- Transcribe audio
Generate a speech-to-text transcription from audio (not streamed).
- Update voice agent
Update an existing voice agent's configuration.
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 Hamsa
MySQL to HamsaConnect directly to a MySQL database and run SQL statements from your automations.
TimelinesAI to HamsaTimelinesAI allows you to share access to your personal or business Whatsapp account, integrate it with...
Questions
GitHub and Hamsa, 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 Hamsa when something happens in GitHub?
Any of Hamsa's 21 actions, including Update voice agent, Add knowledge base item, Add phone number and Add transcription job. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Hamsa to GitHub?
Hamsa has no triggers in the catalog today, so automations start in GitHub. If you need the other direction, ask: your agent reads Hamsa's API documentation and adds it.
Do I have to build a connector for GitHub or Hamsa?
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.