# Connect GitHub to Spike.sh When **New Branch** fires in [GitHub](https://apiant.ai/connections/github), your agent runs **Add alert rule** in [Spike.sh](https://apiant.ai/connections/spike-sh). Describe the whole flow and it is built, tested on every scenario and kept running. GitHub **15** triggers GitHub **19** actions Spike.sh **25** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want GitHub and Spike.sh to do together? Give your AI client this address. `https://mcp.apiant.ai` Any 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What GitHub can start in Spike.sh - When **New Branch** in GitHub then **Add alert rule** in Spike.sh - When **New Collaborator** in GitHub then **Add escalation** in Spike.sh 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 Spike.sh ## Triggers and actions 15 triggers · 44 actions - Trigger **Issue Closed** Triggers when an issue in a repository is closed. - Trigger **New Branch** Triggers when a new branch is created in a GitHub repository. - Trigger **New Collaborator** Triggers when a new collaborator is added to a GitHub repository. - Trigger **New Commit** Triggers when a new commit is pushed to a GitHub repository's default branch. - Trigger **New Commit Comment** Triggers when someone comments on a commit in a repository. - Trigger **New Gist** Triggers when you create a new gist on GitHub. - Trigger **New Global Event** Triggers when a new public event happens anywhere on GitHub, such as a push, fork, or new issue. - Trigger **New Issue** Triggers when a new issue is created in a repository. - Trigger **New Label** Triggers when a new label is added to a GitHub repository. - Trigger **New Milestone** Triggers when a new milestone is created in a repository. - Trigger **New Pull Request** Triggers when a new pull request is opened in a repository. - Trigger **New Release** Triggers when a new release is published in a GitHub repository. - Trigger **New Repo Event** Triggers when new activity (pushes, issues, pull requests, releases and more) happens in a GitHub repository. - Trigger **New Repository** Triggers when a new public repository appears under a GitHub user or organization. - Trigger **New Watcher** Triggers when someone starts watching a repository. - Action **Add Labels to Issue** Adds labels to an issue or pull request in a GitHub repository, keeping its existing labels. - Action **Check Organization Membership** Checks whether a GitHub user is a member of an organization and returns true or false. - Action **Create Branch** Creates a new branch in a repository, starting from the commit you choose. - Action **Create Comment** Adds a comment to an issue or pull request in a GitHub repository. - Action **Create Gist** Creates a new gist with one file on the connected GitHub account. - Action **Create Issue** Creates a new issue in a GitHub repository. - Action **Create or Update File** Creates a new file in a repository, or replaces an existing file's contents, as a commit. - Action **Create Pull Request** Opens a pull request asking to merge one branch into another. - Action **Delete Branch** Deletes a branch from a repository. Any open pull request from that branch is closed. - Action **Find Branch** Finds a branch in a GitHub repository by name and returns its latest commit and protection status. - Action **Find Issue** Finds an issue in a GitHub repository by its number and returns its title, body, state, author and labels. - Action **Find Organization** Finds a GitHub organization by its login and returns its profile details. - Action **Find Pull Request** Finds a pull request in a GitHub repository by its number and returns its title, state, branches and merge status. - Action **Find Repository** Returns a GitHub repository by its owner and name, including its description, visibility, default branch and counts. - Action **Find User** Finds a GitHub user by username and returns their public profile. - Action **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. - Action **Submit Review** Submits a review on a pull request: approve it, request changes, or leave a review comment. - Action **Update Issue** Updates an existing issue in a GitHub repository, such as its title, text, state, labels or assignees. - Action **Update Pull Request** Changes a pull request's title, description, target branch, or open/closed state. - Action **Acknowledge incident** Acknowledge one or more Spike.sh incidents by counter id or incident id. - Action **Add alert rule** Create a new alert routing/automation rule with conditions and actions. - Action **Add escalation** Creates a new escalation policy for a Spike.sh team, defining who is notified, through which channel, and how long to wait between steps. - Action **Add integration** Create a new integration for a team (source system that sends alerts into Spike). - Action **Add on-call** Create a new on-call schedule for a team. - Action **Add service** Create a new service in a team, with name and description. - Action **Create Incident** Creates a Spike incident through one of your integrations and sends alerts. The integration decides which service and escalation policy the incident is routed to. - Action **Delete alert rule** Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents. - Action **Delete escalation** Archives (soft-deletes) a Spike escalation policy by its ID. - Action **Escalate incident** Escalates one or more Spike incidents to the next step of their escalation policy. - Action **Get escalation** Get escalation policy details by id. - Action **Get incident** Fetch a single incident by counter id. - Action **Get integration** Fetches an integration by its token, including its name, type, service, escalation settings and webhook URL. An error occurs if the integration is not found. - Action **Get service** Get a Spike service's details, along with its incidents and open-incident count. - Action **List alert rules** Lists all alert rules (enabled and disabled) configured for a Spike team. - Action **List escalations** Lists the escalation policies that belong to a Spike team. - Action **List incidents** Lists the incidents for a Spike.sh team. - Action **List on-calls** Lists the on-call schedules for a team. - Action **List services** Lists the services in a Spike team. - Action **List teams** Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team. - Action **Resolve incident** Resolve one or more incidents by counter id array. - Action **Update alert rule** Replace an existing Spike alert rule's name, conditions and actions. - Action **Update escalation** Replaces an existing escalation policy's name, steps and start delay. The whole policy is replaced, so send every step you want to keep. - Action **Update on-call** Updates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action. - Action **Update service** Updates the name and/or description of an existing Spike.sh service. ## Each app on its own - [ **GitHub** GitHub is the perfect place to share code and work collaboratively on private and open source software.](https://apiant.ai/connections/github) - [ **Spike.sh** Spike is an incident management system with unlimited alerts and on-call schedules](https://apiant.ai/connections/spike-sh) Reviews ## What our customers say ## More from GitHub - [ **GitHub to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/github-to-hubspot) - [ **GitHub to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/github-to-salesforce) - [ **GitHub to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/github-to-slack) - [ **GitHub to Google Sheets** Google Sheets](https://apiant.ai/connect/github-to-google-sheets) - [ **GitHub to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/github-to-gmail) - [ **GitHub to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/github-to-google-calendar) ## More into Spike.sh - [ **HubSpot to Spike.sh** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-spike-sh) - [ **Salesforce to Spike.sh** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-spike-sh) - [ **Slack to Spike.sh** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-spike-sh) - [ **Google Sheets to Spike.sh** Google Sheets](https://apiant.ai/connect/google-sheets-to-spike-sh) - [ **Gmail to Spike.sh** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-spike-sh) - [ **Google Calendar to Spike.sh** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-spike-sh) Questions ## GitHub and Spike.sh, 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 Spike.sh when something happens in GitHub? Any of Spike.sh's 25 actions, including Create Incident, Update alert rule, Update escalation and Update on-call. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Spike.sh to GitHub? Spike.sh has no triggers in the catalog today, so automations start in GitHub. If you need the other direction, ask: your agent reads Spike.sh's API documentation and adds it. ### ### Do I have to build a connector for GitHub or Spike.sh? 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.