---
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 Bitbucket using Service Catalog

# Onboard Bitbucket to DevOps Change Velocity --- Service Catalog {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Create, connect, discover, and configure your Bitbucket instance using the ServiceNow
Service Catalog.

## Before you begin

Role required: sn_devops.admin or sn_devops.tool_owner

## Procedure

1. Navigate to AllService CatalogCatalog DefinitionsMaintain Items and search for DevOps.  
   Note:  
   You can also access the service catalog from Employee Center or Service portal.
2. From the DevOps catalog items, select and activate DevOps App Onboarding and DevOps Tool Onboarding.
3. After activating, select DevOps Tool Onboarding and select Try it.
4. In the DevOps Tool Onboarding form, enter the tool details:  
   {#sc-bitbucket__table_ubw_p1p_gwb__entry__2}

   | Field | Description |
   |-|-|
   | Tool name | Name for your Bitbucket integration. |
   | Tool integration | Select Bitbucket. |
   | Tool URL | URL of your Bitbucket instance. |
   | Credential type | Select the credential type as one of the following: * Basic Auth * Access Token * OAuth 2.0 - Authorization Code * Oauth 2.0 - Client Credentials {#sc-bitbucket__ul_dtr_24y_52c} For more information, see [Bitbucket integration with DevOps Change Velocity](https://servicenow-prod.fluidtopics.net/6A3cJQ2PJuUbbGh3En8_IA "Connect to your Bitbucket instance to track Bitbucket repositories, commits, branches, and pull requests."). |
   | Use MidServer | 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. |
   [ ]

   {#sc-bitbucket__table_ubw_p1p_gwb}

   For a list of all the permissions required on the credentials for connecting to Bitbucket, see Bitbucket permissions in [Permissions required for DevOps tools](https://servicenow-prod.fluidtopics.net/rkQZOOxQSNdDZ7d5eHch0A "Permissions required in your third-party tool to connect to DevOps Change Velocity.").
5. Select Order Now.  
   A request is created. When the request is approved, the tool is created, connected, and discovered.
6. From the DevOps catalog items, select DevOps App Onboarding.
7. In the DevOps App Onboarding form, enter the details:  

   |-|-|
   | Are you creating a new app or adding to an existing one? | Select from the options whether to create a new app or use an existing app. |
   | App | Enter the name for the app that you're creating or using. |
   | Onboarding pipelines | Leave empty. |
   | Onboarding repositories | Enter the connected Bitbucket tool name. |
   | Repositories | Select the repositories for which you want to configure webhooks and import historical data. |
   | Import from and Import to | Select the dates for which you want to import the data. By default, the last 30 days are selected. You can choose to import data for a maximum of 90 days. |
   | Do you wish to configure webhook for the tool? | Select the check box if you want to configure webhooks for the selected repositories. |
   | Onboarding plans | Leave empty. |
   [ ]

   {#sc-bitbucket__table_vb5_s3p_gwb}
8. Select Order Now.  
   A request is created. When the request is approved, the repository objects are associated to the app record and webhooks are configured for real-time tracking. Historical data is imported for the selected repositories. The Track field is automatically enabled for imported repositories.

*[\>]: and then