--- title: "Connect Casting42 to Spike.sh - APIANT.ai" description: "When \"New Casting\" fires in Casting42, your agent runs \"Add alert rule\" in Spike.sh." canonical: "https://apiant.ai/connect/casting42-to-spike-sh" --- # Connect Casting42 to Spike.sh When **New Casting** fires in [Casting42](https://apiant.ai/connections/casting42), 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. Casting42 **6** triggers Casting42 **15** 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 Casting42 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 Casting42 can start in Spike.sh - When **New Casting** in Casting42 then **Add alert rule** in Spike.sh - When **New Contact** in Casting42 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 Casting42 and Spike.sh ## Triggers and actions 6 triggers · 40 actions - Trigger **New Casting** Triggers when a casting has been created in your Casting42 Database. - Trigger **New Contact** Triggers when a contact has been added to your Casting42 database. - Trigger **New Talent** Triggers when a new talent is added in Casting42. Casting42 only shares talents whose "Allow API response" setting is turned on, so talents without it never trigger this. - Trigger **Updated Casting** Triggers when the data of a casting has been updated. - Trigger **Updated Contact** Triggers when the data of a contact has been updated in your Casting42 database. - Trigger **Updated Talent** Triggers when a talent is updated in Casting42. Casting42 only shares talents whose "Allow API response" setting is turned on, so talents without it never trigger this. - Action **Add File to Talent** Uploads a file such as a resume or PDF document to a talent's profile. - Action **Add Mediafile to Talent** Uploads a video or audio media file to a talent's profile in Casting42. - Action **Add Talent to Group** Adds one or more talents to an existing Casting42 group. - Action **Create Casting** Creates a new casting project in Casting42 and returns it along with its talent sign-up link. - Action **Create Contact** Creates a new contact in Casting42 with name, email, company, phone, language and address. - Action **Create Group** Creates a new group in Casting42 for organizing talents. - Action **Create or Update Candidate** Adds a talent to a casting as a candidate, or updates the candidate's tags if the talent is already in that casting. - Action **Create Talent** Creates a new talent profile in your Casting42 database and returns the created talent. - Action **Find Casting** Finds a casting by its tag and returns the full casting record. - Action **Get Contact** Returns a single Casting42 contact identified by its tag. - Action **Get Group** Returns a Casting42 group and its talents by the group's tag. - Action **Get Talent** Returns a single talent record, including custom fields and skills, by its tag. - Action **Update Casting** Updates an existing casting in Casting42, such as its name, description, dates, locations and sharing options. Fields left blank are not changed. - Action **Update Contact** Updates an existing contact in Casting42. Only the fields you fill in are changed. - Action **Update Talent** Updates an existing talent in Casting42, identified by its tag. Fields left blank keep their current values. - 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 - [ **Casting42** Casting42 is a customizable database for casting directors, production companies, extras agencies, and...](https://apiant.ai/connections/casting42) - [ **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 Casting42 - [ **Casting42 to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/casting42-to-hubspot) - [ **Casting42 to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/casting42-to-salesforce) - [ **Casting42 to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/casting42-to-slack) - [ **Casting42 to Google Sheets** Google Sheets](https://apiant.ai/connect/casting42-to-google-sheets) - [ **Casting42 to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/casting42-to-gmail) - [ **Casting42 to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/casting42-to-google-calendar) ## 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](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 ## Casting42 and Spike.sh, answered ### ### What can start an automation from Casting42? Any of Casting42's 6 triggers in the catalog, including New Casting, New Contact, New Talent and Updated Casting. 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 Casting42? 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 Casting42? Spike.sh has no triggers in the catalog today, so automations start in Casting42. 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 Casting42 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 Casting42 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.