> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/data-quality-tools.md).

# Data quality tools

A data quality or data governance tool is software or a platform designed to assess, monitor, and improve the quality of data within an organization. It helps identify data issues, inconsistencies, errors, and anomalies that may impact data integrity, accuracy, completeness, consistency, and reliability. Data quality tools provide various functionalities and features to ensure that data meets predefined quality standards.

Secoda currently integrates with the following Data Quality tools:

{% content-ref url="/pages/gFdHCFYxMuUA2OAHbrta" %}
[Cyera](/integrations/data-quality-tools/cyera.md)
{% endcontent-ref %}

{% content-ref url="/pages/lR22gJUm3sxkI25Byw3X" %}
[Dataplex](/integrations/data-quality-tools/dataplex.md)
{% endcontent-ref %}

{% content-ref url="/pages/rXrKDbIv4tZi4wOH6XYe" %}
[Great Expectations](/integrations/data-quality-tools/great-expectations-integration.md)
{% endcontent-ref %}

{% content-ref url="/pages/LgMBfrebOxnZ66pfGH1N" %}
[Monte Carlo](/integrations/data-quality-tools/monte-carlo.md)
{% endcontent-ref %}

{% content-ref url="/pages/GmqXmnFsNZm1jbXEUi8q" %}
[Soda](/integrations/data-quality-tools/soda.md)
{% endcontent-ref %}

{% hint style="info" %}
Don't see an integration for a tool you use? Message us on Slack or email us at <support@secoda.co> and we'll add it to the roadmap.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.secoda.co/integrations/data-quality-tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.