The Forms connector

The connector lets an AI assistant such as Claude Desktop work with your forms in conversation: “add a quote form with a file upload”, “make the phone field optional”, “send a test submission”. The assistant writes the same JSON you would, and its forms appear on Form Entries → Forms like any other.

It is off until you turn it on, and it cannot read submissions unless you allow that separately.

When to use it

• Building or changing several forms quickly, or building a whole site with the Promptless WP connector alongside.
• Checking a form end to end before handing a site over.
• For a single small change, editing the JSON on Forms is just as quick.

How to connect

1. Go to Form Entries → Connector.
2. Turn on Allow Claude Cowork to call this site.
3. Under Step 1: Generate Connection, select Generate Connection. This creates a WordPress application password for your user and replaces any earlier connection.
4. Under Step 2: Run Setup Command, copy the command and run it in Terminal on your Mac. It needs Node.js 14 or newer and the Claude Desktop app.
5. Quit Claude Desktop and open it again.
6. Start a conversation and ask: “List the forms on my WordPress site.”

Revoke Connection removes the application password; the assistant loses access at once.

Application passwords need HTTPS, or a site marked as a local environment. On a site without either, the page explains what to change.

Access

Switch	What it allows	Default
Allow Claude Cowork to call this site	Every tool. When off, every call is refused.	Off
Also allow Claude Cowork to read form submissions	The entry tools, which see names, emails and messages.	Off

The connected user also needs the pforms_manage_forms capability, which administrators have. Each tool has a per-minute limit, from 5 a minute for deletes and live test submissions to 60 for reading.

The tools

Checking the connection

• formengine_preflight — confirms the connection, reports the plugin version and both switches, and gives the assistant the rules for writing forms. Assistants call it first.

Forms

• formengine_list_forms — lists saved forms; can show only those the assistant created, or only hand-made ones.
• formengine_get_form — one form’s JSON, shortcode and webhook settings. Webhook secrets are never returned.
• formengine_create_form — creates a form, optionally with a webhook.
• formengine_update_form — changes a form. A new configuration replaces the old one entirely.
• formengine_delete_form — deletes a form and keeps its entries.

Entries (need the read switch)

• formengine_list_entries — lists submissions, filtered by form, status or dates.
• formengine_get_entry — one submission in full.
• formengine_delete_entry — deletes a submission and its files.

Testing

• formengine_test_submit — sends answers to a form. With dry_run it only checks them and shows what would be stored. Without it, it creates a real entry and fires webhooks and workflows; skip_notifications stops the email.

Limits

• Test submissions skip spam protection and cannot include files. Test a file field by submitting the form on the page.
• Webhook secrets can only be regenerated on the Forms screen.
• Forms the assistant creates are marked as its own, so it can tell them from forms you maintain by hand. The mark cannot be changed.
• The Promptless WP connector is separate and set up on its own page; see The Promptless Connector.

Related pages

• Creating and editing forms — The Forms screen, form ID rules, the parts of a form's JSON and every form-level setting.
• Entries — Read, mark, search, export and delete form submissions, and what each entry stores, including uploaded files.
• Privacy and data retention — The personal data Forms stores, how WordPress's export and erase tools reach it, and how to delete old entries on a schedule.
• The Promptless Connector — What the Promptless connector lets an AI assistant such as Claude Desktop do on your site, what it cannot do, and how access is controlled.