Integration
Connect Rootly to Convoso
When New Alert fires in Rootly, your agent runs Agent Monitor in Convoso. 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 Convoso 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 Convoso
When New Alert in Rootly
then Agent Monitor in Convoso
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 Convoso
Triggers and actions 3 triggers · 38 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.
- Agent Monitor
Returns the live state of Convoso agents (status, current call, call counts), optionally filtered by campaign, queue, agent or skill.
- Agent Monitor: Logout
Logs a Convoso agent out of the dialer.
- Callback: Delete
Deletes a scheduled Convoso callback.
- Callback: Insert
Schedules a callback for a Convoso lead, for the system or a specific agent.
- Callbacks
Returns Convoso callbacks filtered by date range, campaign, lead, list, agent, recipient or stage.
- Call Logs
Returns Convoso call log records filtered by lead, campaign, list, agent, phone number, call type or time range.
- Call Logs: Update
Writes values into the two extra fields of a Convoso call log record.
- Campaigns
Returns every campaign in the Convoso account with its ID, name, active status and last call date.
- Campaigns: Set Status
Activates or deactivates a Convoso campaign.
- DNC: Delete
Removes a phone number from a campaign's or the global Do Not Call list.
- DNC: Insert
Adds a phone number to a campaign's or the global Do Not Call list.
- DNC Records
Returns Do Not Call entries from a campaign or the global DNC list, filtered by phone number, campaign, date, reason or purpose.
- Lead: Delete
Deletes a lead from Convoso.
- Lead: Insert
Adds a lead to a Convoso list, optionally checking duplicates and DNC, queuing it in the hopper, or updating an existing match.
- Lead Recordings
Returns the call recordings for a Convoso lead, optionally within a date-time range.
- Leads
Returns Convoso leads matching the given filters, such as list, status, owner, phone number or last-updated date range.
- Lead: Update
Updates an existing Convoso lead's details, list or status.
- List: Delete
Deletes a Convoso lead list.
- List: Insert
Creates a new lead list in Convoso and assigns it to a campaign.
- Lists
Returns lead lists in the Convoso account, filtered by status and optionally by list or campaign.
- List: Update
Updates the name, campaign, description or status of a Convoso lead list.
- User Recordings
Returns call recordings made by the given Convoso users, optionally within a date-time range.
- Users
Returns Convoso user (agent) profiles for the given users.
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 Convoso
HubSpot to ConvosoHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to ConvosoGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ConvosoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ConvosoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Rootly and Convoso, 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 Convoso when something happens in Rootly?
Any of Convoso's 23 actions, including Agent Monitor, Agent Monitor: Logout, Callback: Insert and Callbacks. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Convoso to Rootly?
Convoso has no triggers in the catalog today, so automations start in Rootly. If you need the other direction, ask: your agent reads Convoso's API documentation and adds it.
Do I have to build a connector for Rootly or Convoso?
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 Convoso 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.