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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Create connector

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

* Release version: Yokohama
* 
* Updated February 11, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

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

## Before you begin

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

Role required: sn_ext_conn.xcc_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 must 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 Confluence Cloud tile, then select Next.
5. On the Connection settings page, fill in the connection settings.  
   {#create-ext-cont-connector-acc__table_uvz_jrv_sdc__entry__2}

   | Connection setting | Description |
   |-|-|
   | Connector name | Unique name for this Atlassian Confluence Cloud external content connector. |
   | URL | URL for your Atlassian Confluence Cloud source system, in this format: <kbd class="ph userinput">https://&lt;your-instance-name&gt;.atlassian.net</kbd>. |
   | API Key | API key from your Atlassian Administration console. If you don't have this API key, ask your Atlassian administrator for it. |
   | Client ID | Client identifier for the OAuth 2.0 Atlassian developer application that grants Confluence API access to your Atlassian Confluence Cloud source system. If you don't have this client identifier, ask your Atlassian administrator for it. |
   | Client Secret | OAuth 2.0 client secret for the OAuth 2.0 Atlassian developer application that grants Confluence API access to your Atlassian Confluence Cloud source system. If you don't have this client secret, ask your Atlassian administrator for it. |
   [Table 1. Connection settings]

   {#create-ext-cont-connector-acc__table_uvz_jrv_sdc} {#create-ext-cont-connector-acc__connection-settings-step}
{#create-ext-cont-connector-acc__connection-settings-step}
6. Save and validate your connection settings.
   1. Select Validate Connection.  
      A pop-up window reports that the connector is requesting access to your Atlassian account.
   2. In the Use app on field of the pop-up window, select the site that you specified the URL for in step [5](https://www.servicenow.com/docs/OffN1pub9eDAIF~CmYmlgA#create-ext-cont-connector-acc__connection-settings-step), then select Accept.  

   {#create-ext-cont-connector-acc__substeps_o5l_1tx_vgc}  
   Note:  
   If validation of your connection settings fails, the system shows an error message. Verify your connection settings to ensure they're correct. If permissions required by the connector are missing or incorrectly configured in the source system, a warning message appears showing the permissions that must be corrected. Provide the information from this message to your source system administrator.
7. After your connection settings are validated, select Next.
8. On the Crawl settings page, modify any default crawl settings that you want to override for this connector, then select Next.  
   If you want to skip this step for now, select Skip instead of Next. You can modify the crawl settings for this connector from the External Content Admin Home page. For details on this procedure and the available crawl settings, see [Configure crawl settings for an Atlassian Confluence Cloud external content connector](https://www.servicenow.com/docs/dUTSi3R4p3nH5ureRG46cQ "Specify the spaces you want your Atlassian Confluence Cloud external content connector to crawl. Define inclusion or exclusion filters to dictate the types of content the crawl retrieves and feeds to AI Search for indexing.").
9. On the User permission settings page, modify any default user permission settings that you want to override for this connector.  
   If you want to skip this step for now, select Skip instead of Next. You can modify the user permission settings for this connector from the External Content Admin Home page. For details on this procedure and user permission settings, see [Configure user permission settings for an external content connector](https://www.servicenow.com/docs/61IqHyAKjlUk0sNKovSmoA "Override the default field mappings for an external content connector's user permission crawls. Specify the fields that uniquely identify user security principals in your source system and users in your ServiceNow AI Platform instance. Optionally execute a custom script to transform security principal IDs before they're compared with the IDs of users in your instance."). {#create-ext-cont-connector-acc__new-connector-user-mapping-settings-cmd}
10. On the Create crawl page, create a content crawl for this connector by selecting a crawl scope (if supported) and any desired options, then select Next.  
    If you want to skip this step for now, select Skip instead of Next. You can create and run crawls for this connector from the External Content Admin Home page. For details on creating content crawls, see [Create a content crawl for an external content connector](https://www.servicenow.com/docs/cHKxITeSqLvmLnYo9QVnHg "Retrieve searchable content and metadata from your source system with a content crawl. Run the crawl as a one-time task or schedule it to run on a recurring basis.").
11. On the Connect search profile page, use the Connect to search profile field and Add button to add any search profiles that you want to connect this external content connector's default search source to, then select Save.  
    If you want to skip this step for now, select Skip instead of Next. You can connect search sources for this connector to search profiles from the External Content Admin Home page. For details on connecting an external content connector to search profiles, see [Connect an external content connector to a search profile](https://www.servicenow.com/docs/m4wcX0hwKbI9DWhQaOTQfg "Make results from an external content connector searchable in your portals and search applications by connecting its search sources to your existing search profiles.").

## Result

Your new external content connector appears in the Connectors list on the External Content Admin Home page.

## What to do next

To retrieve searchable content and security principals with your new connector, you must configure and run content and user mapping crawls for it. You can modify your new connector's crawl settings and create crawls for it from the External Content Admin Home page even if you skipped these steps during connector creation.

* To learn how to configure your new connector's crawl settings, see [Configure crawl settings for an Atlassian Confluence Cloud external content connector](https://www.servicenow.com/docs/dUTSi3R4p3nH5ureRG46cQ "Specify the spaces you want your Atlassian Confluence Cloud external content connector to crawl. Define inclusion or exclusion filters to dictate the types of content the crawl retrieves and feeds to AI Search for indexing.").
* For details on creating crawls for your new connector, see [Create a content crawl for an external content connector](https://www.servicenow.com/docs/cHKxITeSqLvmLnYo9QVnHg "Retrieve searchable content and metadata from your source system with a content crawl. Run the crawl as a one-time task or schedule it to run on a recurring basis.") and [Create a user permission crawl for an external content connector](https://www.servicenow.com/docs/qWGajmyPchw0rgi0C28swg "Retrieve security principals from your source system with a user permission crawl. Run the crawl as a one-time task or schedule it to run on a recurring basis.").
{#create-ext-cont-connector-acc__ul_zkt_3qj_4fc}  
To make content crawled by your new connector searchable in portals and search applications, you must link one of its search sources to the search profile used by each portal or search application. You can use the connector's default search source or create your own custom search sources.

Default search source
:   By default, the system creates a search source that includes all content from your external content connector's indexed source.

Custom search sources
:   You can create your own search sources with filters to specify which content from the connector's indexed source is searchable. To view the connector's indexed source, navigate to AllAI SearchAI Search IndexIndexed Sources. For information about creating search sources, see [Search sources in AI Search](https://www.servicenow.com/docs/Lh3hgMrXzdsivyY0rZSrnw "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.").
You can link connector search sources to search profiles from the External Content Admin Home page. For details on this procedure, see [Connect an external content connector to a search profile](https://www.servicenow.com/docs/m4wcX0hwKbI9DWhQaOTQfg "Make results from an external content connector searchable in your portals and search applications by connecting its search sources to your existing search profiles.").

*[\>]: and then