Integration
Connect ilert and STORIS
When New or Updated Incident fires in ilert, your agent runs Add customer in STORIS, or New Activity in STORIS 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 STORIS 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 STORIS can do together
From ilert to STORIS
When New or Updated Incident in ilert
then Add customer in STORIS
When New or Updated Incident in ilert
then Add customer address in STORIS
From STORIS to ilert
When New Activity in STORIS
then Find User on Call in ilert
When New Opportunity in STORIS
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 STORIS
Triggers and actions 3 triggers · 40 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 ActivityTriggers when a new CRM activity is created in STORIS.
Trigger
New OpportunityTriggers when a new sales opportunity is created in STORIS.
Action
Add customerCreates a new customer in STORIS with a billing address and, optionally, a primary ship-to address.
Action
Add customer addressAdds a new deliver-to (ship to) address to an existing STORIS customer.
Action
Add orderCreates a new sales order in STORIS with its line items, optionally linked to an existing customer.
Action
Add purchase orderCreates a new purchase order to a vendor in STORIS, with one or more product line items.
Action
Add quoteCreates a quote in STORIS for a selling location with the given line items, optionally tied to a customer.
Action
Add relationshipCreates a new relationship (a NextGen CRM contact) in STORIS with a name and optional email, phone and description.
Action
Add service orderCreates a service order in STORIS for a completed sales order, listing the merchandise or miscellaneous items that need service.
Action
Create ActivityCreates a CRM activity (a task with a due date) in STORIS.
Action
Create OpportunityCreates a sales opportunity in STORIS.
Action
Delete orderDeletes a sales order in STORIS, recording the reason code for the deletion.
Action
Find activitiesFinds STORIS NextGen activities by owner, relationship, stage, status, due date or last update.
Action
Find Customers By EmailFinds STORIS customers whose email address matches, returning each customer's ID and name.
Action
Find customers by last nameReturns the STORIS customers whose last name matches, optionally narrowed by first name, city or zip code.
Action
Find customers by phoneReturns the STORIS customers whose phone number matches the one you supply.
Action
Find opportunitiesFinds STORIS NextGen opportunities matching the owner, relationship, stage, project type, status and date filters you supply.
Action
Find Orders By CustomerReturns the orders placed by a STORIS customer.
Action
Find Orders By EmailReturns the orders for a customer email address.
Action
Find Product By BarcodeReturns the STORIS product ID for a barcode.
Action
Find relationshipsFinds STORIS NextGen relationships by name, contact email and/or customer ID.
Action
Get CustomerReturns a STORIS customer's full details by customer ID.
Action
Get OrderReturns a STORIS sales order's details, including its line items and fulfillments, by order ID.
Action
Get ProductReturns a STORIS product's details by product ID, optionally priced for one location.
Action
Get Service OrderReturns a STORIS service order's details by service order ID.
Action
List purchase ordersReturns purchase orders from STORIS, optionally filtered by receiving location, type and status.
Action
Update activityUpdates an existing NextGen activity's subject, due date, owner, stage or related relationship.
Action
Update customerUpdates an existing STORIS customer's billing address, primary ship-to address, solicitation preference, customer type or statement delivery method.
Action
Update opportunityUpdates an existing STORIS NextGen opportunity, such as its subject, stage, owner, expected close date or value.
Action
Update orderUpdates an existing STORIS order's delivery date, delivery instructions, comments, handling method, delivery override or shipping address.
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 STORIS
HubSpot to STORISHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to STORISSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to STORISSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to STORISGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to STORISGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to STORISGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
ilert and STORIS, 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 STORIS when something happens in ilert?
Any of STORIS's 28 actions, including Create Activity, Create Opportunity, Update activity and Update customer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from STORIS to ilert?
Yes. When something happens in STORIS, your agent can act in ilert too. This page covers both directions: STORIS's triggers and ilert's actions are listed here as well.
Do I have to build a connector for ilert or STORIS?
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 STORIS 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.