How it works
Each form the tenant whitelists inSettings → Animam → WPForms bridge is exposed as its own dedicated tool, named wp_submit_wpforms_{id} (where {id} is the WPForms form id). The tool’s JSON schema is derived from the form’s own fields (labels, types, required flags), so the agent knows exactly what to collect.
- The agent reads the tool’s schema and captures the fields conversationally.
- After the visitor expresses intent, the agent calls
wp_submit_wpforms_{id}with the structured payload. - The plugin runs the standard WPForms processing pipeline → entry created, notifications and integrations fire.
Why this is safer than a parallel capture surface
Per-form whitelist (opt-in)
The bridge is opt-in per form: nothing is exposed until the tenant explicitly whitelists a form inSettings → Animam → WPForms bridge. Only whitelisted forms get a wp_submit_wpforms_{id} tool; everything else is invisible to the agent. This keeps out of reach:
- Forms that gate sensitive content (DSAR requests, support tickets requiring human triage).
- Forms with payment fields (use the WooCommerce bridge or
COLLECT_PAYMENTinstead). - Forms behind a manual review queue.
Plan
Bridges require the Visitors plan (€19/month) or higher — thebridges capability. See WordPress pricing.