---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Create an Atlassian Jira Cloud external content connector

# Create an Atlassian
Jira Cloud external content connector {#ariaid-title1}

* Release version: Xanadu
* 
* Updated June 25, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Create an external content connector to retrieve searchable content and security principals from your Atlassian
Jira Cloud source system.

## Before you begin

A source system administrator must have already configured your Atlassian
Jira Cloud source system to allow access by the Atlassian
Jira Cloud external content connector. For details on configuring these settings in the source system, see [Configure Atlassian Jira Cloud for external content indexing](https://www.servicenow.com/docs/xAbVIaQfBH8S_mSn~GTOGQ "Register an OAuth 2.0 integration in the Atlassian Developer console and create an API key in Atlassian Administration to allow the Atlassian Jira Cloud external content connector to crawl projects and security principals in your Atlassian Jira Cloud source system.").

Role required: admin

## Procedure

1. Navigate to AllExternal Content ConnectorsExternal Content Admin Home.
2. If prompted, select Switch scope to switch to the External Content Connectors Admin scope.  
   You need to be in this scope to create or edit external content connectors.
3. In the Connectors section, select New.
4. On the Choose source page, select the Jira Cloud tile, then select Next.
5. On the Connector details page, fill in the required connection settings.  
   {#create-ext-cont-connector-jira__table_uvz_jrv_sdc__entry__2}

   | Connection setting | Description |
   |-|-|
   | Connector name | Unique name for this Atlassian Jira Cloud external content connector. |
   | URL | URL for your Atlassian Jira Cloud source system, in this format: <kbd class="ph userinput">https://jira.example.com</kbd>. |
   | Instance ID | Instance ID (cloud ID) for your Atlassian Jira Cloud source system. If you're not sure how to find the instance ID for your Atlassian Jira Cloud source system, contact your Atlassian administrator. |
   | API Key | API key from your Atlassian Administration console. If you're not sure how to find the API key in your Atlassian Administration console, contact your Atlassian administrator. |
   | Client ID | Client identifier for the OAuth 2.0 Atlassian developer application that grants Confluence API access to your Atlassian Jira Cloud source system. If you're not sure how to find the Client ID for the OAuth 2.0 application in your Atlassian developer console, contact your Atlassian administrator. |
   | Client Secret | OAuth 2.0 client secret for the OAuth 2.0 Atlassian developer application that grants Jira API access to your Atlassian Jira Cloud source system. If you're not sure how to find the Client Secret for the OAuth 2.0 application in your Atlassian developer console, contact your Atlassian administrator. |
   [ ]

   {#create-ext-cont-connector-jira__table_uvz_jrv_sdc}
6. Select Save and validate.  
   Note:  
   If validation fails, an error message appears. Double-check your connection settings to ensure they're correct.

## Result

Your new Atlassian
Jira Cloud external content connector appears in the Connectors section.

## What to do next

You can optionally define crawl settings for your new Atlassian
Jira Cloud external content connector. Using these settings, you can limit the set of projects you want the connector to crawl, or define the file extensions for documents you want the connector's crawls
to include or exclude. To learn how to configure the connector's crawl settings, see [Configure crawl settings for the Atlassian Jira Cloud external content connector](https://www.servicenow.com/docs/fm_VqlZxPqwfOTrvQnMAEg "Specify the projects you want your Atlassian Jira Cloud external content connector to crawl. Define inclusion or exclusion filters for file extensions to dictate the types of documents the crawl retrieves and feeds to AI Search for indexing.").

If you want the connector to crawl everything in the source system, and don't want to apply file-extension inclusion or exclusion filters, you can skip
definition of crawl settings and go straight on to define a crawl schedule for your new connector or run one-time crawls for it. For details on defining a crawl schedule, see [Define a crawl schedule for an external content connector](https://www.servicenow.com/docs/XCXxlqJZb8I1hurNFcj9JQ "Keep your search index up to date by scheduling regular document and user mapping crawls for your external content connector. Scheduled crawls can run daily or on selected days of the week, starting at a time that you specify."). To learn about running one-time crawls, see [Run a one-time full or partial document crawl for an external content connector](https://www.servicenow.com/docs/WF27NJ6iuXMWR2w_4osxvw "Retrieve document content and metadata from all or part of your external content connector's data source on demand. A document crawl sends retrieved content and metadata to AI Search for indexing, making them available to users of your AI Search applications.") and [Run a one-time user mapping crawl for an external content connector](https://www.servicenow.com/docs/y6XALmRIpXNR6kXFwU19LQ "Retrieve users and group access permissions from your external content connector's data source on demand. A user mapping crawl maps retrieved user and group permissions to your ServiceNow AI Platform users to facilitate content security in your AI Search applications.").

You can create search sources for the connector's indexed source and link them to your search profiles. To view the connector's indexed source,
navigate to AllAI SearchAI Search IndexIndexed Sources. For information about creating search sources and linking them to search profiles, see [Search sources in AI Search](https://www.servicenow.com/docs/rRLONKzjnEhenBae4lDmeg "Define search sources to make your searchable content available in search experiences. Choose an indexed source and configure optional filter conditions to limit the content that users can search.").

*[\>]: and then