# Configure a Materialize Action

Source: https://userguide.qualytics.io/flows/actions/how-tos/operation/configure-a-materialize-action/

Add a Materialize action to copy container data from a source datastore to the enrichment destination automatically whenever the Flow's trigger activates.

> **Note: Permission Required**
>
> To edit and publish a Flow, you need the **Editor** team permission on every datastore it relates to. Admins are exempt. See [Flow Permissions](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/) for details.

> **Warning: Initialized datastores connected to an enrichment destination only**
>
> The **Datastore** dropdown only lists source datastores that are initialized and have an [enrichment destination](https://userguide.qualytics.io/source-datastore/enrichment-datastore/getting-started/) connected. A source datastore becomes initialized after successful **Sync**, **Profile**, and **Scan** runs. An enrichment datastore becomes initialized after Sync and Profile.

## Field reference

The **Materialize Settings** panel shows the following fields. They mirror the options of running the operation directly on the datastore.

> **Warning: Select the datastore first**
>
> The sections below live in the **Operation Configuration** stepper and stay disabled until a **Datastore** is selected. For [DFS datastores](https://userguide.qualytics.io/source-datastore/datastore/dfs/overview-of-a-dfs-datastore/), the **Select** step lists **File Patterns** instead of **Tables**.

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Datastore** | Yes | Option | The source datastore to materialize data from. |

### Select Containers

Choose which containers the materialize covers. The UI identifies them as tables for JDBC datastores and file patterns for DFS datastores. Picking one of the options is required to move to the next step, and **All** is preselected.

| Option | Description |
| --- | --- |
| **All** | Materializes every container, including ones created after the action is saved. |
| **Specific** | Materializes only the containers you pick from the list. |
| **Tag** | Automatically materializes the containers associated with the selected tags. |

> **Warning: A datastore with no tables**
>
> When the datastore has no tables, a warning above the options reads **No tables were found in this datastore. Run a Sync, or check the connection settings and permissions.** (on a DFS datastore it starts with **No file patterns were found**). Run a [Sync operation](https://userguide.qualytics.io/operations/sync/sync/) on the datastore first, or fix the connection settings or the database user's permissions so the Sync can see the tables.

### Read Settings

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Record Limit** | No | Number | The maximum number of records to materialize per container. Pick a preset (**1M**, **10M**, **100M**, or **All**) or type a custom value from 1 to 1,000,000,000. Defaults to **All**, which sets no limit. |
| **Reveal Masked Values** | No | Checkbox | Materializes masked field values as plain text. |

## Steps

**Step 1**: Navigate to the Flows page by clicking **Flows**  on the left side panel.

**Step 2**: On the **Definitions** tab, click the Flow. On its canvas, click the dashed **Action** placeholder after the trigger, or the **+** handle at the bottom edge of a node.

**Step 3**: In the **List of Actions** panel, pick the **Operation** category, then click **Materialize**. The **Materialize Settings** panel opens on the right-hand side.

**Step 4**: Fill in the fields.

**Step 5**: Click **Save**. The node shows a **CHANGED** badge and the **You have unpublished changes** banner appears on the canvas.

**Step 6**: Click **Publish**  to make the action live.

*Last updated: October 29, 2026.*
