--- title: "Connect Wachete and ilert - APIANT.ai" description: "When \"New notification for monitor\" fires in Wachete, your agent runs \"Find User on Call\" in ilert." canonical: "https://apiant.ai/connect/ilert-to-wachete" --- # Connect Wachete and ilert When **New notification for monitor** fires in [Wachete](https://apiant.ai/connections/wachete), your agent runs **Find User on Call** in [ilert](https://apiant.ai/connections/ilert), or **New or Updated Incident** in ilert to **Create monitor** in Wachete. Describe the whole flow and it is built, tested on every scenario and kept running. Wachete **2** triggers Wachete **7** 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 Wachete 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 Wachete and ilert can do together ### From Wachete to ilert - When **New notification for monitor** in Wachete then **Find User on Call** in ilert - When **Any new notification** in Wachete then **Add Alert** in ilert ### From ilert to Wachete - When **New or Updated Incident** in ilert then **Create monitor** in Wachete - When **New or Updated Incident** in ilert then **Update monitor** in Wachete 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 Wachete and ilert ## Triggers and actions 3 triggers · 19 actions - Trigger **Any new notification** Fires when there is a new change notification from any monitor in your Wachete account. - Trigger **New notification for monitor** Fires when there is a new change notification from the specified Wachete monitor (taskId). - Action **Create monitor** Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes. - Action **Delete monitor** Delete a Wachete monitor by its ID. - Action **Get monitor** Get information about a specific Wachete monitor by its ID. - Action **Get monitor data** Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range. - Action **List folders** List folder contents, optionally under a parent folder. - Action **List notifications** List change notifications, optionally filtered by monitor (taskId) and date range. - Action **Update monitor** Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record. - 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 - [ **Wachete** Wachete monitors web pages (or parts of pages) for changes and notifies you when the text changes or...](https://apiant.ai/connections/wachete) - [ **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 Wachete - [ **Wachete to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/wachete-to-salesforce) - [ **Wachete to ActiveCampaign** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/wachete-to-activecampaign) - [ **Wachete to JIRA** Atlassian JIRA Cloud — issue tracking and project management.](https://apiant.ai/connect/wachete-to-jira) - [ **Wachete to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/wachete-to-zoom) - [ **Wachete to Webflow** Webflow is a professional website builder and CMS for designing, building, and launching responsive...](https://apiant.ai/connect/wachete-to-webflow) - [ **Wachete to Anthropic** Anthropic builds Claude, a family of large language models.](https://apiant.ai/connect/wachete-to-anthropic) ## 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 ## Wachete and ilert, answered ### ### What can start an automation from Wachete? Any of Wachete's 2 triggers in the catalog, including New notification for monitor and Any new notification. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in ilert when something happens in Wachete? 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 Wachete? Yes. When something happens in ilert, your agent can act in Wachete too. This page covers both directions: ilert's triggers and Wachete's actions are listed here as well. ### ### Do I have to build a connector for Wachete 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 Wachete 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.