Integration
Connect Teamup Calendar to Spike.sh
When something happens in Teamup Calendar, your agent does the next thing in Spike.sh. Describe it 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 Teamup Calendar 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 Teamup Calendar can start in Spike.sh
When New Event in Teamup Calendar
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 Teamup Calendar and Spike.sh
Triggers and actions 6 triggers · 36 actions
- Event Cancelled
Triggers when an event is cancelled (deleted) on your Teamup calendar. Polls the calendar's change feed and emits each newly deleted event.
- Event Ended
Triggers when an event on your Teamup calendar has ended. Polls the last day of events and emits each one whose end time has passed.
- Event Start
Triggers when an event on your Teamup calendar has started. Polls the last day of events and emits each one whose start time has passed.
- New Event
Triggers when a new event is added to your Teamup calendar.
- New Event Matching Search
Triggers when a new event matching your search keywords appears on your Teamup calendar.
- New or Updated Event
Triggers when an event is added or changed on your Teamup calendar.
- Add Comment
Posts a comment on an event in your Teamup calendar. Returns the created comment, including its id and creation time.
- Add Signup
Signs a person up for an event on your Teamup calendar. Returns the created signup, including its id and creation time.
- Create Event
Creates a new event on your Teamup calendar, including any custom event fields defined on the calendar. Returns the created event.
- Delete Event
Deletes an event from your Teamup calendar. Returns an undo token for the deletion.
- Find Event Matching Remote ID
Finds the event on your Teamup calendar carrying a given remote id. Searches the supplied date range and returns the matching event.
- Find Events
Searches your Teamup calendar for events matching a keyword within a date range. Returns the matching events.
- Get Event
Returns a single event from your Teamup calendar, including its custom field values, change history and reminders.
- Get Sub-Calendar
Returns a single sub-calendar from your Teamup calendar with all its details.
- List Events
Returns the events on your Teamup calendar for a date range, optionally limited to selected sub-calendars.
- List Sub-Calendars
Returns the sub-calendars on your Teamup calendar.
- Update Event
Updates an existing event on your Teamup calendar, including any custom event fields defined on the calendar. Returns the updated event.
- 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 Teamup Calendar
Teamup Calendar to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Teamup Calendar to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Teamup Calendar to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Teamup Calendar to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
Teamup Calendar to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Teamup Calendar to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
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
Teamup Calendar and Spike.sh, answered
What can start an automation from Teamup Calendar?
Any of Teamup Calendar's 6 triggers in the catalog, including New Event, New Event Matching Search, New or Updated Event and Event Ended. 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 Teamup Calendar?
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 Teamup Calendar?
Spike.sh has no triggers in the catalog today, so automations start in Teamup Calendar. 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 Teamup Calendar 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.