Rootly is an incident management platform that helps engineering and SRE teams respond to, resolve, and learn from incidents. This connector uses the Rootly REST API to ingest incidents, teams, users, severities, post-mortems, and other incident-management resources into Nexla.
Power end-to-end data operations for your Rootly API with Nexla. Our bi-directional Rootly connector is purpose-built for Rootly, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Rootly or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Rootly workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating a Rootly credential, you need a Rootly API key. Rootly authenticates all API requests with a bearer token sent in the Authorization header (Authorization: Bearer <API_KEY>) over HTTPS against the https://api.rootly.com/v1 base URL.
To generate a Rootly API key, follow these steps:
Sign in to your Rootly account with an account that has permission to manage API keys.
Open the organization dropdown and navigate to Organization Settings > API Keys.
Click Generate New API Key, and choose the appropriate scope (Global, Team, or Personal) for your use case.
Copy the generated API key and store it securely. This key grants access to your Rootly data based on its assigned scope and should be treated as a secret.
For more details on authentication, scopes, and available resources, see the Rootly API documentation.
After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Rootly API key in the API Key field. This is the key you generated in Prerequisites and is sent as a bearer token in the Authorization header for all requests to the Rootly API.
Your Rootly API key is sensitive information and should be kept confidential. If a key is compromised, revoke it in Organization Settings > API Keys and generate a new one.
For more information about authentication and available endpoints, see the Rootly API documentation.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Rootly connector tile, then select the credential that will be used to connect to Rootly, and click Next; or, create a new Rootly credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Rootly endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
[Rest API] List Users
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/users endpoint. Retrieve users into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Users Notification Rules
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/users_notification_rules endpoint. Retrieve users_notification_rules into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Authorizations
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/authorizations endpoint. Retrieve authorizations into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Teams
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/teams endpoint. Retrieve teams into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Incident Roles
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/incident_roles endpoint. Retrieve incident_roles into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Incident Permission Sets
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/incident_permission_sets endpoint. Retrieve incident_permission_sets into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Incident Permission Sets Resources
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Roles
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/roles endpoint. Retrieve roles into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Workflow Groups
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/workflow_groups endpoint. Retrieve workflow_groups into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Dashboards
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/dashboards endpoint. Retrieve dashboards into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Incidents
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/incidents endpoint. Retrieve incidents into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Dashboards Panels
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/dashboards_panels endpoint. Retrieve dashboards_panels into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Incident Types
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/incident_types endpoint. Retrieve incident_types into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List IP Ranges
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/ip_ranges endpoint. Retrieve ip_ranges into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Sub Statuses
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/sub_statuses endpoint. Retrieve sub_statuses into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Incidents Sub Statuses
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/incidents_sub_statuses endpoint. Retrieve incidents_sub_statuses into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Post Mortems
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/post_mortems endpoint. Retrieve post_mortems into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Status Pages
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/status_pages endpoint. Retrieve status-pages into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
[Rest API] List Severities
This endpoint template retrieves data from the Rootly https://api.rootly.com/v1/severities endpoint. Retrieve severities into your Nexla flow for analysis, reporting, or integration.
Nexla automatically paginates through the endpoint, fetching subsequent pages until all available records have been retrieved.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Rootly data sources can also be manually configured to ingest data from any valid Rootly API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Rootly data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
