Forms: one way to ask, every plugin answered

Form plugins all do the same job and none of them do it the same way. NibWP covers that twice over: one universal tool for when you do not care which plugin is installed, and a dedicated integration for when you do.

The universal tool

nibwp/forms-manage detects the active form plugin and answers with one shared set of actions: list the installed form plugins, list forms, get a single form, read entries, create an entry, delete an entry. Where several form plugins are installed you can name the one you mean rather than accept the detected one. It is the right tool for "how many enquiries came in last week" on a site you have never seen.

The dedicated integrations

Eleven plugins have their own card on NibWP → Integrations, each reaching far more of that plugin than the universal tool can: Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Ninja Forms, Formidable Forms, Forminator, HappyForms, JetFormBuilder, WS Form, and Bit Form, which arrived in 1.2.11 and reads Bit Form's own tables. Between them they cover fields, entries, notifications, confirmations, add-on feeds, payments, settings and exports.

Because each of those goes deeper, the universal card is no longer listed on the Integrations screen. Anything already switched on keeps working.

The audit

Nine of the eleven carry a read-only audit that looks for the failure you cannot see: a form quietly collecting entries nobody is told about. Depending on the plugin it also catches a submission discarded after the visitor has been thanked, every notification template switched off, a reached entry limit, an expired schedule, or an inactive form still embedded on a page. Findings arrive with their fix attached, and nothing is changed for you.

Full guide: Integrations reference