Integration
Connect ilert and WebChange Detector
When New or Updated Incident fires in ilert, your agent runs Add URLs To Group in WebChange Detector, or New Changes Detected in WebChange Detector to Find User on Call in ilert. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want ilert and WebChange Detector to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)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)Example flows
What ilert and WebChange Detector can do together
From ilert to WebChange Detector
When New or Updated Incident in ilert
then Add URLs To Group in WebChange Detector
When New or Updated Incident in ilert
then Update URL in WebChange Detector
From WebChange Detector to ilert
When New Changes Detected in WebChange Detector
then Find User on Call in ilert
When New Changes Detected in WebChange Detector
then Add Alert in ilert
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 ilert and WebChange Detector
Triggers and actions 2 triggers · 28 actions
Trigger
New or Updated IncidentTriggers 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 IncidentAccepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert.
Action
Add AlertCreates 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 windowCreates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time.
Action
Create IncidentCreates 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 CallFinds 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 alertReturns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders.
Action
Get incidentReturns a single ilert incident by its id, including its status, severity, affected services and responders.
Action
Get maintenance windowFetches a maintenance window by ID. An error occurs if the maintenance window is not found.
Action
List Alert SourcesReturns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy.
Action
List incidentsReturns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date.
Action
List usersReturns the users in your ilert account, with their name, email, role and contact settings.
Action
Resolve IncidentResolves an ilert alert (formerly called an incident), closing it and stopping further escalation.
Trigger
New Changes DetectedTriggers when a check finds a page changed by more than its group's threshold; returns the comparison with its difference percentage and screenshot links.
Action
Add URLs To GroupAdds a URL to a group for desktop and mobile checks.
Action
Delete GroupDeletes a URL group.
Action
Delete URLDeletes a URL from the account.
Action
Get AccountReturns the account's details and plan.
Action
Get ComparisonReturns one comparison with its difference percentage and screenshots.
Action
Get GroupReturns one URL group with its schedule and settings.
Action
Get URLReturns one monitored URL with its title, status code and groups.
Action
Get WebsiteReturns one website with its settings.
Action
List BatchesReturns check batches with their status.
Action
List ComparisonsReturns screenshot comparisons, each with its difference percentage and links.
Action
List GroupsReturns the URL groups in the account.
Action
List URLsReturns the URLs in the account.
Action
List WebsitesReturns the websites in the account.
Action
Take ScreenshotsStarts taking screenshots of a group's URLs.
Action
Trigger Monitoring CheckStarts a monitoring check for a group right away.
Action
Update URLChanges the address of a URL and returns it.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from ilert
ilert to PremblyPrembly secures digital transactions in emerging markets with AI-powered identity verification and fraud...
ilert to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
ilert to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
ilert to MailchimpMailchimp marketing automation and email platform.
ilert to StripeStripe is a payment processing platform for online businesses.
ilert to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into WebChange Detector
HubSpot to WebChange DetectorHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to WebChange DetectorSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to WebChange DetectorSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to WebChange DetectorGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to WebChange DetectorGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to WebChange DetectorGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
ilert and WebChange Detector, answered
What can start an automation from ilert?
Any of ilert's 1 trigger in the catalog, including New or Updated Incident. Describe the moment in plain language and your agent picks the right one.
What can your agent do in WebChange Detector when something happens in ilert?
Any of WebChange Detector's 16 actions, including Update URL, Add URLs To Group, Get Account and Get Comparison. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from WebChange Detector to ilert?
Yes. When something happens in WebChange Detector, your agent can act in ilert too. This page covers both directions: WebChange Detector's triggers and ilert's actions are listed here as well.
Do I have to build a connector for ilert or WebChange Detector?
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 ilert and WebChange Detector 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.