Schemas

Schemas are reusable JSON Schema definitions managed in the Requence UI. Instead of defining input and output shapes inline on every node, you create a schema once and reference it by name wherever it is needed.

Schemas serve two purposes:

• Validation — when a task is started, its input payload is validated against the schema defined on the task template’s entry node. The same applies to exit nodes, ensuring output conforms to the expected shape.
• Type Safety — Requence derives TypeScript types from your schemas and provides them to logic nodes and services via the context API. This means you get autocomplete and compile-time checks while writing transformation logic.

Schemas can reference other schemas, forming a dependency graph that Requence tracks automatically. If a referenced schema is deleted or modified in a breaking way, every task template and service version that depends on it is flagged with a validation error.

Availability in Logic Nodes

When a task template uses schemas — for example on the entry node, exit nodes, through a service version, or via a sub task node — all of those schema types are automatically available inside logic nodes. This includes deeply referenced schemas: if a schema references another schema, and that schema references yet another, the entire dependency tree is resolved and made available as types in the logic node editor. You do not need to import or register them manually.