--- title: "Connect Cronly and incident.io - APIANT.ai" description: "When \"Trigger Activated\" fires in Cronly, your agent runs \"Find Users On-Call\" in incident.io, or \"New Incident\" in incident.io to \"Add project\" in Cronly." canonical: "https://apiant.ai/connect/cronly-to-incident-io" --- # Connect Cronly and incident.io When **Trigger Activated** fires in [Cronly](https://apiant.ai/connections/cronly), your agent runs **Find Users On-Call** in [incident.io](https://apiant.ai/connections/incident-io), or **New Incident** in incident.io 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 incident.io **1** trigger incident.io **10** 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 incident.io 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 incident.io can do together ### From Cronly to incident.io - When **Trigger Activated** in Cronly then **Find Users On-Call** in incident.io - When **Trigger Activated** in Cronly then **Add follow-up** in incident.io ### From incident.io to Cronly - When **New Incident** in incident.io then **Add project** in Cronly - When **New Incident** in incident.io 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 incident.io ## Triggers and actions 2 triggers · 32 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 **New Incident** Triggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode. - Action **Add follow-up** Creates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels. - Action **Add incident update** Shares an update on an incident: a message, a move to a new status, a new severity, or any combination. - Action **Create Incident** Creates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields. - Action **Find Users On-Call** Finds the users on-call for a schedule over a window of time (or right now), returning each effective shift with its user after overrides are applied. - Action **Get incident** Returns a single incident, including its status, severity, role assignments, timestamps and custom field values. - Action **Get Schedule** Returns a single on-call schedule, including its rotations, time zone and current shifts. - Action **List actions** Returns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date. - Action **List schedules** Returns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift. - Action **List severities** Returns every incident severity configured for your incident.io organisation. - Action **List users** Returns the users in your incident.io account, optionally filtered by email address or Slack user ID. ## 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) - [ **incident.io** incident.io is an incident management platform, designed for your entire organisation.](https://apiant.ai/connections/incident-io) 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 incident.io - [ **HubSpot to incident.io** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-incident-io) - [ **Google Sheets to incident.io** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-incident-io) - [ **Gmail to incident.io** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-incident-io) - [ **Google Calendar to incident.io** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-incident-io) - [ **Google Drive to incident.io** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-incident-io) - [ **ActiveCampaign to incident.io** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-incident-io) Questions ## Cronly and incident.io, 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 incident.io when something happens in Cronly? Any of incident.io's 10 actions, including Create Incident, Add follow-up, Add incident update and Find Users On-Call. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from incident.io to Cronly? Yes. When something happens in incident.io, your agent can act in Cronly too. This page covers both directions: incident.io's triggers and Cronly's actions are listed here as well. ### ### Do I have to build a connector for Cronly or incident.io? 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 incident.io 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.