---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Onboard Split using Classic

# Onboard Split to DevOps Change Velocity --- Classic {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Create a Split tool record to connect and discover workspaces, environments,
segments, and feature flags from the connected Split tool.

## Before you begin

Role required: sn_devops.admin

## Procedure

1. Create a tool record in DevOps to automatically connect to Split and get the webhook URL.
   1. Navigate to DevOpsToolsCreate New (legacy) and create a record.
   2. Enter a Tool Name and fill in the tool details.  

      |-|-|
      | Tool Integration | Split |
      | Tool URL | Split tool URL. For example: <kbd class="ph userinput">https://api.split.io</kbd> |
      | Tool Username | Split username |
      | Tool Password / Access Token | Split password or access token. For information on creating a Split token, see [Enable integration with ServiceNow DevOps in Split tool](https://servicenow-prod.fluidtopics.net/02_3JGZNjOOLav8i0XG_Og "Enable integration with ServiceNow DevOps in Split tool and restrict approvers to only the enabled integration for your environment."). |
      [ ]

      {#create-split-tool-record-devops__table_brq_ccf_rjb}

      MID Server is optional. Select MID Server for
      an on-premises tool that is attached to a MID Server. Application is
      automatically set to DevOps and capability is set to
      REST.
   3. Select Submit.  
      The tool is automatically Connected Successfully using a connection alias, and HTTP tool connection (basic authentication credential).  
      Note:  
      If you do not have global admin privileges for your tool (to allow automatic configuration of the webhook URL), you may need to have the tool admin user configure it for you (cut and paste the webhook URL into the tool configuration). Once the webhook is configured in the tool, Enter Manual Configuration Mode to connect to the tool manually, then exit.
   {#create-split-tool-record-devops__substeps_uwd_wlb_ymb}

On successful tool creation, you're taken to the tool record page.

2. If you want to control access to the tool, add the groups that must be given access to the tool in the Maintained by field on the Access tab.  
   The tasks the users in the groups can perform depends on the roles assigned to them.
   * DevOps Tool Owner role: Can view and edit the tool.
   * DevOps App Owner role: Can view the tool and can associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects (such as plans, repositories, and pipelines).
   * DevOps Administrator role: Can edit all tools.
   * Other DevOps roles: Can view the tool.

   {#create-split-tool-record-devops__ul_qnp_fkx_5wb}  
   Note:  
   Only groups containing users with DevOps roles are available for selection in the Maintained by field.

   The All App Owners can view and associate tool objects to applications option becomes available for selection if you choose to restrict access to the tool. This option enables all users having the DevOps App Owner role to access the tool. If selected, they'll be able to view, associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects.
3. Discover workspaces, environments, segments, and feature flags from the connected Split tool by selecting Discover.
4. Automatically configure the webhook URL in Split tool by selecting Configure.  
   ServiceNow Integration will be activated on Split. Webhooks are auto-configured and notifications are sent from Split tool to DevOps.

## Example

The following example specifies how changes made in the Split tool are notified to
ServiceNow DevOps through the webhook.

* Inbound events are created in ServiceNow for status (Requested, Approved, Rejected or Withdrawn) of the event.
* Feature Flag requests (DevOps \> Feature Flag \> Feature Flag Requests) are created or updated based on the status.
* A change request is created for every Feature Flag request, and work notes on the change request is updated with basic change details on the feature flag.
{#create-split-tool-record-devops__ul_y52_mhl_fvb}

*[\>]: and then