Flow Studio
Entities Capability Overview
Reading, creating, updating, and querying business entity records from within workflow nodes — the entity CRUD pattern, schema resolution, and tenant-scoped data isolation.
What are Entities?
Entities are structured business records — employees, customers, invoices, expense reports, assets. The Entities capability exposes CRUD operations on these records as workflow nodes, so workflows can read existing data, create new records, and update state as part of a business process.
Available Entity Nodes
| Node Type | Operation | Output |
|---|---|---|
EntityReadNode | Read one entity by ID | { entityId, entityType, data: {...} } |
EntityCreateNode | Create a new entity | { entityId, entityType, data: {...} } |
EntityUpdateNode | Patch an existing entity | { entityId, entityType, data: {...}, version } |
EntityQueryNode | Query entities with filter + pagination | { items: [...], totalCount, page, pageSize } |
Entity Type System
Each entity operation specifies an entityType string key. The IEntitySchemaRegistry resolves this to the correct service, table, and field schema at runtime. Adding a new entity type is a registry registration — no code changes to executors.
Access Pattern
// Read entity output — field access:
$output.fetchInvoice.data.invoiceNumber
$output.fetchInvoice.data.lineItems[0].amount
$output.fetchEmployee.data.email
// Create entity output — get new ID:
$output.createExpense.entityId
// Query output — iterate results:
$output.searchInvoices.items // array
$output.searchInvoices.totalCount
Tenant isolation: All entity operations are automatically scoped to the execution's tenant. The
IEntityClient enforces this — no node configuration can override it. Cross-tenant entity access is not possible.