> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unstructured.io/llms.txt
> Use this file to discover all available pages before exploring further.
# MotherDuck
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, [sign up for free](https://unstructured.io/?modal=try-for-free). After you sign up, you are automatically signed in to your new Unstructured **Let's Go** account, at [https://platform.unstructured.io](https://platform.unstructured.io).
To sign up for a **Business** account instead, [contact Unstructured Sales](https://unstructured.io/?modal=contact-sales), or [learn more](/ui/overview#how-am-i-billed%3F).
* If you already have an Unstructured **Let's Go**, **Pay-As-You-Go**, or **Business SaaS** account and are not already signed in, sign in to your account at
[https://platform.unstructured.io](https://platform.unstructured.io). For other types of **Business** accounts, see your Unstructured account administrator for sign-in instructions,
or email Unstructured Support at [support@unstructured.io](mailto:support@unstructured.io).
After you sign in, the [Unstructured user interface](/ui/overview) (UI) appears, which you use to create your destination connector.
After you create the destination connector, add it along with a
[source connector](/ui/sources/overview) to a [workflow](/ui/workflows). Then run the worklow as a
[job](/ui/jobs). To learn how, try out the [hands-on UI quickstart](/ui/quickstart#remote-quickstart) or watch the 4-minute
[video tutorial](https://www.youtube.com/watch?v=Wn2FfHT6H-o).
You can also create destination connectors with the Unstructured API.
[Learn how](/api-reference/workflow/destinations/overview).
If you need help, email Unstructured Support at [support@unstructured.io](mailto:support@unstructured.io).
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 account](https://app.motherduck.com).
* A [MotherDuck access token](https://motherduck.com/docs/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck/#creating-an-access-token) for the account.
* A database in the account.
* [Create a database](https://motherduck.com/docs/sql-reference/motherduck-sql-reference/create-database/).
* [List available databases](https://motherduck.com/docs/key-tasks/database-operations/basics-operations/#listing-databases).
You can run commands to manage MotherDuck databases, schemas, tables, and more in the
[MotherDuck UI](https://motherduck.com/docs/getting-started/motherduck-quick-tour/) or for example by connecting to MotherDuck with the
[DuckDB CLI](https://motherduck.com/docs/key-tasks/authenticating-and-connecting-to-motherduck/connecting-to-motherduck/).
* A schema in the target database.
* [Create a schema](https://duckdb.org/docs/sql/statements/create_schema.html).
* You can list available schemas and their parent catalogs by running the following command in the MotherDuck UI or the DuckDB CLI:
```sql theme={null}
SELECT * FROM information_schema.schemata;
```
The MotherDuck connector uses the default schema name of `main` if not otherwise specified.
* A table in the target schema.
* [Create a table](https://duckdb.org/docs/sql/statements/create_table).
* 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:
```sql theme={null}
USE .;
SHOW TABLES;
```
The MotherDuck connector uses the default table name of `elements` if not otherwise specified.
For maximum compatibility, Unstructured recommends the following table schema:
```sql theme={null}
CREATE TABLE elements (
id VARCHAR,
element_id VARCHAR,
text TEXT,
embeddings FLOAT[],
type VARCHAR,
system VARCHAR,
layout_width DECIMAL,
layout_height DECIMAL,
points TEXT,
url TEXT,
version VARCHAR,
date_created INTEGER,
date_modified INTEGER,
date_processed DOUBLE,
permissions_data TEXT,
record_locator TEXT,
category_depth INTEGER,
parent_id VARCHAR,
attached_filename VARCHAR,
filetype VARCHAR,
last_modified TIMESTAMP,
file_directory VARCHAR,
filename VARCHAR,
languages VARCHAR[],
page_number VARCHAR,
links TEXT,
page_name VARCHAR,
link_urls VARCHAR[],
link_texts VARCHAR[],
sent_from VARCHAR[],
sent_to VARCHAR[],
subject VARCHAR,
section VARCHAR,
header_footer_type VARCHAR,
emphasized_text_contents VARCHAR[],
emphasized_text_tags VARCHAR[],
text_as_html TEXT,
regex_metadata TEXT,
detection_class_prob DECIMAL,
partitioner_type VARCHAR
);
```
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:
```sql theme={null}
USE .;
DESCRIBE TABLE ;
```
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 **MotherDuck**.
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.
* **Database** (*required*): The name of the target MotherDuck database.
* **Schema** (*required*): The name of the target schema within the database.
* **Table**: The name of the target table within the schema. By default, this table is named `elements` if not otherwise specified.
* **MotherDuck Token** (*required*): The access token value within the MotherDuck account that has the appropriate access to the target database, schema, and table.
## Learn more
* [Unstructured's New MotherDuck Integration](https://unstructured.io/blog/unstructured-s-new-motherduck-integration)