--- title: "Connect incident.io to Belong - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add ticket tier\" in Belong." canonical: "https://apiant.ai/connect/incident-io-to-belong" --- # Connect incident.io to Belong When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add ticket tier** in [Belong](https://apiant.ai/connections/belong). Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Belong **20** 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 Belong 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 can start in Belong - When **New Incident** in incident.io then **Add ticket tier** in Belong - When **New Incident** in incident.io then **Update ticket tier** in Belong 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 Belong ## Triggers and actions 1 trigger · 30 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 **Add hub** Creates a new hub (community group or NFT collection hub) owned by the connected user. - Action **Add note** Creates a note in a Belong hub with a title, description and content. - Action **Add ticket tier** Creates a priced ticket tier on a Belong event. - Action **Create Event** Creates a new event in Belong with its name, schedule, place and visibility settings, and returns the created event. - Action **Delete event** Deletes an event (activity) in Belong. - Action **Delete hub** Deletes a hub in Belong by its id or slug. - Action **Delete note** Deletes a note in Belong by its ID or slug. - Action **Delete ticket tier** Deletes a ticket tier from an event. Only tiers with no sold tickets and no attached NFT collection can be deleted. - Action **Find events nearby** Finds Belong events within the default radius of a latitude/longitude, optionally filtered by hub, owner, category, dates or a search term. - Action **Get event** Returns a single Belong event by its id or slug, including its schedule, place, and settings. - Action **Get hub** Returns a Belong hub by its id or public slug. - Action **Get note** Returns a single Belong note by its ID or slug, including its title, description, content and hub. - Action **Get user profile** Returns the profile of the Belong user whose account is connected: name, email, phone, username and biography. - Action **List events** Returns a list of Belong events, optionally filtered by hub, owner, category, dates or search text. - Action **List hubs** Returns a list of Belong hubs, optionally filtered by type, status, owner, member or search text. - Action **List ticket tiers** Returns an event's ticket tiers with inventory, pricing and the payment methods each tier can be bought with. - Action **Update event** Updates an existing Belong event's details such as name, description, dates, place, visibility and status. Only the fields you fill in are changed. - Action **Update hub** Updates an existing Belong hub's details, and can optionally connect existing events to it. - Action **Update note** Updates the title, description or content of an existing Belong note. - Action **Update ticket tier** Updates a ticket tier on an event: its name, description, card price, currency or capacity. ## 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) - [ **Belong** Belong is a secure and audited Web2-friendly token-gating solution for communities, events, and content feeds.](https://apiant.ai/connections/belong) 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 Belong - [ **HubSpot to Belong** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-belong) - [ **Salesforce to Belong** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-belong) - [ **Slack to Belong** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-belong) - [ **Google Sheets to Belong** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-belong) - [ **Gmail to Belong** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-belong) - [ **Google Calendar to Belong** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-belong) Questions ## incident.io and Belong, 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 Belong when something happens in incident.io? Any of Belong's 20 actions, including Create Event, Update event, Update hub and Update note. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Belong to incident.io? Belong has no triggers in the catalog today, so automations start in incident.io. If you need the other direction, ask: your agent reads Belong's API documentation and adds it. ### ### Do I have to build a connector for incident.io or Belong? 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 Belong 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.