--- title: "Connect Cronly and GitHub - APIANT.ai" description: "When \"Trigger Activated\" fires in Cronly, your agent runs \"Add Labels to Issue\" in GitHub, or \"New Branch\" in GitHub to \"Add project\" in Cronly." canonical: "https://apiant.ai/connect/cronly-to-github" --- # Connect Cronly and GitHub When **Trigger Activated** fires in [Cronly](https://apiant.ai/connections/cronly), your agent runs **Add Labels to Issue** in [GitHub](https://apiant.ai/connections/github), or **New Branch** in GitHub to **Add project** in Cronly. Describe the whole flow and it is built, tested on every scenario and kept running. Cronly **1** trigger Cronly **22** actions GitHub **15** triggers GitHub **19** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Cronly and GitHub to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. 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 Cronly and GitHub can do together ### From Cronly to GitHub - When **Trigger Activated** in Cronly then **Add Labels to Issue** in GitHub - When **Trigger Activated** in Cronly then **Create Issue** in GitHub ### From GitHub to Cronly - When **New Branch** in GitHub then **Add project** in Cronly - When **New Collaborator** in GitHub then **Get project** in Cronly 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 Cronly and GitHub ## Triggers and actions 16 triggers · 41 actions - Trigger **Trigger Activated** Triggers when a trigger is activated. - Action **Add back-up** Create a new back-up snapshot for a server/username (or a new one if none exists). - Action **Add job monitor** Create a new cron job monitor. - Action **Add project** Create a new project used to group monitors. - Action **Add server** Register a new server for back-up monitoring. - Action **Add SSL certificate monitor** Register a new SSL/TLS certificate monitor. - Action **Delete back-up** Delete a back-up by server ID and username. - Action **Delete job monitor** Delete a job monitor by ID. - Action **Delete project** Delete a project by ID. - Action **Delete server** Delete a server by ID. - Action **Delete SSL certificate monitor** Delete an SSL certificate monitor by ID. - Action **Get back-up** Get details of one back-up by server ID and username. - Action **Get job monitor** Get details of one job monitor by ID. - Action **Get project** Get details of one project by ID. - Action **Get server** Get details of one server by ID. - Action **Get SSL certificate monitor** Get details of one SSL certificate monitor by ID. - Action **Get user** Get details of one user by ID. - Action **List job monitors** List all registered job monitors for the company. - Action **List notifications** List all notifications (monitor failures, SSL certificate status changes, etc), paginated. - Action **List projects** List all projects. - Action **List servers** List all registered servers. - Action **List SSL certificate monitors** List all registered SSL/TLS certificate monitors. - Action **List users** List all users within the organization. - 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. ## Each app on its own - [ **Cronly** Cronly helps you manage your cron jobs in the cloud with built-in monitoring.](https://apiant.ai/connections/cronly) - [ **GitHub** GitHub is the perfect place to share code and work collaboratively on private and open source software.](https://apiant.ai/connections/github) Reviews ## What our customers say ## More from Cronly - [ **Cronly to crob.at** Pokémon team sharing and type chart data](https://apiant.ai/connect/cronly-to-crob-at) - [ **Cronly to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/cronly-to-hubspot) - [ **Cronly to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/cronly-to-salesforce) - [ **Cronly to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/cronly-to-slack) - [ **Cronly to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/cronly-to-google-sheets) - [ **Cronly to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/cronly-to-gmail) ## More into GitHub - [ **ActiveCampaign to GitHub** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-github) - [ **Airtable to GitHub** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-github) - [ **Asana to GitHub** Asana is a collaborative information manager for workspace.](https://apiant.ai/connect/asana-to-github) - [ **ClickUp to GitHub** ClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.](https://apiant.ai/connect/clickup-to-github) - [ **Discord to GitHub** Discord is an all-in-one voice and text chat for gamers.](https://apiant.ai/connect/discord-to-github) - [ **Freshdesk to GitHub** Freshdesk is a cloud-based customer support and helpdesk platform.](https://apiant.ai/connect/freshdesk-to-github) Questions ## Cronly and GitHub, answered ### ### What can start an automation from Cronly? Any of Cronly's 1 trigger in the catalog, including Trigger Activated. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in GitHub when something happens in Cronly? Any of GitHub's 19 actions, including Create Branch, Create Comment, Create Gist and Create Issue. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from GitHub to Cronly? Yes. When something happens in GitHub, your agent can act in Cronly too. This page covers both directions: GitHub's triggers and Cronly's actions are listed here as well. ### ### Do I have to build a connector for Cronly or GitHub? 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. ### ### Can my AI client use Cronly and GitHub without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### 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.