--- title: "Connect Cronly and ilert - APIANT.ai" description: "When \"Trigger Activated\" fires in Cronly, your agent runs \"Find User on Call\" in ilert, or \"New or Updated Incident\" in ilert to \"Add project\" in Cronly." canonical: "https://apiant.ai/connect/cronly-to-ilert" --- # Connect Cronly and ilert When **Trigger Activated** fires in [Cronly](https://apiant.ai/connections/cronly), your agent runs **Find User on Call** in [ilert](https://apiant.ai/connections/ilert), or **New or Updated Incident** in ilert 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 ilert **1** trigger ilert **12** 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 ilert 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 ilert can do together ### From Cronly to ilert - When **Trigger Activated** in Cronly then **Find User on Call** in ilert - When **Trigger Activated** in Cronly then **Add Alert** in ilert ### From ilert to Cronly - When **New or Updated Incident** in ilert then **Add project** in Cronly - When **New or Updated Incident** in ilert 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 ilert ## Triggers and actions 2 triggers · 34 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 or Updated Incident** Triggers when an incident (alert) on the chosen ilert alert source is created or changes: assigned, escalated, accepted, raised, commented on, resolved, or a responder is added or removed. - Action **Accept Incident** Accepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert. - Action **Add Alert** Creates an alert in ilert on the chosen alert source, which then escalates according to the source's escalation policy (or a policy or responders you specify). - Action **Add maintenance window** Creates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time. - Action **Create Incident** Creates a new incident in ilert, optionally marking affected services and adding responders. Depending on the affected services, subscribers may be notified. - Action **Find User on Call** Finds the user currently on call for an on-call schedule, along with the start and end of their current shift. Returns found=false when nobody is on call. - Action **Get alert** Returns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders. - Action **Get incident** Returns a single ilert incident by its id, including its status, severity, affected services and responders. - Action **Get maintenance window** Fetches a maintenance window by ID. An error occurs if the maintenance window is not found. - Action **List Alert Sources** Returns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy. - Action **List incidents** Returns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date. - Action **List users** Returns the users in your ilert account, with their name, email, role and contact settings. - Action **Resolve Incident** Resolves an ilert alert (formerly called an incident), closing it and stopping further escalation. ## 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) - [ **ilert** ilert is a platform for alerting, on-call management, and status pages.](https://apiant.ai/connections/ilert) 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](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 ilert - [ **HubSpot to ilert** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-ilert) - [ **Google Sheets to ilert** Google Sheets](https://apiant.ai/connect/google-sheets-to-ilert) - [ **Gmail to ilert** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-ilert) - [ **Google Calendar to ilert** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-ilert) - [ **Google Drive to ilert** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-ilert) - [ **ActiveCampaign to ilert** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-ilert) Questions ## Cronly and ilert, 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 ilert when something happens in Cronly? Any of ilert's 12 actions, including Create Incident, Accept Incident, Add Alert and Add maintenance window. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from ilert to Cronly? Yes. When something happens in ilert, your agent can act in Cronly too. This page covers both directions: ilert's triggers and Cronly's actions are listed here as well. ### ### Do I have to build a connector for Cronly or ilert? 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 ilert 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.