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 get your Unstructured API key. To learn how, watch this 40-second how-to video.
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 Workflow Endpoint quickstart, go directly to the quickstart notebook, or watch the two 4-minute video tutorials for the Unstructured Python SDK.
You can also create destination connectors with the Unstructured user interface (UI). 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:
A bucket, scope, and collection on the cluster.
The cluster’s public connection string.
Incoming IP address allowance for the cluster.
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.
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 a Couchbase destination connector, see the following examples.
Replace the preceding placeholders as follows:
<name>
(required) - A unique name for this connector.<username>
(required) - The username for the Couchbase server.<bucket>
(required) - The name of the bucket in the Couchbase server.<connection-string>
(required) - The connection string for the Couchbase server.<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.<password>
(required) - The password for the Couchbase server.<batch-size>
- The maximum number of records to transmit per batch. The default is 50
if not otherwise specified.<collection-id>
(source connector only) - The name of the collection field that contains the document ID. The default is id
if not otherwise specified.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 get your Unstructured API key. To learn how, watch this 40-second how-to video.
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 Workflow Endpoint quickstart, go directly to the quickstart notebook, or watch the two 4-minute video tutorials for the Unstructured Python SDK.
You can also create destination connectors with the Unstructured user interface (UI). 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:
A bucket, scope, and collection on the cluster.
The cluster’s public connection string.
Incoming IP address allowance for the cluster.
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.
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 a Couchbase destination connector, see the following examples.
Replace the preceding placeholders as follows:
<name>
(required) - A unique name for this connector.<username>
(required) - The username for the Couchbase server.<bucket>
(required) - The name of the bucket in the Couchbase server.<connection-string>
(required) - The connection string for the Couchbase server.<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.<password>
(required) - The password for the Couchbase server.<batch-size>
- The maximum number of records to transmit per batch. The default is 50
if not otherwise specified.<collection-id>
(source connector only) - The name of the collection field that contains the document ID. The default is id
if not otherwise specified.