--- title: "Connect incident.io and Teamup Calendar - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add Comment\" in Teamup Calendar." canonical: "https://apiant.ai/connect/incident-io-to-teamup-calendar" --- # Connect incident.io and Teamup Calendar When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add Comment** in [Teamup Calendar](https://apiant.ai/connections/teamup-calendar), or **New Event** in Teamup Calendar to **Find Users On-Call** in incident.io. Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **11** actions Teamup Calendar **6** triggers Teamup Calendar **11** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want incident.io and Teamup Calendar 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 incident.io and Teamup Calendar can do together ### From incident.io to Teamup Calendar - When **New Incident** in incident.io then **Add Comment** in Teamup Calendar - When **New Incident** in incident.io then **Create Event** in Teamup Calendar ### From Teamup Calendar to incident.io - When **New Event** in Teamup Calendar then **Find Users On-Call** in incident.io - When **New Event Matching Search** in Teamup Calendar then **Add follow-up** in incident.io 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 incident.io and Teamup Calendar ## Triggers and actions 7 triggers · 22 actions - Trigger **New Incident** Triggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode. - Action **Add follow-up** Creates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels. - Action **Add incident update** Shares an update on an incident: a message, a move to a new status, a new severity, or any combination. - Action **Create Incident** Creates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields. - Action **Find Users On-Call** Finds the users on-call for a schedule over a window of time (or right now), returning each effective shift with its user after overrides are applied. - Action **Get incident** Returns a single incident, including its status, severity, role assignments, timestamps and custom field values. - Action **Get Schedule** Returns a single on-call schedule, including its rotations, time zone and current shifts. - Action **List actions** Returns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date. - Action **List schedules** Returns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift. - Action **List severities** Returns every incident severity configured for your incident.io organisation. - Action **List users** Returns the users in your incident.io account, optionally filtered by email address or Slack user ID. - Action **Update incident** Edits an existing incident's name, summary, severity, status, call link, Slack channel name, custom fields, role assignments or timestamps. Only the values you provide are changed. - Trigger **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. - Trigger **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. - Trigger **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. - Trigger **New Event** Triggers when a new event is added to your Teamup calendar. - Trigger **New Event Matching Search** Triggers when a new event matching your search keywords appears on your Teamup calendar. - Trigger **New or Updated Event** Triggers when an event is added or changed on your Teamup calendar. - Action **Add Comment** Posts a comment on an event in your Teamup calendar. Returns the created comment, including its id and creation time. - Action **Add Signup** Signs a person up for an event on your Teamup calendar. Returns the created signup, including its id and creation time. - Action **Create Event** Creates a new event on your Teamup calendar, including any custom event fields defined on the calendar. Returns the created event. - Action **Delete Event** Deletes an event from your Teamup calendar. Returns an undo token for the deletion. - Action **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. - Action **Find Events** Searches your Teamup calendar for events matching a keyword within a date range. Returns the matching events. - Action **Get Event** Returns a single event from your Teamup calendar, including its custom field values, change history and reminders. - Action **Get Sub-Calendar** Returns a single sub-calendar from your Teamup calendar with all its details. - Action **List Events** Returns the events on your Teamup calendar for a date range, optionally limited to selected sub-calendars. - Action **List Sub-Calendars** Returns the sub-calendars on your Teamup calendar. - Action **Update Event** Updates an existing event on your Teamup calendar, including any custom event fields defined on the calendar. Returns the updated event. ## Each app on its own - [ **incident.io** incident.io is an incident management platform, designed for your entire organisation.](https://apiant.ai/connections/incident-io) - [ **Teamup Calendar** Teamup is a calendar tool for groups and businesses.](https://apiant.ai/connections/teamup-calendar) Reviews ## What our customers say ## More from incident.io - [ **incident.io to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/incident-io-to-salesforce) - [ **incident.io to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/incident-io-to-slack) - [ **incident.io to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/incident-io-to-mailchimp) - [ **incident.io to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/incident-io-to-stripe) - [ **incident.io to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/incident-io-to-shopify) - [ **incident.io to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/incident-io-to-quickbooks-online) ## More into Teamup Calendar - [ **DonorPerfect to Teamup Calendar** DonorPerfect Online (DPO) is fundraising and donor-management software for nonprofits.](https://apiant.ai/connect/donorperfect-to-teamup-calendar) - [ **HubSpot to Teamup Calendar** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-teamup-calendar) - [ **Salesforce to Teamup Calendar** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-teamup-calendar) - [ **Slack to Teamup Calendar** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-teamup-calendar) - [ **Google Sheets to Teamup Calendar** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-teamup-calendar) - [ **Gmail to Teamup Calendar** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-teamup-calendar) Questions ## incident.io and Teamup Calendar, answered ### ### What can start an automation from incident.io? Any of incident.io's 1 trigger in the catalog, including New Incident. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Teamup Calendar when something happens in incident.io? Any of Teamup Calendar's 11 actions, including Create Event, Update Event, Add Comment and Add Signup. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Teamup Calendar to incident.io? Yes. When something happens in Teamup Calendar, your agent can act in incident.io too. This page covers both directions: Teamup Calendar's triggers and incident.io's actions are listed here as well. ### ### Do I have to build a connector for incident.io or Teamup Calendar? 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 incident.io and Teamup Calendar 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.