Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.animam.ai/llms.txt

Use this file to discover all available pages before exploring further.

The WPForms bridge lets the agent submit any of your forms on behalf of the visitor, through the native WPForms pipeline. WPForms persists the entry, fires its existing webhooks/Zapier connectors/notification emails — exactly as if a human had filled the form in the browser.

​
How it works

  1. The agent calls wpforms_list_forms to enumerate forms (skipping any in the denylist from Settings → Animam → WPForms bridge).
  2. The agent calls wpforms_get_form to read the field schema (labels, types, required flags).
  3. After the visitor expresses intent, the agent calls wpforms_submit_form with the structured payload.
  4. The plugin runs the standard wpforms_process_complete pipeline → entry created, automations fire.

​
Why this is safer than a parallel capture surface

Animam-owned captureWPForms bridge
Tenant validationbypassed✅ runs your existing required-field, regex, conditional logic
Tenant integrationsbypassed✅ Zapier, ActiveCampaign, MailChimp, etc. fire as-is
Tenant notification emailsbypassed✅ “New form entry” emails go out as before
Audit trailAnimam-side onlyboth sides
Migration riskhigh (re-wire automations)zero

​
Per-form denylist

In Settings → Animam → WPForms bridge the tenant can mark specific forms as agent-disabled. The agent simply doesn’t see them in wpforms_list_forms. Useful for:
  • Forms that gate sensitive content (DSAR requests, support tickets requiring human triage).
  • Forms with payment fields (use the WooCommerce bridge or COLLECT_PAYMENT instead).
  • Forms behind a manual review queue.

​
Plan

Bridges require the Bundle plan (mcp_tools capability). See WordPress pricing.