Documentation
Integrations
Compatibility has several layers. Detecting a provider does not automatically make its workflows public or safe to execute.
Product surfaces
| Surface | Current scope | Control boundary |
|---|---|---|
| Content | Posts, navigation, search, taxonomies, site information, and public discovery. | Read-only Standard Tools form the default baseline. |
| Forms | Provider-aware discovery and reviewed publication for Contact Form 7 and WPForms Lite. | Every form is reviewed separately; certified execution is bounded to supported single-page forms, irreversible, approval-gated, and disabled by default. |
| Commerce | WooCommerce product discovery, comparison, cart inspection, and selected cart changes. | Cart writes require approval. Checkout, payment, orders, authentication, and accounts are excluded. |
Forms compatibility matrix
This table follows the plugin's canonical provider registry. A certified provider still has per-form enablement, field, workflow, and approval boundaries.
| Provider | Detection | Schema discovery | Reviewed publication | Certified execution | Default enablement | Tested versions | Known limitations |
|---|---|---|---|---|---|---|---|
| Contact Form 7 | Tested | Supported fields discovered | Tested | Certified for supported single-page forms | Detector on; execution off | 6.1.5 and 6.1.6 | Single-page forms only. Quiz, acceptance, CAPTCHA, uploads, payment, account, signature, calculations, and checkout are blocked. |
| WPForms Lite | Tested | Supported fields discovered | Tested | Certified for supported single-page forms | Detector on; execution off | 1.9.9.2 and 1.10.2.1 | Single-page forms only. CAPTCHA, uploads, payment, account, signature, calculations, and checkout are blocked. |
What form execution means
Eligible tools are registered per form, not per provider. An administrator must enable the transactional framework and opt in to the exact reviewed form. Immediately before an irreversible submission, the visitor sees the provider, exact field values, and disclosed side effects, then explicitly approves or cancels.
Provider validation and confirmation remain authoritative. Notifications, redirects, conditional logic, honeypots, and third-party feeds remain provider-controlled and must be reviewed before a form is enabled. Unsupported or high-impact fields cause the form tool to fail closed.
WooCommerce boundary
Read-only product search, product lookup, and categories are part of Standard Tools when WooCommerce is active. Separately reviewed transactional tools can inspect and change the visitor's cart with approval and idempotency controls. Open for Agents does not implement checkout, payment, order placement, login, registration, profile, or account-changing tools.