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: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, email Unstructured Support at support@unstructured.io.You are now ready to start creating a destination connector! Keep reading to learn how.
Send processed data from Unstructured to Pinecone. The following video shows how to fulfill the minimum set of Pinecone requirements: Here are some more details about the requirements:
  • A Pinecone account. Get an account.
  • A Pinecone API key. Get an API key.
  • A Pinecone serverless index. Create a serverless index. An existing index is not required. At runtime, the index behavior is as follows: For the Unstructured UI and Unstructured API:
    • If an existing index name is specified, and Unstructured generates embeddings, but the number of dimensions that are generated does not match the existing index’s embedding settings, the run will fail. You must change your Unstructured embedding settings or your existing index’s embedding settings to match, and try the run again.
    • If an index name is not specified, Unstructured creates a new index in your Pinecone account. If Unstructured generates embeddings, the new index’s name will be u<short-workflow-id>-<short-embedding-model-name>-<number-of-dimensions>. If Unstructured does not generate embeddings, the new index’s name will be u<short-workflow-id.
    For Unstructured Ingest:
    • If an existing index name is specified, and Unstructured generates embeddings, but the number of dimensions that are generated does not match the existing index’s embedding settings, the run will fail. You must change your Unstructured embedding settings or your existing index’s embedding settings to match, and try the run again.
    • If an index name is not specified, Unstructured creates a new index in your Pinecone account. The new index’s name will be unstructuredautocreated.
    If you create a new index or use an existing one, Unstructured recommends that all records in the target index 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 index or, in some cases, the operation could fail altogether.
  • Within a Pinecone serverless index, custom namespaces are supported but are not required.
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 Pinecone.
  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.
  • Index Name: The name of the index in the Pinecone database. If no value is provided, see the beginning of this article for the behavior at run time.
  • Namespace: The name of any custom namespace in the Pinecone index to upsert data into. If no value is provided, the default namespace of default will be used.
  • Batch Size: The number of records to use in a single batch. The default is 50 if not otherwise specified.
  • API Key (required): The Pinecone API key.