AptlyStar

Rootly

Manage incidents, alerts, and on-call with Rootly

Rootly is an incident management platform that helps teams respond to, mitigate, and learn from incidents — all without leaving Slack or your existing tools. Rootly automates on-call alerting, incident workflows, status page updates, and retrospectives so engineering teams can resolve issues faster and reduce toil.

Why Rootly?

  • End-to-End Incident Management: Create, track, update, and resolve incidents with full lifecycle support — from initial triage through retrospective.
  • On-Call Alerting: Create and manage alerts with deduplication, routing, and escalation to ensure the right people are notified immediately.
  • Timeline Events: Add structured timeline events to incidents for clear, auditable incident narratives.
  • Service Catalog: Maintain a catalog of services and map them to incidents for precise impact tracking.
  • Severity & Prioritization: Use configurable severity levels to prioritize incidents and drive appropriate response urgency.
  • Retrospectives: Access post-incident retrospectives to identify root causes, capture learnings, and drive reliability improvements.

Using Rootly in Aptlystar

Aptlystar's Rootly integration connects your agentic workflows directly to your Rootly account using an API key. With operations spanning incidents, alerts, services, severities, teams, environments, functionalities, incident types, and retrospectives, you can build powerful incident management automations without writing backend code.

Key benefits of using Rootly in Aptlystar:

  • Automated incident creation: Trigger incident creation from monitoring alerts, customer reports, or anomaly detection workflows with full metadata including severity, services, and teams.
  • Incident lifecycle automation: Automatically update incident status, add timeline events, and attach mitigation or resolution messages as your response progresses.
  • Alert management: Create and list alerts with deduplication support to integrate Rootly into your existing monitoring and notification pipelines.
  • Organizational awareness: Query services, severities, teams, environments, functionalities, and incident types to build context-aware incident workflows.
  • Retrospective insights: List and filter retrospectives to feed post-incident learnings into continuous improvement workflows.

Whether you're automating incident response, building on-call alerting pipelines, or driving post-incident learning, Rootly in Aptlystar gives you direct, secure access to the Rootly API — no middleware required. Simply configure your API key, select the operation you need, and let Aptlystar handle the rest.

Usage Instructions

Integrate Rootly incident management into workflows. Create and manage incidents, alerts, services, severities, and retrospectives.

Tools

rootly_create_incident

Create a new incident in Rootly with optional severity, services, and teams.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
titlestringNoThe title of the incident (auto-generated if not provided)
summarystringNoA summary of the incident
severityIdstringNoSeverity ID to attach to the incident
statusstringNoIncident status (in_triage, started, detected, acknowledged, mitigated, resolved, closed, cancelled, scheduled, in_progress, completed)
kindstringNoIncident kind (normal, normal_sub, test, test_sub, example, example_sub, backfilled, scheduled, scheduled_sub)
serviceIdsstringNoComma-separated service IDs to attach
environmentIdsstringNoComma-separated environment IDs to attach
groupIdsstringNoComma-separated team/group IDs to attach
incidentTypeIdsstringNoComma-separated incident type IDs to attach
functionalityIdsstringNoComma-separated functionality IDs to attach
labelsstringNoLabels as JSON object, e.g. {"platform":"osx","version":"1.29"}
privatebooleanNoCreate as a private incident (cannot be undone)

Output

ParameterTypeDescription
incidentobjectThe created incident
↳ idstringUnique incident ID
↳ sequentialIdnumberSequential incident number
↳ titlestringIncident title
↳ slugstringIncident slug
↳ kindstringIncident kind
↳ summarystringIncident summary
↳ statusstringIncident status
↳ privatebooleanWhether the incident is private
↳ urlstringURL to the incident
↳ shortUrlstringShort URL to the incident
↳ severityNamestringSeverity name
↳ severityIdstringSeverity ID
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ mitigatedAtstringMitigation date
↳ resolvedAtstringResolution date
↳ closedAtstringClosed date

rootly_get_incident

Retrieve a single incident by ID from Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident to retrieve

Output

ParameterTypeDescription
incidentobjectThe incident details
↳ idstringUnique incident ID
↳ sequentialIdnumberSequential incident number
↳ titlestringIncident title
↳ slugstringIncident slug
↳ kindstringIncident kind
↳ summarystringIncident summary
↳ statusstringIncident status
↳ privatebooleanWhether the incident is private
↳ urlstringURL to the incident
↳ shortUrlstringShort URL to the incident
↳ severityNamestringSeverity name
↳ severityIdstringSeverity ID
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ mitigatedAtstringMitigation date
↳ resolvedAtstringResolution date
↳ closedAtstringClosed date

rootly_update_incident

Update an existing incident in Rootly (status, severity, summary, etc.).

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident to update
titlestringNoUpdated incident title
summarystringNoUpdated incident summary
severityIdstringNoUpdated severity ID
statusstringNoUpdated status (in_triage, started, detected, acknowledged, mitigated, resolved, closed, cancelled, scheduled, in_progress, completed)
kindstringNoIncident kind (normal, normal_sub, test, test_sub, example, example_sub, backfilled, scheduled, scheduled_sub)
privatebooleanNoSet incident as private (cannot be undone)
serviceIdsstringNoComma-separated service IDs
environmentIdsstringNoComma-separated environment IDs
groupIdsstringNoComma-separated team/group IDs
incidentTypeIdsstringNoComma-separated incident type IDs to attach
functionalityIdsstringNoComma-separated functionality IDs to attach
labelsstringNoLabels as JSON object, e.g. {"platform":"osx","version":"1.29"}
mitigationMessagestringNoHow was the incident mitigated?
resolutionMessagestringNoHow was the incident resolved?
cancellationMessagestringNoWhy was the incident cancelled?

Output

ParameterTypeDescription
incidentobjectThe updated incident
↳ idstringUnique incident ID
↳ sequentialIdnumberSequential incident number
↳ titlestringIncident title
↳ slugstringIncident slug
↳ kindstringIncident kind
↳ summarystringIncident summary
↳ statusstringIncident status
↳ privatebooleanWhether the incident is private
↳ urlstringURL to the incident
↳ shortUrlstringShort URL to the incident
↳ severityNamestringSeverity name
↳ severityIdstringSeverity ID
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ mitigatedAtstringMitigation date
↳ resolvedAtstringResolution date
↳ closedAtstringClosed date

rootly_list_incidents

List incidents from Rootly with optional filtering by status, severity, and more.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
statusstringNoFilter by status (in_triage, started, detected, acknowledged, mitigated, resolved, closed, cancelled, scheduled, in_progress, completed)
severitystringNoFilter by severity slug
searchstringNoSearch term to filter incidents
servicesstringNoFilter by service slugs (comma-separated)
teamsstringNoFilter by team slugs (comma-separated)
environmentsstringNoFilter by environment slugs (comma-separated)
sortstringNoSort order (e.g., -created_at, created_at, -started_at)
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
incidentsarrayList of incidents
↳ idstringUnique incident ID
↳ sequentialIdnumberSequential incident number
↳ titlestringIncident title
↳ slugstringIncident slug
↳ kindstringIncident kind
↳ summarystringIncident summary
↳ statusstringIncident status
↳ privatebooleanWhether the incident is private
↳ urlstringURL to the incident
↳ shortUrlstringShort URL to the incident
↳ severityNamestringSeverity name
↳ severityIdstringSeverity ID
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ mitigatedAtstringMitigation date
↳ resolvedAtstringResolution date
↳ closedAtstringClosed date
totalCountnumberTotal number of incidents returned

rootly_create_alert

Create a new alert in Rootly for on-call notification and routing.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
summarystringYesThe summary of the alert
descriptionstringNoA detailed description of the alert
sourcestringYesThe source of the alert (e.g., api, manual, datadog, pagerduty)
statusstringNoAlert status on creation (open, triggered)
serviceIdsstringNoComma-separated service IDs to attach
groupIdsstringNoComma-separated team/group IDs to attach
environmentIdsstringNoComma-separated environment IDs to attach
externalIdstringNoExternal ID for the alert
externalUrlstringNoExternal URL for the alert
deduplicationKeystringNoAlerts sharing the same deduplication key are treated as a single alert

Output

ParameterTypeDescription
alertobjectThe created alert
↳ idstringUnique alert ID
↳ shortIdstringShort alert ID
↳ summarystringAlert summary
↳ descriptionstringAlert description
↳ sourcestringAlert source
↳ statusstringAlert status
↳ externalIdstringExternal ID
↳ externalUrlstringExternal URL
↳ deduplicationKeystringDeduplication key
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ endedAtstringEnd date

rootly_list_alerts

List alerts from Rootly with optional filtering by status, source, and services.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
statusstringNoFilter by status (open, triggered, acknowledged, resolved)
sourcestringNoFilter by source (e.g., api, datadog, pagerduty)
servicesstringNoFilter by service slugs (comma-separated)
environmentsstringNoFilter by environment slugs (comma-separated)
groupsstringNoFilter by team/group slugs (comma-separated)
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
alertsarrayList of alerts
↳ idstringUnique alert ID
↳ shortIdstringShort alert ID
↳ summarystringAlert summary
↳ descriptionstringAlert description
↳ sourcestringAlert source
↳ statusstringAlert status
↳ externalIdstringExternal ID
↳ externalUrlstringExternal URL
↳ deduplicationKeystringDeduplication key
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ endedAtstringEnd date
totalCountnumberTotal number of alerts returned

rootly_add_incident_event

Add a timeline event to an existing incident in Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident to add the event to
eventstringYesThe summary/description of the event
visibilitystringNoEvent visibility (internal or external)

Output

ParameterTypeDescription
eventIdstringThe ID of the created event
eventstringThe event summary
visibilitystringEvent visibility (internal or external)
occurredAtstringWhen the event occurred
createdAtstringCreation date
updatedAtstringLast update date

rootly_list_services

List services from Rootly with optional search filtering.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
searchstringNoSearch term to filter services
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
servicesarrayList of services
↳ idstringUnique service ID
↳ namestringService name
↳ slugstringService slug
↳ descriptionstringService description
↳ colorstringService color
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of services returned

rootly_list_severities

List severity levels configured in Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
searchstringNoSearch term to filter severities
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
severitiesarrayList of severity levels
↳ idstringUnique severity ID
↳ namestringSeverity name
↳ slugstringSeverity slug
↳ descriptionstringSeverity description
↳ severitystringSeverity level (critical, high, medium, low)
↳ colorstringSeverity color
↳ positionnumberDisplay position
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of severities returned

rootly_list_teams

List teams (groups) configured in Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
searchstringNoSearch term to filter teams
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
teamsarrayList of teams
↳ idstringUnique team ID
↳ namestringTeam name
↳ slugstringTeam slug
↳ descriptionstringTeam description
↳ colorstringTeam color
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of teams returned

rootly_list_environments

List environments configured in Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
searchstringNoSearch term to filter environments
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
environmentsarrayList of environments
↳ idstringUnique environment ID
↳ namestringEnvironment name
↳ slugstringEnvironment slug
↳ descriptionstringEnvironment description
↳ colorstringEnvironment color
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of environments returned

rootly_list_incident_types

List incident types configured in Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
searchstringNoFilter incident types by name
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
incidentTypesarrayList of incident types
↳ idstringUnique incident type ID
↳ namestringIncident type name
↳ slugstringIncident type slug
↳ descriptionstringIncident type description
↳ colorstringIncident type color
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of incident types returned

rootly_list_functionalities

List functionalities configured in Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
searchstringNoSearch term to filter functionalities
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
functionalitiesarrayList of functionalities
↳ idstringUnique functionality ID
↳ namestringFunctionality name
↳ slugstringFunctionality slug
↳ descriptionstringFunctionality description
↳ colorstringFunctionality color
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of functionalities returned

rootly_list_retrospectives

List incident retrospectives (post-mortems) from Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
statusstringNoFilter by status (draft, published)
searchstringNoSearch term to filter retrospectives
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
retrospectivesarrayList of retrospectives
↳ idstringUnique retrospective ID
↳ titlestringRetrospective title
↳ statusstringStatus (draft or published)
↳ urlstringURL to the retrospective
↳ startedAtstringIncident start date
↳ mitigatedAtstringMitigation date
↳ resolvedAtstringResolution date
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of retrospectives returned

rootly_delete_incident

Delete an incident by ID from Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident to delete

Output

ParameterTypeDescription
successbooleanWhether the deletion succeeded
messagestringResult message

rootly_get_alert

Retrieve a single alert by ID from Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
alertIdstringYesThe ID of the alert to retrieve

Output

ParameterTypeDescription
alertobjectThe alert details
↳ idstringUnique alert ID
↳ shortIdstringShort alert ID
↳ summarystringAlert summary
↳ descriptionstringAlert description
↳ sourcestringAlert source
↳ statusstringAlert status
↳ externalIdstringExternal ID
↳ externalUrlstringExternal URL
↳ deduplicationKeystringDeduplication key
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ endedAtstringEnd date

rootly_update_alert

Update an existing alert in Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
alertIdstringYesThe ID of the alert to update
summarystringNoUpdated alert summary
descriptionstringNoUpdated alert description
sourcestringNoUpdated alert source
serviceIdsstringNoComma-separated service IDs to attach
groupIdsstringNoComma-separated team/group IDs to attach
environmentIdsstringNoComma-separated environment IDs to attach
externalIdstringNoUpdated external ID
externalUrlstringNoUpdated external URL
deduplicationKeystringNoUpdated deduplication key

Output

ParameterTypeDescription
alertobjectThe updated alert
↳ idstringUnique alert ID
↳ shortIdstringShort alert ID
↳ summarystringAlert summary
↳ descriptionstringAlert description
↳ sourcestringAlert source
↳ statusstringAlert status
↳ externalIdstringExternal ID
↳ externalUrlstringExternal URL
↳ deduplicationKeystringDeduplication key
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ endedAtstringEnd date

rootly_acknowledge_alert

Acknowledge an alert in Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
alertIdstringYesThe ID of the alert to acknowledge

Output

ParameterTypeDescription
alertobjectThe acknowledged alert
↳ idstringUnique alert ID
↳ shortIdstringShort alert ID
↳ summarystringAlert summary
↳ descriptionstringAlert description
↳ sourcestringAlert source
↳ statusstringAlert status
↳ externalIdstringExternal ID
↳ externalUrlstringExternal URL
↳ deduplicationKeystringDeduplication key
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ endedAtstringEnd date

rootly_resolve_alert

Resolve an alert in Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
alertIdstringYesThe ID of the alert to resolve
resolutionMessagestringNoMessage describing how the alert was resolved
resolveRelatedIncidentsbooleanNoWhether to also resolve related incidents

Output

ParameterTypeDescription
alertobjectThe resolved alert
↳ idstringUnique alert ID
↳ shortIdstringShort alert ID
↳ summarystringAlert summary
↳ descriptionstringAlert description
↳ sourcestringAlert source
↳ statusstringAlert status
↳ externalIdstringExternal ID
↳ externalUrlstringExternal URL
↳ deduplicationKeystringDeduplication key
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ endedAtstringEnd date

rootly_create_action_item

Create a new action item for an incident in Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident to add the action item to
summarystringYesThe title of the action item
descriptionstringNoA detailed description of the action item
kindstringNoThe kind of action item (task, follow_up)
prioritystringNoPriority level (high, medium, low)
statusstringNoAction item status (open, in_progress, cancelled, done)
assignedToUserIdstringNoThe user ID to assign the action item to
dueDatestringNoDue date for the action item

Output

ParameterTypeDescription
actionItemobjectThe created action item
↳ idstringUnique action item ID
↳ summarystringAction item title
↳ descriptionstringAction item description
↳ kindstringAction item kind (task, follow_up)
↳ prioritystringPriority level
↳ statusstringAction item status
↳ dueDatestringDue date
↳ createdAtstringCreation date
↳ updatedAtstringLast update date

rootly_list_action_items

List action items for an incident in Rootly.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident to list action items for
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
actionItemsarrayList of action items
↳ idstringUnique action item ID
↳ summarystringAction item title
↳ descriptionstringAction item description
↳ kindstringAction item kind (task, follow_up)
↳ prioritystringPriority level
↳ statusstringAction item status
↳ dueDatestringDue date
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of action items returned

rootly_list_users

List users from Rootly with optional search and email filtering.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
searchstringNoSearch term to filter users
emailstringNoFilter users by email address
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
usersarrayList of users
↳ idstringUnique user ID
↳ emailstringUser email address
↳ firstNamestringUser first name
↳ lastNamestringUser last name
↳ fullNamestringUser full name
↳ timeZonestringUser time zone
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of users returned

rootly_list_on_calls

List current on-call entries from Rootly with optional filtering.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
scheduleIdsstringNoComma-separated schedule IDs to filter by
escalationPolicyIdsstringNoComma-separated escalation policy IDs to filter by
userIdsstringNoComma-separated user IDs to filter by
serviceIdsstringNoComma-separated service IDs to filter by

Output

ParameterTypeDescription
onCallsarrayList of on-call entries
↳ idstringUnique on-call entry ID
↳ userIdstringID of the on-call user
↳ userNamestringName of the on-call user
↳ scheduleIdstringID of the associated schedule
↳ scheduleNamestringName of the associated schedule
↳ escalationPolicyIdstringID of the associated escalation policy
↳ startTimestringOn-call start time
↳ endTimestringOn-call end time
totalCountnumberTotal number of on-call entries returned

rootly_list_schedules

List on-call schedules from Rootly with optional search filtering.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
searchstringNoSearch term to filter schedules
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
schedulesarrayList of schedules
↳ idstringUnique schedule ID
↳ namestringSchedule name
↳ descriptionstringSchedule description
↳ allTimeCoveragebooleanWhether schedule provides 24/7 coverage
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of schedules returned

rootly_list_escalation_policies

List escalation policies from Rootly with optional search filtering.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
searchstringNoSearch term to filter escalation policies
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
escalationPoliciesarrayList of escalation policies
↳ idstringUnique escalation policy ID
↳ namestringEscalation policy name
↳ descriptionstringEscalation policy description
↳ repeatCountnumberNumber of times to repeat escalation
↳ groupIdsarrayAssociated group IDs
↳ serviceIdsarrayAssociated service IDs
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of escalation policies returned

rootly_list_causes

List causes from Rootly with optional search filtering.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
searchstringNoSearch term to filter causes
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
causesarrayList of causes
↳ idstringUnique cause ID
↳ namestringCause name
↳ slugstringCause slug
↳ descriptionstringCause description
↳ positionnumberCause position
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of causes returned

rootly_list_playbooks

List playbooks from Rootly with pagination support.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
playbooksarrayList of playbooks
↳ idstringUnique playbook ID
↳ titlestringPlaybook title
↳ summarystringPlaybook summary
↳ externalUrlstringExternal URL
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of playbooks returned

rootly_mitigate_incident

Transition a Rootly incident to the mitigated state.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident to mitigate
mitigationMessagestringNoHow was the incident mitigated?

Output

ParameterTypeDescription
incidentobjectThe mitigated incident
↳ idstringUnique incident ID
↳ sequentialIdnumberSequential incident number
↳ titlestringIncident title
↳ slugstringIncident slug
↳ kindstringIncident kind
↳ summarystringIncident summary
↳ statusstringIncident status
↳ privatebooleanWhether the incident is private
↳ urlstringURL to the incident
↳ shortUrlstringShort URL to the incident
↳ severityNamestringSeverity name
↳ severityIdstringSeverity ID
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ mitigatedAtstringMitigation date
↳ resolvedAtstringResolution date
↳ closedAtstringClosed date

rootly_resolve_incident

Transition a Rootly incident to the resolved state.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident to resolve
resolutionMessagestringNoHow was the incident resolved?

Output

ParameterTypeDescription
incidentobjectThe resolved incident
↳ idstringUnique incident ID
↳ sequentialIdnumberSequential incident number
↳ titlestringIncident title
↳ slugstringIncident slug
↳ kindstringIncident kind
↳ summarystringIncident summary
↳ statusstringIncident status
↳ privatebooleanWhether the incident is private
↳ urlstringURL to the incident
↳ shortUrlstringShort URL to the incident
↳ severityNamestringSeverity name
↳ severityIdstringSeverity ID
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ mitigatedAtstringMitigation date
↳ resolvedAtstringResolution date
↳ closedAtstringClosed date

rootly_assign_incident_role

Assign an incident role (e.g. commander) to a user on a Rootly incident.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident
userIdstringYesThe ID of the user to assign (use List Users to find IDs)
incidentRoleIdstringYesThe ID of the incident role (use List Incident Roles to find IDs)

Output

ParameterTypeDescription
incidentobjectThe incident after the role assignment
↳ idstringUnique incident ID
↳ sequentialIdnumberSequential incident number
↳ titlestringIncident title
↳ slugstringIncident slug
↳ kindstringIncident kind
↳ summarystringIncident summary
↳ statusstringIncident status
↳ privatebooleanWhether the incident is private
↳ urlstringURL to the incident
↳ shortUrlstringShort URL to the incident
↳ severityNamestringSeverity name
↳ severityIdstringSeverity ID
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ mitigatedAtstringMitigation date
↳ resolvedAtstringResolution date
↳ closedAtstringClosed date

rootly_unassign_incident_role

Remove an incident role assignment from a user on a Rootly incident.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident
userIdstringYesThe ID of the user to unassign (use List Users to find IDs)
incidentRoleIdstringYesThe ID of the incident role to remove (use List Incident Roles to find IDs)

Output

ParameterTypeDescription
incidentobjectThe incident after the role was unassigned
↳ idstringUnique incident ID
↳ sequentialIdnumberSequential incident number
↳ titlestringIncident title
↳ slugstringIncident slug
↳ kindstringIncident kind
↳ summarystringIncident summary
↳ statusstringIncident status
↳ privatebooleanWhether the incident is private
↳ urlstringURL to the incident
↳ shortUrlstringShort URL to the incident
↳ severityNamestringSeverity name
↳ severityIdstringSeverity ID
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ mitigatedAtstringMitigation date
↳ resolvedAtstringResolution date
↳ closedAtstringClosed date

rootly_add_subscribers

Subscribe users to a Rootly incident so they receive updates.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident
userIdsstringYesComma-separated user IDs to subscribe (use List Users to find IDs)

Output

ParameterTypeDescription
incidentobjectThe incident after subscribers were added
↳ idstringUnique incident ID
↳ sequentialIdnumberSequential incident number
↳ titlestringIncident title
↳ slugstringIncident slug
↳ kindstringIncident kind
↳ summarystringIncident summary
↳ statusstringIncident status
↳ privatebooleanWhether the incident is private
↳ urlstringURL to the incident
↳ shortUrlstringShort URL to the incident
↳ severityNamestringSeverity name
↳ severityIdstringSeverity ID
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ mitigatedAtstringMitigation date
↳ resolvedAtstringResolution date
↳ closedAtstringClosed date

rootly_remove_subscribers

Unsubscribe users from a Rootly incident.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident
userIdsstringYesComma-separated user IDs to unsubscribe (use List Users to find IDs)

Output

ParameterTypeDescription
incidentobjectThe incident after subscribers were removed
↳ idstringUnique incident ID
↳ sequentialIdnumberSequential incident number
↳ titlestringIncident title
↳ slugstringIncident slug
↳ kindstringIncident kind
↳ summarystringIncident summary
↳ statusstringIncident status
↳ privatebooleanWhether the incident is private
↳ urlstringURL to the incident
↳ shortUrlstringShort URL to the incident
↳ severityNamestringSeverity name
↳ severityIdstringSeverity ID
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ mitigatedAtstringMitigation date
↳ resolvedAtstringResolution date
↳ closedAtstringClosed date

rootly_create_status_page_event

Post a public status page update for a Rootly incident.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident
eventstringYesThe status page update message to publish
statusPageIdstringNoThe ID of the status page to post to
statusstringNoStatus to set (investigating, identified, monitoring, resolved, scheduled, in_progress, completed)
notifySubscribersbooleanNoWhether to notify status page subscribers
shouldTweetbooleanNoWhether to post the update to the linked Twitter/X account

Output

ParameterTypeDescription
statusPageEventobjectThe created status page event
↳ idstringUnique status page event ID
↳ eventstringThe published update message
↳ statusPageIdstringStatus page ID
↳ statusstringStatus that was set
↳ notifySubscribersbooleanWhether subscribers were notified
↳ shouldTweetbooleanWhether the update was tweeted
↳ startedAtstringWhen the event started
↳ createdAtstringCreation date
↳ updatedAtstringLast update date

rootly_update_action_item

Update a Rootly incident action item (status, priority, assignee, etc.).

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
actionItemIdstringYesThe ID of the action item to update
summarystringNoUpdated action item title
descriptionstringNoUpdated description
kindstringNoThe kind of action item (task, follow_up)
prioritystringNoPriority level (high, medium, low)
statusstringNoAction item status (open, in_progress, cancelled, done)
assignedToUserIdstringNoThe user ID to assign the action item to
dueDatestringNoDue date for the action item

Output

ParameterTypeDescription
actionItemobjectThe updated action item
↳ idstringUnique action item ID
↳ summarystringAction item title
↳ descriptionstringAction item description
↳ kindstringAction item kind (task, follow_up)
↳ prioritystringPriority level
↳ statusstringAction item status
↳ dueDatestringDue date
↳ createdAtstringCreation date
↳ updatedAtstringLast update date

rootly_delete_action_item

Delete a Rootly incident action item.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
actionItemIdstringYesThe ID of the action item to delete

Output

ParameterTypeDescription
successbooleanWhether the action item was deleted
messagestringResult message

rootly_snooze_alert

Snooze a Rootly alert for a set number of minutes.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
alertIdstringYesThe ID of the alert to snooze
delayMinutesnumberYesNumber of minutes to snooze the alert

Output

ParameterTypeDescription
alertobjectThe snoozed alert
↳ idstringUnique alert ID
↳ shortIdstringShort alert ID
↳ summarystringAlert summary
↳ descriptionstringAlert description
↳ sourcestringAlert source
↳ statusstringAlert status
↳ externalIdstringExternal ID
↳ externalUrlstringExternal URL
↳ deduplicationKeystringDeduplication key
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ endedAtstringEnd date

rootly_escalate_alert

Escalate a Rootly alert, optionally to a specific escalation policy or level.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
alertIdstringYesThe ID of the alert to escalate
escalationPolicyIdstringNoEscalation policy ID to escalate to (use List Escalation Policies to find IDs)
escalationPolicyLevelnumberNoEscalation policy level to escalate to

Output

ParameterTypeDescription
alertobjectThe escalated alert
↳ idstringUnique alert ID
↳ shortIdstringShort alert ID
↳ summarystringAlert summary
↳ descriptionstringAlert description
↳ sourcestringAlert source
↳ statusstringAlert status
↳ externalIdstringExternal ID
↳ externalUrlstringExternal URL
↳ deduplicationKeystringDeduplication key
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
↳ startedAtstringStart date
↳ endedAtstringEnd date

rootly_list_incident_events

List the timeline events for a Rootly incident.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
incidentIdstringYesThe ID of the incident
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
eventsarrayList of incident timeline events
↳ idstringUnique event ID
↳ eventstringThe event description
↳ visibilitystringEvent visibility (internal or external)
↳ occurredAtstringWhen the event occurred
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of events returned

rootly_run_workflow

Trigger a Rootly automation workflow, optionally scoped to an incident or alert.

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
workflowIdstringYesThe ID of the workflow to run
incidentIdstringNoIncident ID to run the workflow against
alertIdstringNoAlert ID to run the workflow against
immediatebooleanNoRun immediately (true) or respect the workflow wait time (false). Default true
checkConditionsbooleanNoWhether to evaluate the workflow conditions before running. Default false

Output

ParameterTypeDescription
workflowRunobjectThe triggered workflow run
↳ idstringUnique workflow run ID
↳ workflowIdstringID of the workflow that ran
↳ statusstringRun status (queued, started, completed, completed_with_errors, failed, canceled)
↳ statusMessagestringStatus detail message
↳ triggeredBystringWhat triggered the run (system, user, workflow)
↳ incidentIdstringAssociated incident ID
↳ alertIdstringAssociated alert ID
↳ startedAtstringWhen the run started
↳ completedAtstringWhen the run completed
↳ failedAtstringWhen the run failed
↳ canceledAtstringWhen the run was canceled

rootly_list_incident_roles

List incident roles configured in Rootly (e.g. commander, scribe).

Input

ParameterTypeRequiredDescription
apiKeystringYesRootly API key
searchstringNoSearch term to filter incident roles
pageSizenumberNoNumber of items per page (default: 20)
pageNumbernumberNoPage number for pagination

Output

ParameterTypeDescription
incidentRolesarrayList of incident roles
↳ idstringUnique incident role ID
↳ namestringRole name
↳ slugstringRole slug
↳ summarystringRole summary
↳ descriptionstringRole description
↳ positionnumberDisplay position
↳ optionalbooleanWhether the role is optional
↳ enabledbooleanWhether the role is enabled
↳ createdAtstringCreation date
↳ updatedAtstringLast update date
totalCountnumberTotal number of incident roles returned

On this page