Connect Claude & ChatGPT to Rootly

27 tools for Rootly

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

• acknowledge_alertChanges dataAcknowledge an alert by `alert_id`, which stops further escalation to other responders.
• add_incident_subscribersChanges dataSubscribe users to an incident's updates by `incident_id`. Pass `data` = {type: "incidents", attributes: {user_ids: [...]}}. Subscribers are notified of changes.
• add_incident_timeline_eventChanges dataAdd a note to an incident's timeline by `incident_id`. Pass `data` = {type: "incident_events", attributes: {event: "<text>"}}.
• create_action_itemChanges dataAdd an action item to an incident by `incident_id`. Pass `data` = {type: "incident_action_items", attributes: {summary, description, due_date, assigned_to_user_id}}.
• create_incidentChanges dataDeclare a new incident. Pass JSON:API `data` = {type: "incidents", attributes: {title, summary, severity_id, service_ids, group_ids (teams), environment_ids, incident_type_ids, labels}}. This can page responders and post to Slack, depending on the organization's workflows.
• get_alertGet one alert by `alert_id`, with source, status, summary and linked services.
• get_current_userGet the Rootly user this connection acts as. Use to confirm which organization and user you are working as.
• get_incidentGet one incident by ID (passed as `page_id`), with title, summary, status, severity, services, teams and timestamps.
• list_action_itemsList action items across all incidents, filtered by status, kind, priority or due date. Paginate with `page` and `limit`.
• list_alertsList alerts, filtered by `filter_status`, `filter_source`, `filter_services`, `filter_groups` (teams) or `filter_environments`. Paginate with `page` and `limit`.
• list_environmentsList environments (such as production or staging) with their IDs.
• list_incident_action_itemsList the action items (follow-up tasks) on one incident by `incident_id`.
• list_incident_timelineList the timeline events (updates and notes) of an incident by `incident_id`.
• list_incident_typesList incident types with their IDs.
• list_incidentsList incidents, newest first with `sort`=-created_at, filtered by `filter_search` text, `filter_status`, `filter_severity`, `filter_services`, `filter_teams`, `filter_environments` and more. Paginate with `page` and `limit`.
• list_on_callSee who is on call, optionally between `since` and `until`, filtered by user, team, service, schedule or escalation policy IDs.
• list_schedule_shiftsList the shifts on one on-call schedule by `schedule_id` between `from` and `to` dates.
• list_schedulesList on-call schedules, filtered by name or team. Use to find a schedule ID.
• list_servicesList services in the catalog, filtered by name or `filter_search`. Their IDs are used on incidents and alerts.
• list_severitiesList the incident severity levels with their IDs, needed as severity_id when creating or updating incidents.
• list_teamsList teams, filtered by name or `filter_search`. Their IDs are used as group_ids on incidents.
• list_usersList users in the organization, filtered by `filter_search` text or exact `filter_email`. Use to find user IDs for assigning action items or subscribing people.
• mitigate_incidentVisible to othersMark an incident as mitigated by `incident_id`. Pass `data` = {type: "incidents", attributes: {mitigation_message}} explaining how it was mitigated.
• resolve_alertChanges dataResolve an alert by `alert_id`. Optionally pass `data` = {type: "alerts", attributes: {resolution_message, resolve_related_incidents}}; setting resolve_related_incidents also resolves the incidents linked to it.
• resolve_incidentVisible to othersMark an incident as resolved by `incident_id`. Pass `data` = {type: "incidents", attributes: {resolution_message}} explaining how it was resolved.
• update_action_itemChanges dataUpdate an action item by ID (passed as `product_id`). Pass `data` = {type: "incident_action_items", attributes: {...}} with the fields to change, such as summary, description, due_date or assigned_to_user_id.
• update_incidentChanges dataUpdate an incident by ID (passed as `page_id`). Pass `data` = {type: "incidents", attributes: {...}} with the fields to change, such as title, summary, severity_id, service_ids or group_ids. Use mitigate_incident or resolve_incident to change its status.

Questions