> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/references/resources/vulcan/advanced-features.md).

# Advanced features

Advanced features that extend Vulcan beyond standard model definitions: macros, signals, custom materializations, and importing Snowflake semantic views.

Advanced features help you extend Vulcan beyond standard model definitions.

Use them when built-in behavior is close, but not enough.

## What this section covers

Use this section when you need to:

* make SQL more dynamic with macros
* delay model execution until external conditions are ready
* control how models materialize in the warehouse

## Quick selection guide

Start with **Macros** when you want reusable SQL patterns.

Use **Signals** when schedule timing depends on data readiness.

Use **Custom materializations** when built-in model kinds do not fit.

{% hint style="warning" %}
These features add flexibility, but they also add maintenance overhead. Use them only when the standard workflow is not enough.
{% endhint %}

## Choose a feature

<table data-view="cards"><thead><tr><th></th><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Macros</strong><br>Use variables, built-ins, and templating to generate reusable SQL.</td><td><a href="https://v2.dataos.info/references/resources/vulcan/advanced-features/macros.md">Macros</a></td></tr><tr><td><strong>Signals</strong><br>Add custom readiness checks before scheduled models run.</td><td><a href="https://v2.dataos.info/references/resources/vulcan/advanced-features/signals.md">Signals</a></td></tr><tr><td><strong>Custom materializations</strong><br>Define custom insert and lifecycle behavior for special execution patterns.</td><td><a href="https://v2.dataos.info/references/resources/vulcan/advanced-features/custom-materializations.md">Custom materializations</a></td></tr><tr><td><strong>Import Snowflake semantic views</strong><br>Import a Snowflake-native semantic view into a Vulcan project instead of writing YAML by hand.</td><td><a href="https://v2.dataos.info/references/resources/vulcan/advanced-features/import-snowflake-semantic-views.md">Import Snowflake semantic views</a></td></tr></tbody></table>

## When to use each feature

Quick criteria for picking between macros, signals, and custom materializations.

### Use macros when

* SQL repeats across multiple models
* values depend on execution context
* templating keeps logic clearer than copy-paste

### Use signals when

* upstream data arrives late or irregularly
* schedules alone are not enough
* model execution must wait for custom checks

### Use custom materializations when

* built-in kinds cannot express the write behavior
* the engine needs custom DDL or DML logic
* you are prepared to maintain Python extension code

## Best practices

Prefer built-in model kinds and scheduling first.

Keep macros small, predictable, and easy to test.

Use signals and custom materializations only for clear operational needs.


---

# 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://v2.dataos.info/references/resources/vulcan/advanced-features.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.
