Integration
Connect Rootly to Belong
When New Alert fires in Rootly, your agent runs Add ticket tier in Belong. Describe the whole flow 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 Rootly and Belong to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Rootly can start in Belong
When New Alert in Rootly
then Add 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 Rootly and Belong
Triggers and actions 3 triggers · 35 actions
- New Alert
Triggers when a new alert is created in Rootly.
- New Incident
Triggers when a new incident is created in Rootly.
- New Pulse
Triggers when a new pulse, such as a deploy or config change, is recorded in Rootly.
- Add action item
Adds an action item (task or follow-up) to a Rootly incident.
- Add service
Creates a new service in Rootly's service catalog.
- Create Alert
Creates a new alert in Rootly and returns its ID and status.
- Create Incident
Creates a new incident in Rootly and returns its ID, status and link.
- Create Pulse
Records a pulse in Rootly, such as a deploy or configuration change, and returns its ID.
- Get Alert
Returns one Rootly alert by its ID.
- Get Incident
Returns one Rootly incident by its ID.
- Get Pulse
Returns one Rootly pulse by its ID.
- List alerts
Returns alerts in your Rootly organization, optionally filtered by status, source, service, team, environment, label or time range.
- List incidents
Returns incidents in your Rootly organization, optionally filtered by status, severity, services, teams, dates and more.
- List pulses
Returns the pulses (deploys and other change events) recorded in Rootly, optionally filtered by source, service, environment, label, ref or time range.
- List services
Returns the services in your Rootly organization, optionally filtered by name, slug, external ids or creation date.
- List teams
Returns the teams in your Rootly organization, optionally filtered by name, slug, color, external ids or creation date.
- List users
Returns the users in your Rootly organization, optionally filtered by search text, email, role or creation date.
- Update incident
Updates an existing Rootly incident's title, status, severity, teams, services, timestamps and other details.
- Add hub
Creates a new hub (community group or NFT collection hub) owned by the connected user.
- Add note
Creates a note in a Belong hub with a title, description and content.
- Add ticket tier
Creates a priced ticket tier on a Belong event.
- Create Event
Creates a new event in Belong with its name, schedule, place and visibility settings, and returns the created event.
- Delete event
Deletes an event (activity) in Belong.
- Delete hub
Deletes a hub in Belong by its id or slug.
- Delete note
Deletes a note in Belong by its ID or slug.
- Delete ticket tier
Deletes a ticket tier from an event. Only tiers with no sold tickets and no attached NFT collection can be deleted.
- 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.
- Get event
Returns a single Belong event by its id or slug, including its schedule, place, and settings.
- Get hub
Returns a Belong hub by its id or public slug.
- Get note
Returns a single Belong note by its ID or slug, including its title, description, content and hub.
- Get user profile
Returns the profile of the Belong user whose account is connected: name, email, phone, username and biography.
- List events
Returns a list of Belong events, optionally filtered by hub, owner, category, dates or search text.
- List hubs
Returns a list of Belong hubs, optionally filtered by type, status, owner, member or search text.
- List ticket tiers
Returns an event's ticket tiers with inventory, pricing and the payment methods each tier can be bought with.
- 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.
- Update hub
Updates an existing Belong hub's details, and can optionally connect existing events to it.
- Update note
Updates the title, description or content of an existing Belong note.
- Update ticket tier
Updates a ticket tier on an event: its name, description, card price, currency or capacity.
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 Rootly
Rootly to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Rootly to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Rootly to StripeStripe is a payment processing platform for online businesses.
Rootly to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Rootly to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Rootly to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into Belong
HubSpot to BelongHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to BelongGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to BelongGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to BelongGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Rootly and Belong, answered
What can start an automation from Rootly?
Any of Rootly's 3 triggers in the catalog, including New Alert, New Incident and New Pulse. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Belong when something happens in Rootly?
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 Rootly?
Belong has no triggers in the catalog today, so automations start in Rootly. 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 Rootly 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 Rootly 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.