--- title: "Connect Clio to Spike.sh - APIANT.ai" description: "When \"Matter Status Updated\" fires in Clio, your agent runs \"Add alert rule\" in Spike.sh." canonical: "https://apiant.ai/connect/clio-to-spike-sh" --- # Connect Clio to Spike.sh When **Matter Status Updated** fires in [Clio](https://apiant.ai/connections/clio), your agent runs **Add alert rule** in [Spike.sh](https://apiant.ai/connections/spike-sh). Describe the whole flow and it is built, tested on every scenario and kept running. Clio **8** triggers Clio **38** actions Spike.sh **25** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Clio and Spike.sh to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What Clio can start in Spike.sh - When **Matter Status Updated** in Clio then **Add alert rule** in Spike.sh - When **New Activity** in Clio then **Add escalation** 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 Clio and Spike.sh ## Triggers and actions 8 triggers · 63 actions - Trigger **Matter Status Updated** Triggers when the status of a matter has changed. - Trigger **New Activity** Triggers when a new activity is created. - Trigger **New Calendar Entry** Triggers when a new calendar entry is created. - Trigger **New Communication** Triggers when a new communication is created. - Trigger **New Contact** Triggers when a new contact is created. - Trigger **New Matter** Triggers when a new matter is created. - Trigger **New Task** Triggers when a new task is created. - Trigger **Task Status Updated** Triggers when the status of a task has changed. - Action **Create Calendar Entry** Creates a new calendar entry. - Action **Create Communication** Creates a new communication. - Action **Create Company Contact** Creates a company contact. - Action **Create Expense Entry (Activity)** Creates a new expense entry. - Action **Create Matter** Adds a new matter to Clio Manage. - Action **Create Matter Folder** Creates a new folder in a matter. - Action **Create Matter Note** Creates a new matter note. - Action **Create Person Contact** Creates a person contact. - Action **Create Task** Creates a new task. - Action **Create Time Entry (Activity)** Creates a new time entry. - Action **Delete activity** Delete an activity. - Action **Delete calendar entry** Delete a calendar entry. - Action **Delete contact** Delete a contact. - Action **Delete matter** Delete a matter. - Action **Delete task** Delete a task. - Action **Find Company Contact** Returns the company contacts that match the search text. - Action **Find Matter** Returns the matters that match the specified search text and optional filters - Action **Find Newest Matter by Client Email** Returns the most recently created matter for the client with the given email address. - Action **Find Person Contact** Find a person contact by ID, name, title, email address, address, phone number, web site, instant messenger, custom fields, related matter name, or company name matching a given string. - Action **Find User** Find a user by name. - Action **Get activity** Fetches an activity (time or expense entry) by ID. An error occurs if the activity is not found. - Action **Get calendar entry** Returns one calendar entry by id, including summary, start and end times. - Action **Get communication** Returns one communication by id. - Action **Get contact** Retrieve a contact (person or company) by id. - Action **Get document** Retrieve document metadata by id. - Action **Get matter** Retrieve a matter by id. - Action **Get task** Retrieve a task by id. - Action **List activities** List all activities. - Action **List contacts** List all contacts. - Action **List practice areas** List practice areas. - Action **List tasks** List all tasks. - Action **List users** List firm users. - Action **Update activity** Update an activity. - Action **Update calendar entry** Update a calendar entry. - Action **Update Matter** Update an existing matter. - Action **Update Person Contact** Updates an existing person contact. - Action **Update Task** Updates a task. - Action **Upload Document to Matter** Uploads a file from a URL into a Clio matter's documents and marks it fully uploaded. - Action **Acknowledge incident** Acknowledge one or more Spike.sh incidents by counter id or incident id. - Action **Add alert rule** Create a new alert routing/automation rule with conditions and actions. - Action **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. - Action **Add integration** Create a new integration for a team (source system that sends alerts into Spike). - Action **Add on-call** Create a new on-call schedule for a team. - Action **Add service** Create a new service in a team, with name and description. - Action **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. - Action **Delete alert rule** Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents. - Action **Delete escalation** Archives (soft-deletes) a Spike escalation policy by its ID. - Action **Escalate incident** Escalates one or more Spike incidents to the next step of their escalation policy. - Action **Get escalation** Get escalation policy details by id. - Action **Get incident** Fetch a single incident by counter id. - Action **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. - Action **Get service** Get a Spike service's details, along with its incidents and open-incident count. - Action **List alert rules** Lists all alert rules (enabled and disabled) configured for a Spike team. - Action **List escalations** Lists the escalation policies that belong to a Spike team. - Action **List incidents** Lists the incidents for a Spike.sh team. - Action **List on-calls** Lists the on-call schedules for a team. - Action **List services** Lists the services in a Spike team. - Action **List teams** Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team. - Action **Resolve incident** Resolve one or more incidents by counter id array. - Action **Update alert rule** Replace an existing Spike alert rule's name, conditions and actions. - Action **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. - Action **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. - Action **Update service** Updates the name and/or description of an existing Spike.sh service. ## Each app on its own - [ **Clio** Clio is a practice management platform that helps lawyers work more efficiently by making it easy to do...](https://apiant.ai/connections/clio) - [ **Spike.sh** Spike is an incident management system with unlimited alerts and on-call schedules](https://apiant.ai/connections/spike-sh) Reviews ## What our customers say ## More from Clio - [ **Clio to PandaDoc** PandaDoc helps you build and deliver sales quotes and proposals and track presentations and close deals...](https://apiant.ai/connect/clio-to-pandadoc) - [ **Clio to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/clio-to-hubspot) - [ **Clio to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/clio-to-salesforce) - [ **Clio to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/clio-to-slack) - [ **Clio to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/clio-to-google-sheets) - [ **Clio to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/clio-to-gmail) ## More into Spike.sh - [ **HubSpot to Spike.sh** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-spike-sh) - [ **Salesforce to Spike.sh** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-spike-sh) - [ **Slack to Spike.sh** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-spike-sh) - [ **Google Sheets to Spike.sh** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-spike-sh) - [ **Gmail to Spike.sh** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-spike-sh) - [ **Google Calendar to Spike.sh** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-spike-sh) Questions ## Clio and Spike.sh, answered ### ### What can start an automation from Clio? Any of Clio's 8 triggers in the catalog, including Matter Status Updated, New Activity, New Calendar Entry and New Communication. 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 Clio? 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 Clio? Spike.sh has no triggers in the catalog today, so automations start in Clio. 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 Clio 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 Clio 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.