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

Before you can create a destination connector, you must first sign up for Unstructured. After you sign up, the Unstructured user interface (UI) appears, which you use to create the destination connector.

After you create the destination connector, add it along with a source 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 destination 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 destination connector! Keep reading to learn how.

Send processed data from Unstructured to Couchbase.

The requirements are as follows.

For Couchbase Capella, you will need:

For a local Couchbase server, you will need:

To learn more about how to set up a Couchbase cluster and play with data, refer to this tutorial.

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 Couchbase.
  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.
  • Bucket (required): The name of the bucket to connect to on the cluster.
  • Connection string (required): The connection string for the Couchbase cluster.
  • Scope: The name of the scope in the bucket. The default is _default if not otherwise specified.
  • Collection: The name of the collection in the scope. The default is _default if not otherwise specified.
  • Batch Size: The maximum number of documents per transmitted batch. The default is 50 if not otherwise specified.
  • Collection ID key (source connector only): The name of the collection field that contains the document ID. The default is id if not otherwise specified
  • Username (required): The cluster access name (username) that has access to the cluster.
  • Password (required): The password for the corresponding username.