Glossary · Workflow design
JSON schema
Also called: JSON Schema validation, schema
JSON Schema is a standard vocabulary for describing what a JSON document must look like (which fields are required, their types, formats, allowed values and ranges) so data can be validated automatically.
A schema is a contract. This one says an invoice must have a vendor, a positive total and an ISO date:
{
"type": "object",
"required": ["vendor", "total", "due_date"],
"properties": {
"vendor": { "type": "string", "minLength": 1 },
"total": { "type": "number", "exclusiveMinimum": 0 },
"due_date": { "type": "string", "format": "date" },
"po_number": { "type": "string" }
}
}A validator compares data against it and returns either "valid" or a list of exactly what's wrong.
Where it earns its keep in automation
- After AI steps. Language models are good at following a format and occasionally bad at it. A schema check turns "occasionally" into a routed exception instead of a corrupted record. See structured output.
- At webhook boundaries. Validate incoming payloads before anything acts on them; a sender's format change becomes a clear failure, not silent bad data.
- Between workflows. A sub-workflow's inputs are an API contract; a schema documents and enforces it.
Keep schemas honest
Only mark fields required if the downstream step truly needs them. Over-strict schemas push people to make models invent values, which is worse than an empty field.
In Fluxo Flow
The Validator node checks data against simple rules ("email exists", "amount greater than 0") or a JSON schema, then routes the run to a pass or fail branch. Put it right after AI steps and right before actions that write to other systems.
Read next
Related terms
- Structured outputStructured output is a model response in a predefined, machine-readable format, typically a JSON object matching a schema, so the next steps of a workflow can use the fields directly instead of parsing prose.
- AI guardrailsAI guardrails are automated checks placed before or after a model call that block, correct or route away inputs and outputs that break your rules, such as banned content, leaked data or invalid formats.
- Sub-workflowA sub-workflow is a workflow that another workflow calls as one of its steps, passing data in and getting a result back, so shared logic is built once and reused.
- Lead routingLead routing is the process of automatically assigning each new lead to the right salesperson, team or nurture track based on rules such as territory, company size, product interest, score or round-robin rotation.
- iPaaSiPaaS, or integration platform as a service, is cloud-hosted software that connects applications and data sources and automates processes between them, without the buyer running integration servers.