Guide

Build

Data Models

1 min readOpen in Neblex

Data Models (canonical models) describe one shared business shape, such as Customer or Order, that many systems map to and from. Keep the core of a flow stable while adapters at the edges change.

  • Design: in the visual designer add fields, nested records and lists of records. Each field has a type (Text, Number, Integer, True / false, Object, Array, Null or an advanced union), whether it is required, a description, a format (such as email, date-time or uuid) and optional allowed values. View it as JSON, as JSON Schema, or as a live example record.
  • Check a schema: paste a candidate schema and Run check. Each difference is marked Breaking or Compatible (field added or removed, type changed, required added or removed).
  • Use it: in Map fields or Transform items choose it as the Output contract so the step's result is checked against the model. Models are not applied to flows automatically.
  • Lifecycle: version history, and Trash with restore.
Data Models.
Data Models.
  1. Shared business shapes and compatibility checks.