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, 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 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 Astra DB. The requirements are as follows.
  • An Astra account. Create or sign in to an Astra account.
  • A database in the Astra account. Create a database in an account.
  • An application token for the database. Create a database application token.
  • A namespace in the database. Create a namespace in a database.
  • A collection in the namespace. Create a collection in a namespace. An existing collection is not required. At runtime, the collection behavior is as follows: For the Unstructured UI and Unstructured API:
    • If an existing collection name is specified, and Unstructured generates embeddings, but the number of dimensions that are generated does not match the existing collection’s embedding settings, the run will fail. You must change your Unstructured embedding settings or your existing collection’s embedding settings to match, and try the run again.
    • If a collection name is not specified, Unstructured creates a new collection in your namespace. If Unstructured generates embeddings, the new collections’s name will be u<short-workflow-id>_<short-embedding-model-name>_<number-of-dimensions>. If Unstructured does not generate embeddings, the new collections’s name will be u<short-workflow-id.
    For Unstructured Ingest:
    • If an existing collection name is specified, and Unstructured generates embeddings, but the number of dimensions that are generated does not match the existing collection’s embedding settings, the run will fail. You must change your Unstructured embedding settings or your existing collections’s embedding settings to match, and try the run again.
    • If a collection name is not specified, Unstructured creates a new collection in your Pinecone account. The new collection’s name will be unstructuredautocreated.
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 Astra DB.
  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.
  • Collection Name: The name of the collection in the namespace. If no value is provided, see the beginning of this article for the behavior at run time.
  • Keyspace (required): The name of the keyspace in the collection.
  • Batch Size: The maximum number of records per batch. The default is 20 if not otherwise specified.
  • Flatten Metadata: Check this box to flatten the metadata into each record. Specifically, when flattened, the metadata key values are brought to the top level of the element, and the metadata key itself is removed. By default, the metadata is not flattened.
  • API Endpoint (required): The database’s associated API endpoint.
  • Token (required): The application token for the database.