---
title: Create a MongoDB connection
description: Establish a zero copy connection to a MongoDB database in Zero Copy Connector Hub.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/integrate-applications/create-mongodb-connection-zcc.html
release: australia
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 1
breadcrumb: [MongoDB, Community connectors, Zero Copy Connectors, Workflow Data Fabric]
---

# Create a MongoDB connection

Establish a zero copy connection to a MongoDB database in Zero Copy Connector Hub.

## Before you begin

Role required: df\_connection\_admin

## About this task

Work with your data source admin to create a connection to MongoDB. For additional information about connecting, refer to the [MongoDB connector documentation](https://trino.io/docs/current/connector/mongodb.html).

**Note:** This connector was developed by the open-source community and made available through the ServiceNow AI Platform for general use. Functionality can vary and might not cover all use cases supported by primary connectors.

## Procedure

1.  Navigate to the available community connectors in Zero Copy Connector Hub in one of the following ways:

    -   Navigate to **All** > **Zero Copy Connector Hub** > **Available connectors** > **Community connectors**.
    -   Navigate to **Admin** > **Zero Copy Connector Hub** > **Available connectors** > **Community connectors**.
2.  Find the MongoDB connector and select **Connect**.

3.  On the form, fill in the fields.

<table id="table_kmx_fw1_2fc"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td class="sub-head" colspan="2">

Name and description

</td></tr><tr><td>

Connection label

</td><td>

Unique name for this connection. This helps in identifying the connection within your system.

</td></tr><tr><td>

Connection name

</td><td>

System-generated name based on the Connection label. This field cannot be modified once the connection is established.

</td></tr><tr><td>

Short description

</td><td>

Description of the connection explaining what it is about.

</td></tr><tr><td class="sub-head" colspan="2">

Connection attributes

</td></tr><tr><td>

Connection URL

</td><td>

URL to establish the connection. For example:`mongodb://<host>:<port>/database_name?ssl=true&authSource=external&authMechanism=MONGODB-X509`

</td></tr></tbody>
</table>4.  Configure secure authentication by providing truststore information.

<table id="choicetable_dth_vsc_qfc"><thead><tr><th align="left" id="d428466e218">

Option

</th><th align="left" id="d428466e221">

Description

</th></tr></thead><tbody><tr><td id="d428466e227">

**Upload truststore file**

</td><td>

1.  Select **Attach TrustStore file**.
2.  Browse and select the truststore file.


</td></tr><tr><td id="d428466e248">

**Enter truststore contents manually**

</td><td>

Copy and paste the contents of the keystore file.

</td></tr></tbody>
</table>5.  Configure secure authentication by providing keystore information.

<table id="choicetable_zbg_15c_qfc"><thead><tr><th align="left" id="d428466e266">

Option

</th><th align="left" id="d428466e269">

Description

</th></tr></thead><tbody><tr><td id="d428466e275">

**Upload keystore file**

</td><td>

1.  Select **Attach KeyStore file**.
2.  Browse and select the keystore file.


</td></tr><tr><td id="d428466e296">

**Enter keystore contents manually**

</td><td>

Copy and paste the contents of the keystore file.

</td></tr></tbody>
</table>6.  Enter the truststore password.

7.  Enter the keystore password.

8.  Select **Connect**.


## Result

A test connection is made to the external data source, verifying that the connection details are correct and the data source is accessible.

## What to do next

If the connection succeeds, configure data steward access on the **Access Control** tab. See [Manage access to an established connection using roles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/manage-access-connection-zcc.md).

If the connection fails, verify the connection details with your data source administrator and try again.