What it does: Pick a trigger, add conditions, add steps. Nothing here is a JSON textarea any more: every trigger and every action draws its form from the params_schema it already declares, so each parameter is a labelled field with the right control. How to access: Flow Forge > Flows > Add new (form editor), or the canvas. Notes:

• Conditions are rows: field, operator, value. The operator list is read from the evaluator itself, together with each operator’s value arity (one value, a list, or none), so the dropdown can never offer an operator the engine does not implement.
• Next to each text field is an “Insert field” menu carrying the trigger’s {{event.*}} paths with a real example value from its sample payload.
• The three JSON textareas survive under an Advanced (JSON) toggle and still post the same three fields, so saving is unchanged.
• The builder refuses to draw what it cannot draw honestly. A key absent from the schema, a nested condition group, or an OR group on a site without the Pro add-on is detected on the server before a single control is rendered, and that panel opens as JSON with an explanation — otherwise the first keystroke would erase the half of the flow the form did not understand.
• {{event.*}} survives type coercion: an integer field holding a placeholder is not turned into 0, which is why numeric, URL and e-mail fields render as type="text" with an inputmode.
• Without JavaScript the screen degrades to the previous JSON editor; nothing is lost.
• The canvas node modal renders the same controls through the same shared component, so a parameter edited on the canvas is coerced exactly as it is in the form.
• Variables are interpolated with {{event.user.email}}-style placeholders drawn from the trigger payload. A flow is a draft until you activate it, and the version is recorded on every run.