If you’re new to Unstructured, read this note first.

Before you can create a source connector, you must first sign in to your Unstructured account:

  • If you do not already have an Unstructured account, go to https://unstructured.io/contact and fill out the online form to indicate your interest.
  • If you already have an Unstructured account, sign in by using the URL of the sign in page that Unstructured provided to you when your Unstructured account was created. If you do not have this URL, contact Unstructured Sales at sales@unstructured.io.

After you sign in, the Unstructured user interface (UI) appears, which you use to create your source connector.

After you create the source connector, add it along with a destination connector to a workflow. Then run the worklow as a job. To learn how, try out the hands-on UI quickstart or watch the 4-minute video tutorial.

You can also create source connectors with the Unstructured API. Learn how.

If you need help, reach out to the community on Slack, or contact us directly.

You are now ready to start creating a source connector! Keep reading to learn how.

Ingest your files into Unstructured from 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.

  • A MongoDB Atlas cluster. Create a 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.

  • The cluster must be configured to allow IP address. Learn how.

    To get Unstructured’s IP address ranges, go to 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.

  • The database must have at least one user, and that user must have sufficient access to the database. Create a database user. Give the user database access.

  • The database must have at least one collection. 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:

    mongodb+srv://<db_user>:<db_password>@<host>/?retryWrites=true&w=majority&appName=<cluster>

    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.

To create the source connector:

  1. On the sidebar, click Connectors.
  2. Click Sources.
  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.