> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unstructured.io/llms.txt
> Use this file to discover all available pages before exploring further.
# MongoDB
If you're new to Unstructured, read this note first.
Before you can create a destination connector, you must first sign in to your Unstructured account:
* If you do not already have an Unstructured account, [sign up for free](https://unstructured.io/?modal=try-for-free). After you sign up, you are automatically signed in to your new Unstructured **Let's Go** account, at [https://platform.unstructured.io](https://platform.unstructured.io).
To sign up for a **Business** account instead, [contact Unstructured Sales](https://unstructured.io/?modal=contact-sales), or [learn more](/ui/overview#how-am-i-billed%3F).
* If you already have an Unstructured **Let's Go**, **Pay-As-You-Go**, or **Business SaaS** account and are not already signed in, sign in to your account at
[https://platform.unstructured.io](https://platform.unstructured.io). For other types of **Business** accounts, see your Unstructured account administrator for sign-in instructions,
or email Unstructured Support at [support@unstructured.io](mailto:support@unstructured.io).
After you sign in, the [Unstructured user interface](/ui/overview) (UI) appears, which you use to create your destination connector.
After you create the destination connector, add it along with a
[source connector](/ui/sources/overview) to a [workflow](/ui/workflows). Then run the worklow as a
[job](/ui/jobs). To learn how, try out the [hands-on UI quickstart](/ui/quickstart#remote-quickstart) or watch the 4-minute
[video tutorial](https://www.youtube.com/watch?v=Wn2FfHT6H-o).
You can also create destination connectors with the Unstructured API.
[Learn how](/api-reference/workflow/destinations/overview).
If you need help, email Unstructured Support at [support@unstructured.io](mailto:support@unstructured.io).
You are now ready to start creating a destination connector! Keep reading to learn how.
Send processed data from Unstructured to MongoDB.
The requirements are as follows.
The MongoDB requirements for a MongoDB Atlas deployment include:
For MongoDB Atlas, SCRAM-SHA-1 is not supported for authentication. This means that cluster types that only
include SCRAM-SHA-1, such as **Free**, **M0**, **Flex**, and **Serverless**, are **not** supported.
Unstructured only supports SCRAM-SHA-256 for MongoDB Atlas, which is cryptographically stronger than SCRAM-SHA-1.
If you try to test or use a connector that refers to a cluster type that only includes SCRAM-SHA-1, the
operation will fail, and you will get an error message similar to the following:
`[digital envelope routines] unsupported`.
* A MongoDB Atlas account. [Create an account](https://www.mongodb.com/cloud/atlas/register).
* A MongoDB Atlas cluster. [Create a cluster](https://www.mongodb.com/docs/atlas/tutorial/create-new-cluster/). Be sure to **not**
select a cluster type that only includes SCRAM-SHA-1, such as **Free**, **M0**, **Flex**, or **Serverless**.
* The cluster must be reachable from your application environment, for example by adding IP addresses to your IP access list. [Learn more](https://www.mongodb.com/docs/atlas/setup-cluster-security/#network-and-firewall-requirements).
* The cluster must be configured to allow IP address. [Learn how](https://www.mongodb.com/docs/atlas/security/ip-access-list/#add-ip-access-list-entries).
To get Unstructured's IP address ranges, go to
[https://assets.p6m.u10d.net/publicitems/ip-prefixes.json](https://assets.p6m.u10d.net/publicitems/ip-prefixes.json)
and allow all of the `ip_prefix` fields' values that are listed.
These IP address ranges are subject to change. You can always find the latest ones in the preceding file.
* The cluster must have at least one database. [Create a database](https://www.mongodb.com/docs/compass/current/databases/#create-a-database).
* The database must have at least one user, and that user must have sufficient access to the database. [Create a database user](https://www.mongodb.com/docs/atlas/security-add-mongodb-users/#add-database-users). [Give the user database access](https://www.mongodb.com/docs/manual/core/authorization/).
* The database must have at least one collection. [Create a collection](https://www.mongodb.com/docs/compass/current/collections/#create-a-collection).
For the destination connector, Unstructured recommends that all documents in the target collection have a field
named `record_id` with a `String` data type.
Unstructured can use this field to do intelligent document overwrites. Without this field, duplicate documents
might be written to the collection or, in some cases, the operation could fail altogether.
* The connection string for the cluster. For MongoDB Atlas, this connection string must include the protocol, username, password, host, and cluster name. For example:
```text theme={null}
mongodb+srv://:@/?retryWrites=true&w=majority&appName=
```
To get the connection string in MongoDB Atlas, do the following:
1. Log in to your MongoDB Atlas console.
2. In the sidebar, under **Databases**, click **Clusters**.
3. Click on the cluster you want to connect to.
4. Click **Connect**.
5. Click **Drivers**.
6. Under **Add your connection string into your application code**, copy the connection string.
You can then close the **Connect** dialog in MongoDB Atlas.
Before you use this connection string, be sure to fill in any placeholders in the string, such as your MongoDB Atlas database user's password value.
[Learn more](https://www.mongodb.com/resources/products/fundamentals/mongodb-connection-string).
To create the destination connector:
1. On the sidebar, click **Connectors**.
2. Click **Destinations**.
3. Cick **New** or **Create Connector**.
4. Give the connector some unique **Name**.
5. In the **Provider** area, click **MongoDB**.
6. Click **Continue**.
7. Follow the on-screen instructions to fill in the fields as described later on this page.
8. Click **Save and Test**.
Fill in the following fields:
* **Name** (*required*): A unique name for this connector.
* **Database** (*required*): The name of the database on the instance.
* **Collection** (*required*): The name of the collection within the database.
* **Connection String** (*required*): The MongoDB instance connection string.
## Learn more
* [How to go from S3 to MongoDB with no code using Unstructured](https://unstructured.io/blog/how-to-go-from-s3-to-mongodb-with-no-code-using-unstructured)