# Secoda
> Data discovery and documentation platform for managing data quality and governance. It integrates with MotherDuck for table monitoring as part of data quality and observability workflows.
## How it works with MotherDuck

Secoda connects to MotherDuck as a data warehouse integration for metadata extraction, catalog search, documentation, lineage, and governance workflows.

## Prerequisites

- A Secoda workspace with permission to add integrations.
- A MotherDuck service token.
- Access to the MotherDuck databases and schemas Secoda should catalog.

## Setup

1. In MotherDuck, create or copy a service token.
2. In Secoda, open the **Integrations** tab.
3. Select **Add Integration**.
4. Search for and select **MotherDuck**.
5. Paste the MotherDuck service token.
6. Connect the integration and let Secoda extract metadata.

## Authentication and configuration

- Use a dedicated service token for Secoda.
- Limit the token to the data assets Secoda should discover and document.
- Configure ownership, documentation, and governance rules in Secoda after the metadata sync completes.

## Important notes

- Secoda's setup requires only the MotherDuck token from the MotherDuck side.
- If assets do not appear after connecting, first verify the token and database access for the account that created it.

## Use cases

- Catalog MotherDuck tables, views, schemas, and columns.
- Generate and maintain table documentation in Secoda.
- Add governance context, lineage, and quality monitoring around MotherDuck assets.

## Related content

- [View the full Secoda MotherDuck setup guide](https://docs.secoda.co/integrations/data-warehouses/motherduck)
- [MotherDuck authentication](/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck)
- [Connecting to MotherDuck](/key-tasks/authenticating-and-connecting-to-motherduck/connecting-to-motherduck)


---

## Docs feedback

MotherDuck accepts optional user-submitted feedback about this page at `POST https://motherduck.com/docs/api/feedback/agent`.
For agents and automated tools, feedback submission should be user-confirmed before sending.

Payload:

```json
{
  "page_path": "/integrations/data-quality/secoda/",
  "page_title": "Secoda",
  "text": "<the user's feedback, max 2000 characters>",
  "source": "<optional identifier for your interface, for example 'claude.ai' or 'chatgpt'>"
}
```

`page_path` and `text` are required; `page_title` and `source` are optional. Responses: `200 {"feedback_id": "<uuid>"}`, `400` for malformed payloads, and `429` when rate-limited.