Docs · Integrations

WS Form

Build and run WS Form with AI: forms and their JSON, fields, tabs and sections, the actions that fire on submit, submissions and exports, styles and templates.

WS Form is one of the plugins NIBWP turns into a set of typed, agent-callable tools. Activate WS Form, switch the integration on, and an agent can build and run your forms through the same secure MCP endpoint as everything else.

Building a form is structural work: fields in sections, sections in tabs, and then the part everyone forgets — the actions that decide whether a submission reaches anybody. A form without them collects data and notifies nobody, which looks like success until someone asks where the enquiries went.

TL;DR

Active plugin in, typed tools out. Forms and their whole JSON definition, fields, tabs and sections, the actions that fire on submit, submissions with their exports and notes, styles and templates — with every irreversible operation behind its own permission.

Your forms, programmable

Connecting WS Form to your agents changes what is possible with it:

  • Whole forms in one call — Read a working form as JSON, adapt it, and create the next one from that — faster and more correct than building field by field.
  • Actions covered — Email, webhooks and the rest. This is the part that decides whether a submission is acted on, and it is the part most automation skips.
  • The real layout tree — Fields live in sections, sections in tabs. Multi-step forms are just more than one tab.
  • Submissions and exports — List, read, star, mark read, change status, and export as rows or CSV with the headers WS Form itself would use.
  • Styles and templates — Style a form once and reuse it, or start from a template instead of an empty canvas.
  • Deletion kept apart — Every irreversible operation sits behind its own tool and asks for confirmation. Trashing does not, because putting something back should never be the harder option.

The tools

Fourteen abilities, grouped by what they touch:

ToolWhat it does
nibwp/wsform-infoVersion, edition, form and submission counts.
nibwp/wsform-formsList, create, clone, publish, draft, restore and count forms.
nibwp/wsform-jsonRead a whole form as JSON, or create and replace one from it.
nibwp/wsform-fieldsList, add, update, clone and delete fields, and list the field types.
nibwp/wsform-tabsThe top level of the layout — multi-step forms.
nibwp/wsform-sectionsThe sections that hold the fields.
nibwp/wsform-actionsWhat happens on submit: list, add, update and remove actions.
nibwp/wsform-submissionsList and read submissions, and change their state.
nibwp/wsform-exportExport submissions as rows or CSV, paginated.
nibwp/wsform-notesInternal notes on a submission.
nibwp/wsform-stylesCreate, update, publish and assign styles.
nibwp/wsform-templatesThe templates this install offers.
nibwp/wsform-configField types, data sources, frameworks and parse variables.
nibwp/wsform-deletePermanent deletion of forms, submissions and expired data.

Building a form that works

The order that avoids an empty shell:

  1. Start from something realwsform-templates, or read an existing form with wsform-json and adapt it.
  2. Check the vocabularywsform-config lists the field types this edition actually offers.
  3. Build the structure — Tabs, then sections, then fields — a field cannot exist without a section to live in.
  4. Add the actionswsform-actions. Without one, the form collects submissions and tells nobody.
  5. Style itwsform-styles, reusing a style the site already has where one fits.
  6. Check the submissionswsform-submissions and wsform-export once real entries arrive.

Worth knowing

Submission data is personal data — read what the task needs and do not copy it somewhere it was not collected for. Exports are paginated on purpose, so a form with thousands of entries returns something usable instead of failing slowly. WS Form 1.12 also registers abilities of its own under a different namespace; both sets can be live at once without colliding.

FAQ

Do I need WS Form Pro?
The integration works against whatever edition you have. Where a feature such as styles or templates belongs to a higher edition, the ability says so rather than failing obscurely.
Can it build a whole form at once?
Yes — wsform-json creates a form from a complete JSON definition, which carries fields, tabs, sections, actions and conditional logic together.
What happens if I delete a form?
Its submissions go with it. Permanent deletion requires explicit confirmation; trashing is reversible and does not.
Does it handle file uploads?
Submissions are read through WS Form’s own export layer, so uploaded files are represented the way WS Form represents them.
Will it conflict with WS Form’s own AI tools?
No. The namespaces are separate, so both can be registered at the same time.

Connect WS Form

Activate the plugin, switch the integration on, and let an agent build forms that actually notify someone.

Browse integrations

Connect your first agent.

Follow the quickstart, or book a demo and we'll walk you through it.