Integration
Connect Casebook and Coro
When New Case fires in Casebook, your agent runs Add Ticket Comment in Coro, or New Audit Log Entry in Coro to Create a Note in Casebook. 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 Casebook and Coro 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 Casebook and Coro can do together
From Casebook to Coro
When New Case in Casebook
then Add Ticket Comment in Coro
When New Intake Report in Casebook
then Perform Ticket Action in Coro
From Coro to Casebook
When New Audit Log Entry in Coro
then Create a Note in Casebook
When New Device in Coro
then Add a Person to a Case in Casebook
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 Casebook and Coro
Triggers and actions 7 triggers · 30 actions
Trigger
New CaseTriggers when a new case is created in Casebook.
Trigger
New Intake ReportTriggers when a new intake report is created in Casebook.
Trigger
New PersonTriggers when a new person is created in Casebook.
Action
Add a Person to a CaseAdds a person to a Casebook case.
Action
Create a CaseCreates a new case in Casebook with a name, description and case type.
Action
Create an Intake ReportCreates a new intake report in Casebook with a name, narrative and report type.
Action
Create a NoteCreates a note in Casebook, optionally attached to a person, case or other record.
Action
Create a PersonCreates a new person in Casebook with their name and basic demographics.
Action
Create a ProviderCreates a new provider in Casebook with a name and contact details.
Action
Delete a PersonDeletes a person in Casebook. The record is hidden from view, not permanently purged.
Action
Find PeopleFinds Casebook people by first name, last name or date of birth and returns the first match.
Action
Get a CaseReturns one Casebook case by ID, including its name and description.
Action
Get an Intake ReportReturns one Casebook intake report by ID, including its name, narrative and when it was reported.
Action
Get a PersonReturns one Casebook person by ID, including name, date of birth and other demographics.
Action
Get a ProviderReturns one Casebook provider by ID, including its name, email and phone number.
Action
Update a CaseUpdates a Casebook case's name, description or goals. Only the fields you fill in are changed.
Action
Update a PersonUpdates a Casebook person's name or demographics. Only the fields you fill in are changed.
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.
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 Casebook
Casebook to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Casebook to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Casebook to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Casebook to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Casebook to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Casebook to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Coro
ActiveCampaign to CoroActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to CoroOrganize anything with Airtable, a modern database created for everyone.
Asana to CoroAsana is a collaborative information manager for workspace.
ClickUp to CoroClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Brevo to CoroBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to CoroCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Questions
Casebook and Coro, answered
What can start an automation from Casebook?
Any of Casebook's 3 triggers in the catalog, including New Case, New Intake Report and New Person. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Coro when something happens in Casebook?
Any of Coro's 16 actions, including Update User Protection, Add Portal User, Add Ticket Comment and Get Portal User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Coro to Casebook?
Yes. When something happens in Coro, your agent can act in Casebook too. This page covers both directions: Coro's triggers and Casebook's actions are listed here as well.
Do I have to build a connector for Casebook or Coro?
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 Casebook and Coro 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.