# Create entity record

> Configure the Create entity record node to add a Data Fabric record, and read its output in later nodes.

Creates a new record in a Data Fabric entity. This is a native node. It doesn't need a connection. It works with existing entities from the Data Fabric platform, wherever they are stored, and with entities defined in a VS Code solution. [Entities in VS Code](/data-service/automation-cloud/latest/user-guide/entities-in-vs-code): how to define an entity in a VS Code solution.

![Create entity record node's Properties panel showing a Data Fabric entity picker and a Select fields checklist for choosing which fields to set on the new record.](https://dev-assets.cms.uipath.com/assets/images/maestro/node-create-entity-record-properties-797fe4b6.webp)

## Configuration

| Field | Required | Description |
|---|---|---|
| **Data Fabric entity** | Yes | The entity to create a record in. Select **Refresh schema** if the entity's fields changed since you added the node. |
| **Field values** | Yes | Select **+ Select fields** to choose which fields to set, then provide a value for each selected field. At least one field value is required. |

This node doesn't support the **Error handling** tab.

## Output

The node's output mirrors all of the entity's fields. The fields and types vary by entity and typically include the entity's standard system fields (such as **Id**, **CreateTime**, and **CreatedBy**) alongside your custom fields. Access them downstream as `$vars.<nodeId>.output.<fieldName>`.

### Live reference behavior

The output is a **live reference** to the created record, not a stored copy of the values you wrote. Every expression, condition, or script that reads it re-reads the record at that moment, so it reflects any later change, so no extra Query entity records node is needed. The **LIVE QUERY** chip in the schema tree marks outputs that behave this way.

For example, if this node creates a ticket with status `Open` and a later node sets that ticket to `Closed`, an expression reading `$vars.<nodeId>.output.Status` after that point returns `Closed`, not the `Open` value this node wrote.

Loop and data-transform collections are the exception. They read a snapshot of the record taken when the node ran.

## Next steps

- [Data Fabric entity nodes](data-fabric-entity-nodes.md): the other entity record nodes.
- [Node reference](node-reference.md): every node and how to configure it.
- [Community](community.md): ask questions and share workflows with other builders on the UiPath Forum.