API: Local source/destination connectors - how-to for multiple files, add connector overview pages (#540)

Author: Paul-Cornell

api-reference/workflow/destinations/local.mdx

@@ -0,0 +1,15 @@
+---
+title: Local
+---
+
+Send processed data from Unstructured to local storage.
+
+This local destination connector is supported only for REST API clients such as `curl` and Postman. It is currently not supported by the Unstructured user interface (UI) or the Unstructured Python SDK.
+
+The local destination connector works only with the [local source connector](/api-reference/workflow/sources/local). You cannot use the local destination connector with any other source connector.
+
+For details, see the following:
+
+1. [Create a workflow](/api-reference/workflow/workflows#create-a-workflow) that uses a local destination and local source.
+2. [Run a workflow as a job](/api-reference/workflow/overview#run-a-workflow) that uses a local destination and local source.
+3. [Download a processed local file from the workflow's completed job run](/api-reference/workflow/overview#download-a-processed-local-file-from-a-job).

api-reference/workflow/destinations/overview.mdx

@@ -31,6 +31,7 @@ For the list of specific settings, see:
 - [Elasticsearch](/api-reference/workflow/destinations/elasticsearch) (`ELASTICSEARCH` for the Python SDK or `elasticsearch` for `curl` or Postman)
 - [Google Cloud Storage](/api-reference/workflow/destinations/google-cloud) (`GCS` for the Python SDK or `gcs` for `curl` or Postman)
 - [Kafka](/api-reference/workflow/destinations/kafka) (`KAFKA_CLOUD` for the Python SDK or `kafka-cloud` for `curl` or Postman)
+- [Local](/api-reference/workflow/destinations/local) (Supported only for `curl` or Postman)
 - [Milvus](/api-reference/workflow/destinations/milvus) (`MILVUS` for the Python SDK or `milvus` for `curl` or Postman)
 - [MongoDB](/api-reference/workflow/destinations/mongodb) (`MONGODB` for the Python SDK or `mongodb` for `curl` or Postman)
 - [MotherDuck](/api-reference/workflow/destinations/motherduck) (`MOTHERDUCK` for the Python SDK or `motherduck` for `curl` or Postman)

api-reference/workflow/overview.mdx

@@ -1760,15 +1760,18 @@ the `POST` method to call the `/workflows/<workflow-id>/run` endpoint (for `curl
         - `<filename.extension>` with the filename of the local file to upload.
         - `<local-file-media-type>` with the local file's media type. For a list of available media types, such as `application/pdf`, see [Media Types](https://www.iana.org/assignments/media-types/media-types.xhtml).
 
+        To upload multiple files, add additional `--form` entries, one per file.
+
         ```bash
         curl --request 'POST' --location \
         "$UNSTRUCTURED_API_URL/workflows/<workflow-id>/run" \
         --header 'accept: application/json' \
         --header "unstructured-api-key: $UNSTRUCTURED_API_KEY" \
-        --form "input_files=@</full/path/to/local/filename.extension>" \
-        --form "filename=<filename.extension>" \
-        --form "type=<local-file-media-type>" \
+        --form "input_files=@</full/path/to/local/filename.extension>;filename=<filename.extension>;type=<local-file-media-type>" \
+        --form "input_files=@</full/path/to/local/filename.extension>;filename=<filename.extension>;type=<local-file-media-type>" # For each additional file to be uploaded.
         ```
+
+        To access the processed files' data, [download a processed local file](#download-a-processed-local-file-from-a-job) from the workflow's job run.
     </Accordion>
     <Accordion title="Postman (remote source and remote destination)">
         1. In the method drop-down list, select **POST**.
@@ -1810,12 +1813,24 @@ the `POST` method to call the `/workflows/<workflow-id>/run` endpoint (for `curl
         4. On the **Body** tab, select **form-data**, and specify the settings for the workflow run:
 
             - **Key**: `input_files`, **File**, **Value**: Click the **Value** box, then click **New file from local machine**, and select the file to upload.
+
+              To upload multiple files, add additional `input_files` entries after this one, one entry per additional file to upload.
+
             - **Key**: `filename`, **Text**, **Value**: Type the name of the file that you just uploaded.
+
+              To upload multiple files, add additional `filename` entries after this one, one entry per additional file to upload. Make sure the order of these 
+              `filename` entries matches the order of the `input_files` entries, respectively.
+
             - **Key**: `type`, **Text**, **Value**: `<local-file-media-type>`
 
+              To upload multiple files, add additional `type` entries after this one, one entry per additional file to upload. Make sure the order of these 
+              `type` entries matches the order of the `input_files` entries, respectively.
+
             For a list of available media types, such as `application/pdf`, see [Media Types](https://www.iana.org/assignments/media-types/media-types.xhtml).
 
         5. Click **Send**.
+
+        To access the processed files' data, [download a processed local file](#download-a-processed-local-file-from-a-job) from the workflow's job run.
     </Accordion>
 </AccordionGroup>
 

api-reference/workflow/sources/local.mdx

@@ -0,0 +1,15 @@
+---
+title: Local
+---
+
+Ingest your files into Unstructured from local storage.
+
+This local source connector is supported only for REST API clients such as `curl` and Postman. It is currently not supported by the Unstructured user interface (UI) or the Unstructured Python SDK.
+
+The local source connector works only with the [local destination connector](/api-reference/workflow/destinations/local). You cannot use the local source connector with any other destination connector.
+
+For details, see the following:
+
+1. [Create a workflow](/api-reference/workflow/workflows#create-a-workflow) that uses a local source and local destination.
+2. [Run a workflow as a job](/api-reference/workflow/overview#run-a-workflow) that uses a local source and local destination.
+3. [Download a processed local file from the workflow's completed job run](/api-reference/workflow/overview#download-a-processed-local-file-from-a-job).

api-reference/workflow/sources/overview.mdx

@@ -32,6 +32,7 @@ For the list of specific settings, see:
 - [Google Cloud Storage](/api-reference/workflow/sources/google-cloud) (`GCS` for the Python SDK or `gcs` for `curl` and Postman)
 - [Google Drive](/api-reference/workflow/sources/google-drive) (`GOOGLE_DRIVE` for the Python SDK or `google_drive` for `curl` and Postman)
 - [Kafka](/api-reference/workflow/sources/kafka) (`KAFKA_CLOUD` for the Python SDK or `kafka-cloud` for `curl` and Postman)
+- [Local](/api-reference/workflow/sources/local) (Supported only for `curl` and Postman)
 - [MongoDB](/api-reference/workflow/sources/mongodb) (`MONGODB` for the Python SDK or `mongodb` for `curl` and Postman)
 - [OneDrive](/api-reference/workflow/sources/onedrive) (`ONEDRIVE` for the Python SDK or `onedrive` for `curl` and Postman)
 - [Outlook](/api-reference/workflow/sources/outlook) (`OUTLOOK` for the Python SDK or `outlook` for `curl` and Postman)

mint.json

@@ -281,6 +281,7 @@
               "api-reference/workflow/sources/google-cloud",
               "api-reference/workflow/sources/google-drive",
               "api-reference/workflow/sources/kafka",
+              "api-reference/workflow/sources/local",
               "api-reference/workflow/sources/mongodb",
               "api-reference/workflow/sources/onedrive",
               "api-reference/workflow/sources/outlook",
@@ -304,6 +305,7 @@
               "api-reference/workflow/destinations/elasticsearch",
               "api-reference/workflow/destinations/google-cloud",
               "api-reference/workflow/destinations/kafka",
+              "api-reference/workflow/destinations/local",
               "api-reference/workflow/destinations/milvus",
               "api-reference/workflow/destinations/mongodb",
               "api-reference/workflow/destinations/motherduck",