Documentation

Action Types Reference

Action types are classification labels, not claims of executable launch support. Common labels include search, contact_form, lead_form, add_to_cart, checkout_start, and auth.

Detection and action classification do not certify execution. Form providers have separate maturity, default-enablement, field, and version boundaries in the Integrations matrix. The launch matrix covers Contact Form 7 and WPForms Lite only.

Detected Action Types

Action Type	Description
`search`	Site search actions (read-oriented query surfaces).
`contact_form`	Detected contact workflows, including reviewed Contact Form 7 forms.
`lead_form`	Detected lead workflows, including reviewed WPForms Lite forms.
`browse_products`	WooCommerce catalog/shop browsing actions.
`add_to_cart`	Adds products to cart.
`view_cart`	Views current cart state.
`update_cart`	Updates quantity/coupon/cart state.
`checkout_start`	Classifies a detected checkout entry point; it is not an executable launch tool.
`order_status`	Classifies an authenticated order/account surface; it is excluded from launch execution.
`auth`	Classifies login, registration, or password-reset surfaces; they are excluded from launch execution.
`submit_comment`	WordPress comment submission actions.
`custom`	Generic/inferred custom actions (including mined AJAX/REST surfaces).

Risk Levels

Low: Read-oriented or low-impact interactions such as search.
Medium: State-changing interactions with limited commercial impact, typically non-payment forms.
High: Sensitive operations such as authentication, checkout, or account-management paths.

Form submission controls

Eligible form tools are irreversible and disabled by default. The exact provider form, supported field schema, notifications, redirects, and configured feeds require administrator review. The visitor then sees the extracted values and explicitly approves or cancels before the provider performs its own validation and submission.

Confidence Scale

High confidence (>= 0.80): Detector matched a known plugin API or strongly typed integration pattern.
Medium confidence (>= 0.50 and < 0.80): Action inferred from structured form semantics and endpoint behavior.
Low confidence (< 0.50): Action discovered through generic HTML or hook/route mining and should be manually reviewed before publication.

Auth Required and Restricted Flags

Auth required indicates that the action depends on a logged-in session or privileged capability. Restricted means the action is intentionally withheld from public tiers unless you explicitly allow it.

Admin UI Glossary

UI Label	Meaning	Publication Impact
Risk	Operational impact level: low, medium, high.	Dangerous/high-risk actions are excluded from public tiers.
Confidence	How certain the detector is about action semantics.	Use low confidence as a manual-review signal before publishing.
Auth Required	Action depends on authenticated session or privileged context.	Auth-required actions are excluded from `public_standard`.
Restricted	Manual internal-only guard set in the Actions screen.	Restricted actions are treated as dangerous and stay out of public tiers.
Status	Enabled or disabled in the local action map.	Disabled actions are omitted from all exports.
Agent Visibility	Allowed agent contexts for discovering an action.	Sensitive extension-visible actions are filtered in public exports.

Next: Publication Tiers