- Introduction
- Getting started
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Opening the modeling canvas
- Modeling your process
- Aligning and connecting BPMN elements
- Autopilot for Maestro (Preview)
- Process Repository
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Debugging
- Simulating
- Evaluations (Preview)
- Common implementation scenarios
- Building with Maestro Case
- Introduction to Maestro Case
- Maestro BPMN vs. Maestro Case: when to use case management
- The Maestro Case lifecycle: from event trigger to app experience
- Build your first case with Maestro Case
- Build a Maestro Case with a coding agent (preview)
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Exit rules and early stage termination
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Case Manager input and output contract
- Maestro Case component dictionary
- Building with Maestro Flow
- Maestro Automate
- Integrations
- Operating
- Monitoring
- Optimizing
- Reference information
Create entity record node for writing a new record to a Data Fabric entity from a Flow, without an Integration Service connection.
Creates a new record in a Data Fabric entity. This is a native Flow node — it doesn't require an Integration Service (IS) connection. It works with existing entities from the Data Fabric platform — both tenant and folder entities — and with entities defined in a VS Code solution. Refer to Entities in VS Code.
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 — 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.