Integration
Connect ilert to RotaCloud
When New or Updated Incident fires in ilert, your agent runs Create User in RotaCloud. 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 RotaCloud 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 can start in RotaCloud
When New or Updated Incident in ilert
then Create User in RotaCloud
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 RotaCloud
Triggers and actions 1 trigger · 35 actions
- 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.
- 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.
- 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).
- 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.
- Create Incident
Creates a new incident in ilert, optionally marking affected services and adding responders. Depending on the affected services, subscribers may be notified.
- 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.
- Get alert
Returns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders.
- Get incident
Returns a single ilert incident by its id, including its status, severity, affected services and responders.
- Get maintenance window
Fetches a maintenance window by ID. An error occurs if the maintenance window is not found.
- List Alert Sources
Returns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy.
- List incidents
Returns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date.
- List users
Returns the users in your ilert account, with their name, email, role and contact settings.
- Resolve Incident
Resolves an ilert alert (formerly called an incident), closing it and stopping further escalation.
- Assign User to Location
Adds a RotaCloud user to a location, keeping the locations they are already assigned to.
- Assign User to Role
Adds a role to a RotaCloud user's roles, keeping the roles they already have.
- Create Leave
Creates leave within RotaCloud.
- Create Location
Creates a location within RotaCloud.
- Create Role
Creates a role within RotaCloud.
- Create Shift
Creates a shift within RotaCloud.
- Create User
Creates a user within RotaCloud.
- Delete Location
Deletes a location from the RotaCloud account.
- Delete Role
Deletes a role from the RotaCloud account.
- Delete User
Deletes a user from the RotaCloud account.
- Find Leave by ID
Fetches a leave request by ID, with its employee, leave type, dates, status and messages. An error occurs if the leave is not found.
- Find Location by ID
Returns the RotaCloud location with the specified ID.
- Find Location by Name
Returns the RotaCloud locations whose name matches the specified name (case-insensitive).
- Find Role by ID
Returns the RotaCloud role with the specified ID.
- Find Role by Name
Returns the roles whose name matches the specified name.
- Find Shift by ID
Fetches a shift by ID, with its times, location, role, assigned employee, notes and whether it is published or open. An error occurs if the shift is not found.
- Find User by Email
Returns the RotaCloud user whose email address matches the specified email.
- Find User by ID
Retrieves a single RotaCloud user by their ID.
- Unassign User From Location
Removes a user from one location in RotaCloud, keeping their other location assignments.
- Unassign User From Role
Unssigns a user from a role within RotaCloud.
- Update Location
Updates an existing RotaCloud location's name, address, geolocation or timezone. Fields left blank are left unchanged.
- Update Role
Updates a role within RotaCloud.
- Update User
Updates an existing user by ID
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 RotaCloud
Postman to RotaCloudPostman is a platform for building and testing APIs.
HubSpot to RotaCloudHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to RotaCloudGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to RotaCloudGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
ilert and RotaCloud, 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 RotaCloud when something happens in ilert?
Any of RotaCloud's 23 actions, including Create Leave, Create Location, Create Role and Create Shift. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from RotaCloud to ilert?
RotaCloud has no triggers in the catalog today, so automations start in ilert. If you need the other direction, ask: your agent reads RotaCloud's API documentation and adds it.
Do I have to build a connector for ilert or RotaCloud?
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 RotaCloud 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.