Validation & Security

Schema, business-logic, semantic, security, integrity, and compliance validation nodes.

Overview

The Validation & Security group holds nodes that check upstream data before it is allowed to continue through the pipeline — catching bad shapes, broken business rules, security risks, or compliance issues early rather than letting them reach an Integration or Output node.

This group spans two underlying node categories: Validation and Security.

Nodes in This Group

Validation

Node	Description
Quality Check	Runs a general-purpose quality check against upstream data.
Schema Validation	Validates upstream data against a defined schema (e.g. from a Define Schema node).
Business Logic	Validates upstream data against custom business rules.
Semantic Validation	Uses an LLM to check whether upstream content is semantically correct or consistent.
Security Validation	Scans upstream data for security-relevant issues (e.g. injection patterns, unsafe content).
Integrity Check	Verifies upstream data has not been corrupted or truncated.
Compliance Validation	Checks upstream data against configured compliance rules.
Validate Rules	Runs a configurable set of validation rules against the upstream value.

Security

Node	Description
Security Protocol	Applies a configured security protocol (e.g. redaction, access check) to upstream data before it continues.

Usage Tips

Validate right after Data Sources

Place Schema Validation or Integrity Check immediately after a Data Sources node that reads from an external API or database — catching a malformed response early avoids confusing errors deeper in the pipeline.

Failed validation stops the branch

When a Validation node's check fails, the downstream branch does not execute. Pair validation nodes with a Condition or Manual Approval node if you want a fallback path instead of simply halting.

Frequently Asked Questions

What's the difference between Schema Validation and Business Logic?

Schema Validation checks the shape of the data (required fields, types). Business Logic checks rules specific to your domain (e.g. "order total must not exceed the customer's credit limit") that go beyond structural correctness.

Does Security Validation block malicious content automatically?

It flags content matching configured risk patterns and stops the branch from continuing; it does not silently sanitize or auto-correct the data. Use it alongside Security Protocol if you want data to be cleaned rather than simply blocked.