Rootly Tools

Rootly is an incident-management platform. These tools let a workflow list existing incidents, create new ones, and fetch a single incident by ID through the Rootly v1 REST API. Use them to automate incident creation from alerts or to pull incident data into downstream steps.

Overview

Operations

Configuration

rootly_list_incidents

rootly_create_incident

rootly_get_incident

Outputs

rootly_list_incidents

• data (json) — Array of incident objects.
• metadata (json) — List metadata, with properties:
  • count (number) — Number of incidents returned.
  • total (number) — Total number of incidents available (from the API meta.total_count).

rootly_create_incident

• data (json) — The created incident object.
• metadata (json) — Incident identifiers, with properties:
  • id (string) — Incident ID.
  • type (string) — Resource type.

rootly_get_incident

• data (json) — The incident object.
• metadata (json) — Incident identifiers, with properties:
  • id (string) — Incident ID.
  • type (string) — Resource type.

YAML Example

rootly_1:
  type: rootly
  name: "Rootly"
  inputs:
    operation: "rootly_create_incident"
    title: "API latency spike"
    summary: "Elevated p99 latency on the checkout API"
    apiKey: "{{ROOTLY_API_KEY}}"
  connections:
    outgoing:
      - target: next-block-id

Tips

• Auth setup: Generate an API key in your Rootly account settings and store it as an environment variable (e.g. ROOTLY_API_KEY). The key is sent as Authorization: Bearer <apiKey> against https://api.rootly.com/v1/incidents; it is user-only, so the LLM never sees it.
• Chaining incidents: After rootly_create_incident, reference the new incident's ID downstream with {{rootly_1.metadata.id}}, or pass the full object with {{rootly_1.data}} to an Agent or notification block.
• Pagination: rootly_list_incidents only exposes pageSize (mapped to page[size]). Check {{rootly_1.metadata.total}} to see how many incidents exist versus how many were returned in {{rootly_1.metadata.count}}.