Formidable Forms
Manage forms, entries and Views on a self-hosted Formidable Forms site via its WordPress REST API v3.
About
Formidable Forms ships in the w6w first-party pack. It declares 15 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.formidableforms- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Forms & Surveys · Productivity
Overview
Formidable Forms is a WordPress plugin for building forms, directories, dashboards and calculators, and this app talks to a site’s own Formidable REST API v3: read and manage forms, list their fields, search and manage entries, pull field statistics, and list the styles and Views the site has defined.
Because every call goes to the customer’s own WordPress install rather than a shared vendor host, this app connects per site rather than per account, with a WordPress Application Password standing in for a login. Creating or updating an entry writes the database row directly through Formidable’s own entry-saving code, but unlike a real visitor filling in the form, it does not run field validation, spam checks or fire the form’s own notifications — the right choice for imports and back-fills that shouldn’t refire a customer email.
Deleting a form or an entry is here as well, deliberately gated behind an explicit confirmation, because a self-hosted instance has no trash to recover from either. Form-authoring surfaces this app deliberately stays out of: building a form’s field graph, style CSS internals, form actions (notifications/webhooks), Applications, and View layouts are all left to the WordPress admin, since none of them have a documented request/response shape solid enough to automate without guessing.
Build with Formidable Forms
Three routes to the same 15 actions. The Workflow tab is generated from Formidable Forms's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Formidable Forms's real ids.
{
"manifestVersion": "2",
"name": "formidableforms-example",
"steps": [
{
"id": "entry-create",
"uses": {
"app": "io.w6w.formidableforms",
"action": "entry-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"formId": "<formId>",
"fieldValues": "<fieldValues>"
}
}
]
}Here are some of the things you can do
-
Create Entry
performentry-create -
Get Entry
readentry-get -
Get Many Entries
searchentry-get-many -
Update Entry
performentry-update -
Get Form Fields
readfield-get-many
+10 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Formidable Forms, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Formidable Forms. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "entry-create",
payload: {
formId: "<value>",
fieldValues: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action entry-create --payload '{"formId":"<value>","fieldValues":"<value>"}'Give an AI agent Formidable Forms — without giving it Formidable Forms's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.formidableforms#entry-create",
"input": {
"formId": "<formId>",
"fieldValues": "<fieldValues>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Formidable Forms connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Formidable Forms's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Formidable Forms itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Formidable Forms declares its own checks, so its health is a property of the app rather than something the host guesses at.
Formidable Forms platform status
Site reachable
Unauthenticated `GET /wp-json/` against this connection's site — proves the host resolves, the WordPress REST API is enabled, and the `frm/v3` namespace is registered.