Rootly is an AI-native incident management platform that automates workflows and collaboration, integrating with Slack, PagerDuty, and other tools to streamline incident response.
Rootly is an AI-native incident management platform that automates workflows and collaboration, integrating with Slack, PagerDuty, and other tools to streamline incident response. On Nagent, Rootly is exposed as a fully-configurable it operations integration that any agent can call — 6 actions, and API key authentication. No code is required to wire Rootly into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Rootly to automate the kinds of tasks it operations teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Rootly into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Rootly, with input parameters and output schema. Drop these into any step of an agent built in Helix.
ROOTLY_DELETE_ACTION_ITEMThis tool allows for the deletion of a specific action item in Rootly. It complements the existing ROOTLY_LIST_ACTION_ITEMS functionality by providing the ability to remove individual action items from the system.
Input parameters
The unique identifier (UUID) of the action item to delete. Use ROOTLY_LIST_ACTION_ITEMS to find action item IDs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ROOTLY_DELETE_INCIDENTTool to delete an incident in Rootly by ID. Use when performing administrative cleanup. This is a destructive operation and depends on appropriate Rootly permissions.
Input parameters
The unique identifier of the incident to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ROOTLY_GET_ACTION_ITEMRetrieves detailed information about a specific action item by its ID from Rootly. Action items are tasks or follow-up items created during incident management to track work that needs to be completed. This tool returns comprehensive details including: - Core info: summary, description, kind (task/follow_up), priority, status, due_date - Assignment: assigned user and group IDs - Integration links: Jira, GitHub, GitLab, Linear, Asana, Trello, ClickUp, and other connected tools - Metadata: creation and update timestamps, direct URL to the action item Use ROOTLY_LIST_ACTION_ITEMS first to discover available action item IDs if you don't already have one.
Input parameters
The unique identifier of the action item to retrieve. Use ROOTLY_LIST_ACTION_ITEMS to discover available action item IDs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ROOTLY_GET_INCIDENTTool to retrieve full details for a single Rootly incident by ID. Use when you need complete incident information for drill-down after listing or searching incidents. Supports optional include parameter to fetch related resources like environments, services, action_items, and events in a single request.
Input parameters
The ID of the incident to retrieve (UUID or slug format)
Comma-separated list of related resources to include in response. Available options: sub_statuses, causes, subscribers, roles, slack_messages, environments, incident_types, services, functionalities, groups, events, action_items, custom_field_selections, feedbacks, incident_post_mortem, alerts
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ROOTLY_LIST_ACTION_ITEMSThis tool retrieves a list of all action items for an organization in Rootly. Action items are tasks or follow-up items that need to be completed during or after an incident, helping to track and manage incident-related tasks effectively.
Input parameters
Kind of action item in Rootly.
Status of action items.
Priority levels for action items.
Number of items per page
Page number for pagination
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ROOTLY_UPDATE_INCIDENTTool to update fields on an existing Rootly incident by ID. Use when you need to modify incident status, severity, metadata, or other attributes. Supports updating title, status, summary, severity_id, service_ids, environment_ids, and more.
Input parameters
The ID of the incident to update (UUID or slug format)
Data object containing the incident type and attributes to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 85 agents privately built on Nagent that already use Rootly.
Build on Nagent
Connect Rootly to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Rootly, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Rootly is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Rootly is connected, you configure its 6 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Rootly steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Rootly event fires, the agent kicks off automatically.
Every Rootly action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Rootly ships with 6 pre-built it operations actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Rootly together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Rootly-based workflows tailored to your business.