Rootly

Rootly + Konnectify

Rootly Integration with Konnectify

Connect Rootly, an incident management and response platform, with Konnectify to automate incident response, alert handling, timeline updates, services, and support workflows across your stack.

Incidents Alerts Alert Events Incident Events Action Items Services 8 Triggers 47 Actions

ON THIS PAGE

→ What is Rootly? → API & authentication → How to connect → Triggers (8) → Actions (47) → Popular automations → FAQ

What is Rootly?

Rootly is an incident management and response platform used by engineering, DevOps, SRE, and support teams to coordinate outages, alerts, post-incident workflows, and operational tasks. It helps teams create incidents, manage alert lifecycles, document timeline events, assign roles, track action items, and maintain service information.

With Konnectify, you can connect Rootly to your support, monitoring, chat, CRM, project management, and data tools so your incident response workflows move automatically from detection to resolution.

New to Rootly?

Explore Rootly for incident management, response orchestration, and operational reliability workflows.

Visit Rootly →

New to Konnectify?

Build no-code and low-code automations that connect Rootly with the rest of your business tools.

What you can automate

• Create, update, restart, mitigate, resolve, cancel, or delete incidents.

• Create alerts, snooze alerts, escalate alerts, and resolve alert noise.

• Add incident timeline events and alert notes for response context.

• Attach alerts to incidents and list related incident alerts.

• Create, update, and list action items for post-incident follow-up.

• Maintain Rootly service records and operational ownership data.

API & Authentication

Authentication method: API Key authentication

This Rootly connector uses an API key credential. When you create a connection in Konnectify, enter your Rootly API Key in the required API Key field. Konnectify securely uses this key to authenticate API requests to your Rootly account.

You can typically generate or copy your API key from your Rootly account settings or API settings area. Ensure the key has permission to access the Rootly resources used by your workflow.

Supported API capabilities

Incident creation, updates, retrieval, listing, deletion, and lifecycle transitions.
Alert creation, updates, retrieval, listing, escalation, snoozing, resolution, and incident linking.
Alert receipts and alert event management, including note-style alert events.
Incident timeline event creation, updates, retrieval, deletion, and listing.
Incident action item creation, updates, retrieval, and listing.
Service creation, updates, retrieval, listing, and deletion.
Incident subscriber management and incident role assignment.

Note: Rootly API access, available endpoints, event delivery, and rate limits may vary based on your Rootly plan, workspace configuration, and API key permissions. If a workflow fails due to permissions or throttling, review your Rootly plan and API settings.

For endpoint-level details, refer to the official Rootly API documentation.

How to Connect Rootly to Konnectify

Prerequisites

An active Rootly account with API access enabled.
A Rootly API Key with permissions for the incidents, alerts, services, and related resources you want to automate.
A Konnectify account with permission to create or edit workflows.
Sample Rootly records for testing, such as an incident, alert, service, or action item.

Add Rootly to a Workflow

Open Konnectify and create a new workflow, or edit an existing workflow.
Search for Rootly in the app selector.
Choose a Rootly trigger or action depending on your automation goal.

Authorize via API Key authentication

Select Connect new account.
Paste your Rootly API Key into the API Key field.
Save the connection and let Konnectify validate access.

Configure the Trigger or Action

Map required fields such as Incident ID, Alert ID, User IDs, role IDs, service attributes, or event details.
For update actions, populate only the fields you want to change.
Use output from earlier workflow steps to dynamically fill Rootly fields.

Important: Destructive actions such as deleting incidents, alert events, incident events, or services are permanent in Rootly. Test with non-production records first.

Test the Workflow

Run a test for the trigger or action.
Confirm that Konnectify receives Rootly webhook payloads or API responses.
Review generated incidents, alerts, events, action items, or services in Rootly.

Activate the Workflow

Turn the workflow on when test results look correct.
Monitor early runs to verify field mapping, permissions, and rate limit behavior.
Adjust filters or conditions to avoid unnecessary incident or alert updates.

Triggers 8

Rootly includes 8 webhook triggers. These triggers fire when supported incident or alert events occur in Rootly and send the event payload to Konnectify in real time.

Incidents 7 triggers

Incident Created

Fires whenever a new incident is created in Rootly.

Incident Updated

Fires whenever an existing incident is updated in Rootly.

Incident In Triage

Fires whenever the status of an incident changes to In Triage in Rootly.

Incident Mitigated

Fires whenever the status of an incident is changed to Mitigated in Rootly.

Incident Resolved

Fires whenever an incident is fully resolved in Rootly.

Incident Cancelled

Fires whenever an incident is cancelled or marked as a false alarm in Rootly.

Incident Deleted

Fires whenever an incident is permanently deleted from Rootly.

Alerts 1 trigger

Alert Created

Fires whenever a new alert is created in Rootly.

Actions 47

Use Rootly actions in Konnectify to create, retrieve, update, list, transition, and delete Rootly resources as part of automated incident response workflows.

Incidents12 actions

Create Incident

Creates a new incident in Rootly with the specified attributes. Title is auto-generated if left blank.

Update Incident

Updates an existing incident in Rootly. Map the Incident ID and populate only the fields you wish to change.

Get Incident

Fetches details of a specific Rootly incident using its ID, with optional include parameters for expanded relational data.

List Incidents

Returns a paginated list of incidents based on specified filtering parameters.

Delete Incident

Permanently deletes an existing incident in Rootly using its unique ID.

Mitigate Incident

Updates the status of an incident to mitigated and logs the mitigation message.

Resolve Incident

Updates the status of an incident to resolved and logs the resolution message.

Cancel Incident

Updates the status of an incident to cancelled and logs the cancellation message.

In Triage Incident

Updates the status of an existing incident to 'in triage'.

Duplicate Incident

Updates the status of an incident to duplicate and logs the resolution message.

Restart Incident

Updates the status of an existing incident back to 'started' (restarted).

Detach from Parent Incident

Removes the parent-child relationship of a specific incident, making it a standalone incident.

Incident Subscribers & Roles4 actions

Add Subscribers to Incident

Subscribes specific users to an incident using their User IDs.

Remove Subscribers from Incident

Unsubscribes specific users from an incident using their User IDs.

Assign Role to User

Assigns a defined incident role (e.g., Commander, Scribe) to a specific user for a given incident.

Unassign Role from User

Unassigns a previously assigned incident role (e.g., Commander, Scribe) from a specific user for a given incident.

Alerts10 actions

Create Alert

Creates a new alert in Rootly with the specified attributes.

Update Alert

Updates an existing alert in Rootly. Map the Alert ID and populate only the fields you wish to change.

Get Alert

Fetches details of a specific Rootly alert using its ID, with optional include parameters for expanded relational data.

Resolve Alert

Resolves an alert and optionally resolves any incidents that are directly related to it.

Snooze Alert

Temporarily snoozes an alert for a specified number of minutes before it re-triggers.

Escalate Alert

Triggers an escalation for a specific alert using an Escalation Policy ID and level.

List Alerts

Returns a paginated list of alerts based on specified filtering parameters.

Attach Alerts to Incident

Links one or more existing alerts to a specific incident in Rootly.

List Incident Alerts

Fetches a list of all alerts currently attached to a specific Rootly incident.

Get Alert Receipt

Fetches details of a specific Rootly alert receipt using its unique ID.

Alert Events6 actions

Create Alert Event

Creates a new alert event (like a note) attached to a specific alert.

Update Alert Event

Updates an existing alert event. Note: Only alert events with kind='note' can be updated.

Get Alert Event

Fetches details of a specific Rootly alert event using its unique ID.

Delete Alert Event

Permanently deletes an existing alert event in Rootly using its unique ID.

List Alert Events

Returns a paginated list of events attached to a specific alert based on specified filtering parameters.

List All Alert Events

Returns a paginated list of all alert events across your organization based on specified filtering parameters.

Incident Events5 actions

Create Incident Event

Creates a new timeline event attached to a specific incident.

Update Incident Event

Updates the summary or visibility of an existing incident event.

Get Incident Event

Fetches details of a specific Rootly incident event using its unique ID.

Delete Incident Event

Permanently deletes an existing incident event in Rootly using its unique ID.

List Incident Events

Returns a paginated list of events (timeline) for a specific incident.

Action Items5 actions

Create Action Item

Creates a new action item associated with an incident.

Update Action Item

Updates an existing action item in Rootly.

Get Action Item

Fetches details of a specific Rootly incident action item using its unique ID.

List Incident Action Items

Returns a paginated list of action items attached to a specific incident.

List All Action Items

Returns a paginated list of action items based on specified filtering parameters.

Services5 actions

Create Service

Creates a new service in Rootly with the specified attributes.

Update Service

Updates an existing service in Rootly.

Get Service

Fetches details of a specific Rootly service using its unique ID.

Delete Service

Permanently deletes an existing service in Rootly using its unique ID.

List Services

Returns a paginated list of services in your organization based on specified filtering parameters.

Popular Automations

Here are common ways teams use Rootly with Konnectify to accelerate incident response and operational follow-through.

Notify teams when a new incident starts

When Rootly creates a new incident, trigger downstream notifications, create a timeline event, and assign response ownership.

Incident Created → Create Incident Event → Assign Role to User

Turn critical alerts into incidents

Use new Rootly alerts as an entry point for incident creation, then attach related alerts for full context.

Alert Created → Create Incident → Attach Alerts to Incident

Create follow-up tasks after mitigation

After an incident is mitigated, automatically create action items and document the mitigation in the incident timeline.

Incident Mitigated → Create Action Item → Create Incident Event

Resolve noisy alerts when incidents close

When an incident is resolved, list related alerts, resolve them, and keep records synchronized.

Incident Resolved → List Incident Alerts → Resolve Alert

FAQ

How does Rootly authenticate with Konnectify?

Rootly uses API Key authentication in Konnectify. Create or copy an API key from Rootly, paste it into the required API Key field when creating the connection, and save the connection.

Which Rootly plans are supported?

Any Rootly plan that provides API key access and webhook event support can be used. Some endpoints, roles, escalation features, or incident resources may depend on your Rootly plan and workspace configuration.

How do Rootly triggers work in Konnectify?

The available Rootly triggers are webhook-based. Rootly sends event payloads to Konnectify when matching events occur, such as incident.created, incident.updated, incident.resolved, or alert.created.

Does this connector prevent duplicate Rootly records?

This connector does not include dedicated upsert actions. To prevent duplicates, use list or get actions before creating records, add filters or conditions in your workflow, and store external IDs where appropriate.

How are Rootly API rate limits handled?

If Rootly returns a rate limit response, review the failed run details in Konnectify and reduce request volume by adding workflow filters, batching upstream events where possible, or spacing out high-volume automation steps.

Can I connect multiple Rootly accounts?

Yes. You can create separate Rootly connections in Konnectify using different API keys. Name each connection clearly so workflow builders can select the correct Rootly workspace or environment.

Can I automate Rootly incident lifecycle transitions?

Yes. The connector supports lifecycle actions such as In Triage Incident, Mitigate Incident, Resolve Incident, Cancel Incident, Duplicate Incident, Restart Incident, and Detach from Parent Incident, allowing you to automate incident state changes from external signals.

Ready to automate your Rootly workflows?

Connect Rootly to Konnectify and automate incident response, alerts, services, and follow-up work across your tools.

Get started free →