Build solutions, not workarounds.
What do you want Zoom and Spike.sh to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Zoom can start in Spike.sh
When New recording completed in Zoom
then Add alert rule in Spike.sh
When New webinar registrant in Zoom
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 Zoom and Spike.sh
Triggers and actions 15 triggers · 42 actions
Trigger
Meeting endedTriggered when a meeting ends.
Trigger
Meeting participant joinedTriggers when a participant joins a meeting.
Trigger
Meeting registration cancelledTriggered when a meeting registration is cancelled.
Trigger
Meeting startedTriggered when a meeting starts.
Trigger
New recording completedTriggered when a cloud recording is completed.
Trigger
New recording completed (all active licensed accounts)Triggered when a cloud recording is completed in any licensed active account.
Trigger
New recording completed (specified account)Triggered when a cloud recording is completed for the specified account.
Trigger
New webinar registrantTriggers when a new registrant is added to a Webinar.
Trigger
Recording completedTriggered when a recording completes.
Trigger
Upcoming meetingTriggered when a meeting is upcoming in the specified amount of time. NOTE: this trigger only fetches up to 300 meetings at a time. If more than 300 meetings are within the specified timeframe, those additional meetings will not be triggered.
Trigger
Upcoming meeting (all active licensed accounts)Triggered when a meeting is upcoming in the specified amount of time for any active licensed account. NOTE: this trigger only fetches up to 300 meetings at a time for each account. If more than 300 meetings are within the specified timeframe, those additional meetings will not be triggered.
Trigger
Upcoming meeting (specified account)Triggered when a meeting is upcoming in the specified amount of time for the specified account. NOTE: this trigger only fetches up to 300 meetings at a time. If more than 300 meetings are within the specified timeframe, those additional meetings will not be triggered.
Trigger
Upcoming meeting via integration setting (all active licensed accounts)Triggered when a meeting is upcoming in the amount of time given by the specified integration setting stored in a lookup table. The default is 30 minutes if the setting is not found.
Trigger
Webinar endedTriggered when a webinar ends.
Trigger
Webinar startedTriggered when a webinar starts.
Action
Add meeting registrantAdds a registrant to the specified meeting. The meeting must have been created with an approval_type of "0" or "1", in which registrants are either automatically or manually approved.
Action
Create meetingCreates a new meeting.
Action
Delete meetingDeletes the specified meeting.
Action
End meetingImmediately ends a meeting.
Action
Find meeting by agendaFinds a meeting that matches the provided agenda. An error occurs if zero or multiple meetings match.
Action
Get approved meeting registrantsReturns approved registrants (up to 300 max) registrants for the specified meeting.
Action
Get connection modeReturns the mode of the named Zoom connection, either Individual or Admin.
Action
Get meetingOutputs details for the specified meeting.
Action
Get meeting registrantReturns details for the specified registrant in the specified meeting.
Action
Get userReturns a Zoom user's profile and settings by user ID or email.
Action
Get user settingsOutputs all settings for the specified user.
Action
List cloud recordingsLists cloud recordings for a Zoom user within a date range.
Action
List meetingsLists a Zoom user's scheduled, live, or upcoming meetings.
Action
List usersLists the users on the Zoom account.
Action
Update meetingUpdates an existing meeting.
Action
Update meeting registrant statusUpdates a registrant's status for the specified meeting.
Action
Update user settingsUpdates the specified user's settings.
Action
Acknowledge incidentAcknowledge one or more Spike.sh incidents by counter id or incident id.
Action
Add alert ruleCreate a new alert routing/automation rule with conditions and actions.
Action
Add escalationCreates 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 integrationCreate a new integration for a team (source system that sends alerts into Spike).
Action
Add on-callCreate a new on-call schedule for a team.
Action
Add serviceCreate a new service in a team, with name and description.
Action
Create IncidentCreates 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 ruleArchives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents.
Action
Delete escalationArchives (soft-deletes) a Spike escalation policy by its ID.
Action
Escalate incidentEscalates one or more Spike incidents to the next step of their escalation policy.
Action
Get escalationGet escalation policy details by id.
Action
Get incidentFetch a single incident by counter id.
Action
Get integrationFetches 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 serviceGet a Spike service's details, along with its incidents and open-incident count.
Action
List alert rulesLists all alert rules (enabled and disabled) configured for a Spike team.
Action
List escalationsLists the escalation policies that belong to a Spike team.
Action
List incidentsLists the incidents for a Spike.sh team.
Action
List on-callsLists the on-call schedules for a team.
Action
List servicesLists the services in a Spike team.
Action
List teamsLists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team.
Action
Resolve incidentResolve one or more incidents by counter id array.
Action
Update alert ruleReplace an existing Spike alert rule's name, conditions and actions.
Action
Update escalationReplaces 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-callUpdates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action.
Action
Update serviceUpdates 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 Zoom
Zoom to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Zoom to Google SheetsGoogle Sheets
Zoom to ActiveCampaignActiveCampaign is a marketing automation, email marketing, and CRM platform.
Zoom to AirtableOrganize anything with Airtable, a modern database created for everyone.
Zoom to ClickUpClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Zoom to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
More into Spike.sh
HubSpot to Spike.shHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Spike.shSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Spike.shSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Spike.shGoogle Sheets
Gmail to Spike.shGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Spike.shGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Zoom and Spike.sh, answered
What can start an automation from Zoom?
Any of Zoom's 15 triggers in the catalog, including New recording completed, New recording completed (all active licensed accounts), New recording completed (specified account) and New webinar registrant. 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 Zoom?
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 Zoom?
Spike.sh has no triggers in the catalog today, so automations start in Zoom. 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 Zoom 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.
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.