WPForms
FormsGive AI agents read access to WPForms on your WordPress site. Agents list forms, inspect form structure, and retrieve submitted entries so downstream workflows can qualify, route, and respond to every submission.
What This Integration Enables
WPForms is the front door on millions of WordPress sites, and this connector gives FlowRunner agents read access to what walks through it: List Forms and Get Form to map the site's forms, List Entries and Get Entry to pull the submissions. It comes with a caveat this page will not bury. Forms read cleanly through the WordPress REST API when the site exposes the wpforms post type, but entries are a WPForms Pro feature in a custom database table with no officially documented public REST API. The entry operations target the plausible endpoint and work only on sites that expose one through an add-on or custom code. FlowRunner's view: a connector that names its failure modes is the only kind you should let near your lead pipeline, because agents can be built to verify what a spec sheet would rather not mention. - Sync WordPress form submissions into CRMs, spreadsheets, and email marketing lists on a schedule - Enumerate a site's forms and inspect a specific form by ID for routing and mapping - Pull individual entries or entry lists for reporting on sites that expose an entries endpoint - Treat endpoint absence and empty reads as verifiable events, with a human closing the loop - Prove the setup works with a probe before any pipeline depends on it
Without FlowRunner
With FlowRunner
Use Case Scenarios
The quote-request form wired to a same-hour response
A services firm's quote form runs on WPForms. The hourly sweep pulls new entries with List Entries, creates each requester as a contact in [HubSpot](/integrations/hubspot) with the project details logged, and posts the request to the sales channel in [Slack](/integrations/slack) with name, email, and budget field. The firm's honest response time drops from "when someone checks the inbox" to "within the hour," without anyone changing how the website works.
The newsletter list that grows itself
Signup forms across the site feed one workflow: entries sweep in, the agent normalizes the email field, and each signup lands in [Mailchimp](/integrations/mailchimp) with a tag for which form and page produced it. The tracking row in [Google Sheets](/integrations/google-sheets) gives marketing a per-form conversion view. Unsubscribed and bounced addresses never get re-added, because the agent checks the audience before writing.
The migration that proved the endpoint before trusting it
An ops team inherits a WordPress site and wants entries flowing into the CRM. Before scheduling the sync, they run the workflow's verification path: List Forms confirms the post type is exposed, then Get Entry is tested against a known entry ID from wp-admin. On this site the entries endpoint returns 404, so the workflow reports exactly that, and the team adds the endpoint via an add-on before turning on the sweep. The connector told them the floor was missing before they stacked a pipeline on it.
Human-in-Loop Highlight
List Entries is best-effort by the nature of what it targets: entries live in a Pro-only custom table, and the REST route this operation calls only exists on sites that added one. That makes the dangerous output of this connector not a bad write, there are none, but a false silence. An empty response can mean no new leads, or it can mean the endpoint 404ed, a plugin update removed the route, or the site moved hosts, while quote requests pile up unseen behind the login. A missed lead is spend you cannot recover; the click was paid for whether or not anyone answered. So the sweep agent never converts an error or a suspicious empty read into "nothing new." It holds that conclusion, posts what it saw, the route, the status code, the last known entry count, and asks a person to confirm against wp-admin. The workflow reports "no new leads" only after a human has made it true.
Agent Capabilities
4 actionsForms
2- List Forms Retrieves a paginated list of WPForms forms from the connected site via the wp/v2/wpforms REST route, with search, status filtering, and ordering. Requires the wpforms post type to be exposed to the REST API; a stock install may 404.
- Get Form Fetches a single form by its numeric post ID, returning the form's post record: title, slug, status, dates, and link. Full field configuration appears only when the site exposes it via REST.
Entries
2- List Entries Best-effort retrieval of a form's submissions. Entries are a WPForms Pro feature in a custom database table with no documented public REST API; this targets a plausible wpforms/v1/entries route and works only where such an endpoint exists. Experimental, and the reason this page's verification gate exists.
- Get Entry Best-effort retrieval of a single entry by its numeric ID via the same unofficial route. Used to pull one submission's full detail on sites where the endpoint is present, and as the probe that verifies the endpoint before a sync is trusted.
Frequently Asked Questions
What can FlowRunner do with WPForms?
FlowRunner agents can run List Forms, Get Form, and List Entries in WPForms, plus 1 more action.
Does connecting WPForms to FlowRunner require OAuth?
No. WPForms connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can WPForms trigger a FlowRunner workflow automatically?
WPForms doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with WPForms
$100 in credits. No card required. Connect in minutes.