Forms and server workflows New

Build a form from blocks, then let the server send the email, save the message or call a web service.

A Form block holds anything (columns, text, a Steps block) and the field blocks you drag into it: text, email, phone, web address, number, date, time, long text, a dropdown, choice buttons, a tick box and a Send button. The browser checks the fields and the server checks them again, keeping only the fields the form declares.

Workflows can also run on the server. The server actions are Send an email (to the site, to the address of a role, or back to the visitor, with values such as {field:email} in the subject and message), Save as a record (into the built-in Submissions inbox, or into a VX content type, always as pending or draft, never published), Add a note to the run log, and Send to a web service (Slack, Discord, or any address that takes JSON). Conditions on the server can look at a form value, who is signed in, an address parameter or cookie, or the day and date.

Safety needs nothing to switch on: the server runs only workflows that are saved on the page, the browser never sends an action or a recipient, a hidden field and a minimum time catch bots, and each workflow can have limits. Only administrators, plus the users and roles you choose, may change server actions. Test a workflow without sending anything, and see recent runs with the reason a run failed. Workflows that belong to no page start when someone registers or signs in, a post is published, a comment is posted or at an hour of the day.

Not included yet: delays, services beyond those above (Mailchimp and the like), file uploads in forms, and forms generated from a VX field set. A form needs JavaScript.

More features

New

Visual editing

Steps block

How it works, timelines, order status and click-through steps in one block.

Data binding

Display conditions

Show a block only when a field has a value, or hide it on a device.

New

Headless publishing

Headless publishing

Edit in WordPress. Serve the same pages from a separate front end.

Design the page. Keep the data.

Drag, bind, publish. When your VX data changes, the page follows, on WordPress or on a headless front end.

Get VX Editor Email us