Integration
Connect ilert and Ninety
When New or Updated Incident fires in ilert, your agent runs Create Issue in Ninety, or New Issue Created in Ninety 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 Ninety 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)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 Ninety can do together
From ilert to Ninety
When New or Updated Incident in ilert
then Create Issue in Ninety
When New or Updated Incident in ilert
then Update Issue in Ninety
From Ninety to ilert
When New Issue Created in Ninety
then Find User on Call in ilert
When New Measurable in Ninety
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 Ninety
Triggers and actions 5 triggers · 33 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 Issue CreatedTriggered when a new issue is created in Ninety, optionally only on one team or only short-term vs long-term issues.
Trigger
New MeasurableTriggered when a new measurable (KPI) is added to your Ninety scorecard, optionally only those tracked over a given period like weekly or monthly.
Trigger
New TeamTriggered when a new team is created in your Ninety company.
Trigger
To-Do Created, Updated, or DeletedTriggered when a to-do is created or changed in Ninety — including being completed or archived — optionally only on one team or only personal to-dos. Ninety's API does not report hard deletions, so a removed to-do simply stops appearing rather than firing this trigger.
Action
Create IssueCreates an issue on a Ninety team's issues list.
Action
Create MilestoneCreates a milestone on a Ninety rock, with a title and due date.
Action
Create RockCreates a rock (a quarterly goal) for a Ninety team, with a due date, status and level.
Action
Create To-DoCreates a to-do on a Ninety team, with a due date and optional description.
Action
Delete IssueDeletes an existing Issue in Ninety by its ID.
Action
Delete Measurable NoteDeletes the note on a Measurable for one scorecard period.
Action
Delete Measurable ScoreDeletes the score on a Measurable for one scorecard period.
Action
Delete RockDeletes a Rock in Ninety by its ID. Returns the deleted Rock's ID along with the status Ninety returned.
Action
Delete To-DoDeletes a to-do in Ninety by its ID. Use it to remove a to-do that was created by mistake or is no longer needed.
Action
Find IssueSearches Ninety for issues matching the words you provide, optionally narrowed to one team or to short-term vs long-term issues. Returns the matching issues.
Action
Find MeasurableSearches Ninety's scorecard for measurables (KPIs) matching the words you provide, optionally limited to a tracking period like weekly or monthly. Returns the matching measurables.
Action
Find MilestoneSearches Ninety for milestones by title. Ninety carries milestones on their rocks, so this reads the rocks (optionally just one team's) and returns the milestones whose title matches, optionally limited to a single rock.
Action
Find RockSearches Ninety for rocks (quarterly goals) matching the words you provide, optionally narrowed to one team or one status. Returns the matching rocks.
Action
Find TeamReturns the teams in your Ninety company, optionally only those whose name contains the words you provide. Use it to get the team ID other Ninety actions need.
Action
Find To-DoSearches Ninety for to-dos matching the words you provide, optionally narrowed to one team, to personal to-dos, or to finished vs open ones. Returns the matching to-dos.
Action
Update IssueChanges an existing issue in Ninety — its title, detail, team, priority, short-term/long-term setting, or whether it is solved. Fields you leave blank are left as they are.
Action
Update Measurable NoteSaves the note on a Ninety scorecard measurable for one period, replacing any note already there.
Action
Update Measurable ScoreRecords the score on a Ninety scorecard measurable for one period, replacing any score already there.
Action
Update MilestoneChanges an existing milestone in Ninety — its title, detail, due date, owner, or whether it is finished. Fields you leave blank are left as they are.
Action
Update RockChanges an existing rock (quarterly goal) in Ninety — its title, detail, status, owner, team, quarter, due date, or whether it is archived. Fields you leave blank are left as they are.
Action
Update To-DoChanges an existing to-do in Ninety — its title, detail, due date, owner, team, repeat setting, or whether it is done or archived. Fields you leave blank are left as they are.
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 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.
ilert to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Ninety
HubSpot to NinetyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to NinetyGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to NinetyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to NinetyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to NinetyGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to NinetyMailchimp marketing automation and email platform.
Questions
ilert and Ninety, 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 Ninety when something happens in ilert?
Any of Ninety's 21 actions, including Create Issue, Create Milestone, Create Rock and Create To-Do. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Ninety to ilert?
Yes. When something happens in Ninety, your agent can act in ilert too. This page covers both directions: Ninety's triggers and ilert's actions are listed here as well.
Do I have to build a connector for ilert or Ninety?
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 Ninety 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.