Formidable Forms
FormsWork with Formidable Forms data on your WordPress site. Agents list forms, and create, update, and delete entries through the REST API using WordPress Application Password auth.
What This Integration Enables
A huge share of business forms live inside WordPress, and Formidable Forms entries live inside the site's own database, which usually means the data stays wherever the plugin's admin screens can show it. The REST API changes that, and this connector puts FlowRunner agents on it. Agents list and inspect forms, read entries with their field values and submission metadata, create entries from external workflows, update values programmatically, and delete under review, authenticated with a WordPress Application Password rather than anyone's real login. - Sync new submissions into CRMs, spreadsheets, and databases on a schedule - Mirror submissions from external sources into WordPress form entries - Read and update entry data programmatically, keyed by the form's numeric field IDs - Moderate and clean up entries with human judgment on the destructive step - Keep the site's form data and your operational systems telling the same story The Application Password model is worth the setup: the connecting user gets a revocable credential scoped to API access, so the automation never holds a human's real WordPress login, and rotating it touches nothing else on the site. One detail matters for orchestration hygiene: Create Entry writes directly to the database and does not fire front-end confirmations or notifications, so mirrored entries never spam your team or your submitters. The destructive end runs through FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The WordPress form that finally reaches the CRM
List Entries sweeps the contact form every fifteen minutes, scoped by form ID and paged by entry. Each new submission becomes a contact in [HubSpot](/integrations/hubspot), a row in [Google Sheets](/integrations/google-sheets), and an alert in [Slack](/integrations/slack) for the sales team, with values mapped through the field IDs from Get Form. The site keeps collecting exactly as before; the data just stops living only in wp-admin, and nobody on the sales team ever needs a WordPress login.
One intake, many front doors
Leads arrive through [Typeform](/integrations/typeform) at events and through the website's Formidable form the rest of the time. Create Entry mirrors the external submissions into the WordPress form, keyed by numeric field ID, so the site's database remains the single archive and downstream reporting reads one source. Because the direct write skips front-end notifications, the mirroring runs silent, and the source system is recorded in a dedicated field.
Moderated cleanup on a live site
The spam scorer from the primary workflow feeds a weekly moderation queue. The site owner reviews each suspect with the full entry from Get Entry, its values, submission date, and originating IP, and rules on it. Update Entry tags borderline entries for observation instead of deleting them, and Delete Entry removes only the condemned, one ID at a time, with the verdict logged. The form's data stays clean without the bulk-delete roulette that WordPress admins know too well.
Human-in-Loop Highlight
Delete Entry is permanent, and on this connector the risk has a particular shape: entries are addressed by bare numeric IDs, and the values inside them are keyed by numeric field IDs too. A moderation loop that mistakes entry 4821 for 4812 destroys a real customer's quote request with no recycle bin behind the REST API to save it. So deletion here is a verdict, not a filter outcome. The agent presents the suspect: "Entry 4821 on the Quote Request form, submitted 03:12 from an IP with four other submissions that hour, message contains six outbound links. Full values attached. Spam?" The owner rules, and only a confirmed guilty verdict triggers the delete against that exact ID. The scorer improves over time, but its false positives cost review minutes instead of customers, which is the correct direction for the asymmetry to run.
Agent Capabilities
7 actionsForms
2- List Forms Retrieves all forms on the connected WordPress site with each form's ID, key, name, and description. The discovery step before any entry work.
- Get Form Retrieves one form's full configuration, including its fields and their numeric IDs. The field-ID map every create and update depends on.
Entries
5- List Entries Retrieves submitted entries, filterable to one form and paginated, each with field values keyed by field ID plus creation date, user, and IP metadata. The sweep behind every sync and moderation queue.
- Get Entry Retrieves a single entry by numeric ID with all values and submission metadata. The evidence pull before any moderation verdict.
- Create Entry Creates an entry for a form with a Field Values object keyed by numeric field IDs. Writes directly without firing front-end confirmations or notifications, which makes silent mirroring possible.
- Update Entry Updates an entry's field values, changing only the supplied fields. Used for tagging, corrections, and status tracking on live entries.
- Delete Entry Permanently deletes an entry by numeric ID. Cannot be undone, which is why it executes only on this page's reviewed verdicts.
Frequently Asked Questions
What can FlowRunner do with Formidable Forms?
FlowRunner agents can run List Forms, Get Form, and List Entries in Formidable Forms, plus 4 more actions.
Does connecting Formidable Forms to FlowRunner require OAuth?
No. Formidable Forms connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Formidable Forms trigger a FlowRunner workflow automatically?
Formidable Forms doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Formidable Forms
$100 in credits. No card required. Connect in minutes.