Integration · Data quality
Great Expectations + OrchestrAI
Catalog exported 2026-09-02 · Great Expectations website
Run Great Expectations checkpoints and validations from chat and read the results and Data Docs.
OrchestrAI exposes 8 Great Expectations operations: 8 are low-risk (read-only or low-impact).
What teams use it for
Data quality owners use OrchestrAI to run a checkpoint after a load, read the validation result, and rebuild Data Docs so stakeholders see the outcome. It can also create an expectation suite and list existing suites and results. Every Great Expectations operation is rated low risk, so none of them waits for confirmation. There is no operation to delete a suite or edit individual expectations inside one, so suite maintenance happens in your GX project files or the GX Cloud UI.
Every Great Expectations operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Build GX Data Docs |
Build data documentation | Low risk | No |
Create Expectation Suite |
Create expectation suite | Low risk | No |
Get Expectation Suite |
Get expectation suite details | Low risk | No |
Get Validation Result |
Get validation result by ID | Low risk | No |
List Expectation Suites |
List expectation suites | Low risk | No |
List Validation Results |
List validation results | Low risk | No |
Run GX Checkpoint |
Run a checkpoint | Low risk | No |
Run GX Validation |
Run validation on data | Low risk | No |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
What you connect
A Great Expectations credential (stored as great_expectations).
Connected-service tokens are envelope-encrypted with a per-record key wrapped by a cloud KMS.
Prompts that work
- Run the Great Expectations checkpoint orders_daily and tell me which expectations failed
- Create an expectation suite named customers_raw_suite for the customers_raw asset
- Rebuild Data Docs and list the validation results from the last run
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Why are Great Expectations operations all low risk in OrchestrAI?
- Because they validate data and write results or documentation rather than changing the data itself. Even creating a suite adds a definition without altering any table.
- Can OrchestrAI delete a Great Expectations suite?
- No. Suites can be created, listed, and read, but there is no delete or per-expectation edit operation.
- How does OrchestrAI authenticate to Great Expectations?
- You add a Great Expectations credential once in the connections screen. It is envelope-encrypted with a per-record key wrapped by a cloud KMS and is only decrypted inside the run that needs it.
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.