Integration
Connect Coro to RotaCloud
When New Audit Log Entry fires in Coro, 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 Coro 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)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 Coro can start in RotaCloud
When New Audit Log Entry in Coro
then Create User in RotaCloud
When New Device in Coro
then Update 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 Coro and RotaCloud
Triggers and actions 4 triggers · 39 actions
Trigger
New Audit Log EntryTriggers when a new audit log entry is recorded in the workspace.
Trigger
New DeviceTriggers when a new device is enrolled in the workspace.
Trigger
New Protected UserTriggers when a new user appears in the workspace.
Trigger
New TicketTriggers when a new security ticket is created in the workspace.
Action
Add Portal UserInvites a user to the Coro end-user portal.
Action
Add Ticket CommentAdds a comment to a security ticket.
Action
Get Portal UserReturns one end-user portal user by ID.
Action
Get TicketReturns one security ticket by ID.
Action
Get UserReturns one user by ID.
Action
Get WorkspaceReturns the details of the connected Coro workspace.
Action
List DevicesReturns the protected devices in the workspace.
Action
List Portal UsersReturns the users of the Coro end-user portal.
Action
List Ticket ActionsReturns the actions that can be taken on a security ticket.
Action
List Ticket CommentsReturns the comments on a security ticket.
Action
List TicketsReturns security tickets in the workspace, optionally filtered by processed state and time range.
Action
List UsersReturns the users in the workspace, optionally filtered by email or name.
Action
Perform Ticket ActionRuns an action on a security ticket, such as marking it processed.
Action
Search Audit LogsReturns audit log entries for the workspace within an optional time range.
Action
Search WorkspacesReturns the child workspaces the connected workspace can access, optionally filtered by a search term.
Action
Update User ProtectionTurns Coro protection on or off for a user, identified by email.
Action
Assign User to LocationAdds a RotaCloud user to a location, keeping the locations they are already assigned to.
Action
Assign User to RoleAdds a role to a RotaCloud user's roles, keeping the roles they already have.
Action
Create LeaveCreates leave within RotaCloud.
Action
Create LocationCreates a location within RotaCloud.
Action
Create RoleCreates a role within RotaCloud.
Action
Create ShiftCreates a shift within RotaCloud.
Action
Create UserCreates a user within RotaCloud.
Action
Delete LocationDeletes a location from the RotaCloud account.
Action
Delete RoleDeletes a role from the RotaCloud account.
Action
Delete UserDeletes a user from the RotaCloud account.
Action
Find Leave by IDFetches a leave request by ID, with its employee, leave type, dates, status and messages. An error occurs if the leave is not found.
Action
Find Location by IDReturns the RotaCloud location with the specified ID.
Action
Find Location by NameReturns the RotaCloud locations whose name matches the specified name (case-insensitive).
Action
Find Role by IDReturns the RotaCloud role with the specified ID.
Action
Find Role by NameReturns the roles whose name matches the specified name.
Action
Find Shift by IDFetches 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.
Action
Find User by EmailReturns the RotaCloud user whose email address matches the specified email.
Action
Find User by IDRetrieves a single RotaCloud user by their ID.
Action
Unassign User From LocationRemoves a user from one location in RotaCloud, keeping their other location assignments.
Action
Unassign User From RoleUnssigns a user from a role within RotaCloud.
Action
Update LocationUpdates an existing RotaCloud location's name, address, geolocation or timezone. Fields left blank are left unchanged.
Action
Update RoleUpdates a role within RotaCloud.
Action
Update UserUpdates 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 Coro
Coro to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Coro to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Coro to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Coro to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Coro to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Coro to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
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.
Salesforce to RotaCloudSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to RotaCloudSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
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
Coro and RotaCloud, answered
What can start an automation from Coro?
Any of Coro's 4 triggers in the catalog, including New Audit Log Entry, New Device, New Protected User and New Ticket. Describe the moment in plain language and your agent picks the right one.
What can your agent do in RotaCloud when something happens in Coro?
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 Coro?
RotaCloud has no triggers in the catalog today, so automations start in Coro. 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 Coro 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 Coro 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.