Integration
Connect Casebook to Spike.sh
When New Case fires in Casebook, your agent runs Add alert rule in Spike.sh. 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 Spike.sh 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 Casebook can start in Spike.sh
When New Case in Casebook
then Add alert rule in Spike.sh
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 Spike.sh
Triggers and actions 3 triggers · 39 actions
- New Case
Triggers when a new case is created in Casebook.
- New Intake Report
Triggers when a new intake report is created in Casebook.
- New Person
Triggers when a new person is created in Casebook.
- Add a Person to a Case
Adds a person to a Casebook case.
- Create a Case
Creates a new case in Casebook with a name, description and case type.
- Create an Intake Report
Creates a new intake report in Casebook with a name, narrative and report type.
- Create a Note
Creates a note in Casebook, optionally attached to a person, case or other record.
- Create a Person
Creates a new person in Casebook with their name and basic demographics.
- Create a Provider
Creates a new provider in Casebook with a name and contact details.
- Delete a Person
Deletes a person in Casebook. The record is hidden from view, not permanently purged.
- Find People
Finds Casebook people by first name, last name or date of birth and returns the first match.
- Get a Case
Returns one Casebook case by ID, including its name and description.
- Get an Intake Report
Returns one Casebook intake report by ID, including its name, narrative and when it was reported.
- Get a Person
Returns one Casebook person by ID, including name, date of birth and other demographics.
- Get a Provider
Returns one Casebook provider by ID, including its name, email and phone number.
- Update a Case
Updates a Casebook case's name, description or goals. Only the fields you fill in are changed.
- Update a Person
Updates a Casebook person's name or demographics. Only the fields you fill in are changed.
- Acknowledge incident
Acknowledge one or more Spike.sh incidents by counter id or incident id.
- Add alert rule
Create a new alert routing/automation rule with conditions and actions.
- Add escalation
Creates a new escalation policy for a Spike.sh team, defining who is notified, through which channel, and how long to wait between steps.
- Add integration
Create a new integration for a team (source system that sends alerts into Spike).
- Add on-call
Create a new on-call schedule for a team.
- Add service
Create a new service in a team, with name and description.
- Create Incident
Creates a Spike incident through one of your integrations and sends alerts. The integration decides which service and escalation policy the incident is routed to.
- Delete alert rule
Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents.
- Delete escalation
Archives (soft-deletes) a Spike escalation policy by its ID.
- Escalate incident
Escalates one or more Spike incidents to the next step of their escalation policy.
- Get escalation
Get escalation policy details by id.
- Get incident
Fetch a single incident by counter id.
- Get integration
Fetches an integration by its token, including its name, type, service, escalation settings and webhook URL. An error occurs if the integration is not found.
- Get service
Get a Spike service's details, along with its incidents and open-incident count.
- List alert rules
Lists all alert rules (enabled and disabled) configured for a Spike team.
- List escalations
Lists the escalation policies that belong to a Spike team.
- List incidents
Lists the incidents for a Spike.sh team.
- List on-calls
Lists the on-call schedules for a team.
- List services
Lists the services in a Spike team.
- List teams
Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team.
- Resolve incident
Resolve one or more incidents by counter id array.
- Update alert rule
Replace an existing Spike alert rule's name, conditions and actions.
- Update escalation
Replaces an existing escalation policy's name, steps and start delay. The whole policy is replaced, so send every step you want to keep.
- Update on-call
Updates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action.
- Update service
Updates the name and/or description of an existing Spike.sh service.
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 Spike.sh
Questions
Casebook and Spike.sh, 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 Spike.sh when something happens in Casebook?
Any of Spike.sh's 25 actions, including Create Incident, Update alert rule, Update escalation and Update on-call. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Spike.sh to Casebook?
Spike.sh has no triggers in the catalog today, so automations start in Casebook. If you need the other direction, ask: your agent reads Spike.sh's API documentation and adds it.
Do I have to build a connector for Casebook or Spike.sh?
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 Spike.sh 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.