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, 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 MotherDuck.
The requirements are as follows.
A MotherDuck access token for the account.
A database in the account.
You can run commands to manage MotherDuck databases, schemas, tables, and more in the MotherDuck UI or for example by connecting to MotherDuck with the DuckDB CLI.
A schema in the target database.
You can list available schemas and their parent catalogs by running the following command in the MotherDuck UI or the DuckDB CLI:
The MotherDuck connector uses the default schema name of main
if not otherwise specified.
A table in the target schema.
You can list available tables in a schema by running the following commands in the MotherDuck UI or the DuckDB CLI, replacing the target catalog and schema names:
The MotherDuck connector uses the default table name of elements
if not otherwise specified.
For maximum compatibility, Unstructured recommends the following table schema:
You can list the schema of a table by running the following commands in the MotherDuck UI or the DuckDB CLI, replacing the target catalog, schema, and table names:
To create the destination connector:
Fill in the following fields:
elements
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 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 MotherDuck.
The requirements are as follows.
A MotherDuck access token for the account.
A database in the account.
You can run commands to manage MotherDuck databases, schemas, tables, and more in the MotherDuck UI or for example by connecting to MotherDuck with the DuckDB CLI.
A schema in the target database.
You can list available schemas and their parent catalogs by running the following command in the MotherDuck UI or the DuckDB CLI:
The MotherDuck connector uses the default schema name of main
if not otherwise specified.
A table in the target schema.
You can list available tables in a schema by running the following commands in the MotherDuck UI or the DuckDB CLI, replacing the target catalog and schema names:
The MotherDuck connector uses the default table name of elements
if not otherwise specified.
For maximum compatibility, Unstructured recommends the following table schema:
You can list the schema of a table by running the following commands in the MotherDuck UI or the DuckDB CLI, replacing the target catalog, schema, and table names:
To create the destination connector:
Fill in the following fields:
elements
if not otherwise specified.