> ## Documentation Index > Fetch the complete documentation index at: https://docs.unpage.ai/llms.txt > Use this file to discover all available pages before exploring further. # Rootly Our Rootly integration allows [Agents](/concepts/agents) to learn about, filter, and take action on incidents happening in your infrastructure. * Rootly Incidents * **list\_recent\_incidents**: List recent Rootly incidents * **get\_incident\_details**: Retrieve incident details by ID * **get\_alert\_details\_for\_incident**: Get alert details for an incident * **post\_status\_update**: Post a status update to an incident * **resolve\_incident**: Resolve an incident * **mitigate\_incident**: Mitigate an incident * **acknowledge\_incident**: Acknowledge an incident * **add\_incident\_event**: Add event to the incident timeline * **log\_investigation\_finding**: Log an investigation finding for root cause analysis * **log\_action\_taken**: Log an action taken during incident response * **log\_escalation**: Log an incident escalation * **log\_communication**: Log a communication event * **get\_incident\_timeline**: Get the complete timeline of events for an incident * **update\_incident\_event**: Update an existing incident event * **delete\_incident\_event**: Delete an incident event\`\`\` ## Prerequisites To configure the Rootly integration you'll need to generate a Rootly API key. In the Rootly UI, navigate to your organization settings. Go to "Organization Settings > API Keys" and create a new token with the necessary permissions for incident management. ## Configuration Configure the Rootly plugin by running `uv run unpage configure` or by editing the `~/.unpage/profiles//config.yaml` file: ```yaml theme={null} plugins: # ... rootly: enabled: true settings: api_key: # required ``` Alternatively, you can set the `ROOTLY_API_KEY` environment variable. ## Developing Agents Your Agents can react to Rootly incidents by adding context from your [Knowledge Graph](/concepts/knowledge-graph), pulling [Metrics](/plugins/metrics), or running custom [Shell Commands](/plugins/shell). Learn more about [Creating Agents](/concepts/agents). ### Running Locally You can test your Agents locally on past or current Rootly incidents by passing in a Rootly incident ID or URL to `unpage agent run`: ```bash theme={null} uv run unpage agent run --rootly-incident 01234567-89ab-cdef-0123-456789abcdef ``` You can also use a full Rootly incident URL: ```bash theme={null} uv run unpage agent run --rootly-incident https://app.rootly.com/incidents/01234567-89ab-cdef-0123-456789abcdef ``` Alternatively, you can use the interactive quickstart to select from recent incidents: ```bash theme={null} uv run unpage agent quickstart ``` Unpage will fetch the incident automatically and send it to your Agent. The Agent thought process, tool calls, and output will be printed to `stdout`. ### Webhooks Agent workflows can run automatically by configuring Rootly to send webhooks to your [Unpage Server](/commands/agent#subcommand%3A-serve). Configure your Rootly webhooks to send incident events to your Unpage Server endpoint at `/webhook` (like `https://unpage.yourdomain.com/webhook`). During development you can tunnel to your local Unpage instance using ngrok by running `uv run unpage agent serve --tunnel` (see [Unpage Server](/commands/agent#subcommand%3A-serve) for details). Unpage will now receive webhooks from Rootly and send them to the [Router](/concepts/router), which will decide which [Agent](/concepts/agents) workflow to run. For production deployments with Rootly integration, see our [Deployment Guide](/howto/deployment-guide) for complete setup instructions including Docker configuration and GitHub Actions CI/CD. ## Tools The Rootly plugin provides the following tools to Agents and MCP Clients: Get a Rootly incident by ID, including all incident details. **Arguments** The ID of the Rootly incident. Typically a UUID string. For example "01234567-89ab-cdef-0123-456789abcdef". **Returns** `dict`: The incident JSON payload, including all incident details.
Get the details of the alert(s) for a Rootly incident. **Arguments** The ID of the Rootly incident. Typically a UUID string. For example "01234567-89ab-cdef-0123-456789abcdef". **Returns** `list[dict]`: The list of alert details (incident events).
Post a status update to a Rootly incident. **Arguments** The ID of the Rootly incident. Typically a UUID string. For example "01234567-89ab-cdef-0123-456789abcdef". The status update message to post. **Returns** `None`
Resolve a Rootly incident. **Arguments** The ID of the Rootly incident. Typically a UUID string. For example "01234567-89ab-cdef-0123-456789abcdef". An optional message to include with the resolution. **Returns** `None`
Mitigate a Rootly incident. **Arguments** The ID of the Rootly incident. Typically a UUID string. For example "01234567-89ab-cdef-0123-456789abcdef". **Returns** `None`
Acknowledge a Rootly incident. **Arguments** The ID of the Rootly incident. Typically a UUID string. For example "01234567-89ab-cdef-0123-456789abcdef". **Returns** `None`
Add a timeline event to a Rootly incident for root cause analysis **Arguments** The ID of the Rootly incident. Typically a UUID string. For example "01234567-89ab-cdef-0123-456789abcdef". Description of the event/activity Event visibility - "internal" or "external" (default: "internal") **Returns** `dict`: The created event data
List recent Rootly incidents **Arguments** Maximum number of incidents to return (default: 10) **Returns** `list[dict]`: List of recent incidents with their details
Log an investigation finding for root cause analysis **Arguments** The Rootly ID of the incident The investigation finding or discovery Source of the finding (e.g., 'logs', 'metrics', 'database') Event visibility - "internal" or "external" (default: "internal") **Returns** `dict`: The created event data
Log an action taken during incident response **Arguments** The Rootly ID of the incident The action that was taken The result or outcome of the action Event visibility - "internal" or "external" (default: "internal") **Returns** `dict`: The created event data
Log an incident escalation **Arguments** The Rootly ID of the incident Who or what team the incident was escalated to Reason for the escalation Event visibility - "internal" or "external" (default: "internal") **Returns** `dict`: The created event data
Log a communication event (e.g., customer notification, internal update) **Arguments** The Rootly ID of the incident Type of communication (e.g., "Customer Notification", "Team Update") Details of the communication Event visibility - "external" for customer-facing, "internal" for team-only (default: "external") **Returns** `dict`: The created event data
Get the complete timeline of events for an incident **Arguments** The Rootly ID of the incident **Returns** `list`: List of all events/timeline entries for the incident
Update an existing incident event **Arguments** The ID of the event to update Updated description of the event Event visibility - "internal" or "external" (default: "internal") **Returns** `dict`: The updated event data
Delete an incident event **Arguments** The ID of the event to delete **Returns** `dict`: Response from the deletion request