# Extensions

### Go beyond observability

Once Woven is watching your repositories, you can extend it with deeper automation and governance workflows.<br>

> Extensions help teams move from *seeing* changes to *acting* on them — automatically.

***

#### 🟣 Post-Merge Automations

Keep your data stack in sync after schema changes land.\
Examples include updating replication configs (e.g., Fivetran, Snowflake) or refreshing dbt models and metadata.

#### 🔒 Pre-Merge Controls

Add intelligent checks in pull requests — like privacy tagging or compliance validation — before changes merge.

***

Both extensions rely on **metadata and ownership context** collected through your existing repositories and configurations.

They’re typically tailored to each environment, so we’ll help you get it right.

***

### Next Steps

Want to enable extensions?<br>

Reach out to the Woven team — we’ll walk you through setup and configuration.

[📅 **Schedule a setup session →**](/docs/resources/support.md)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.woven.dev/docs/getting-started/extensions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.