Approval before action
The validator refuses any workflow where a Send or CRM write can be reached without passing the approved output of a Human approval step. The server re-checks this on every run.
Security
This page lists the controls that exist in this demo's code today, and is plain about what does not exist.
The validator refuses any workflow where a Send or CRM write can be reached without passing the approved output of a Human approval step. The server re-checks this on every run.
Steps are a fixed list of types with fixed operations. Imported JSON is checked against a schema; unknown step types are refused and nothing in a file is ever run as code.
The engine never fetches a URL, never calls an AI provider and never sends a message. Sends are recorded as simulated.
Classify steps flag instruction-like text such as "ignore previous instructions" and carry on with their own rules.
Requests over 96 KB, more than 40 steps, more than 80 connections or 30 record fields are refused. Loops are impossible, so every run ends.
Each server instance allows about 60 demo requests per minute per address.
Runs are computed and returned. The server keeps the last 50 runs in memory for a short time and nothing on disk. Your edits live in your own browser storage.
An approval decision must come with the original run inputs. The server checks they hash to the same run id before it continues, so a run cannot be resumed with swapped inputs.