Get the plugin
WP MCP/Integrations/Forms

Forms integration

Elementor Pro Forms MCP

Elementor Pro keeps what its forms collect in three tables of its own, a form identified the way its submissions screen filters by it ("{post_id}_{element_id}"). WP MCP Pro reads those tables directly with the same filters the screen uses, so a site without a license key still answers: elementor-list-forms finds the forms in pages, templates and popups with their fields and submission counts; elementor-list-submissions, elementor-get-submission and elementor-export-submissions read what came in. Writes are off until a site opts in: elementor-update-submission-status moves a submission between new and trash and sets read or unread under a before-image of that one row; elementor-delete-submission permanently deletes a submission with its values and action log, asking for confirm:true first and capturing every row as a before-image so rollback-session reinserts them with their original ids. Submissions are personal data (names, emails, IP addresses), and every op takes the capability Elementor Pro's own submissions screen requires.

plugin-data-readplugin-data-write

In practice

How Elementor Pro Forms work goes with an agent.

Elementor Pro does not keep forms as records. A form is a widget inside a page's Elementor data, or an atomic form in newer builds, named by the page id and element id, and what visitors submit goes to three tables: one row per submission, one row per field value and one per action that ran after the submit. WP MCP reads those tables with the same filters Elementor's submissions screen uses. It also finds forms that have submitted before but are no longer on the page, flagged in_page:false from Elementor's stored form snapshot.

Which Elementor forms exist, and how many submissions are unread on each?

Runs elementor-list-forms, which scans pages, templates and popups and returns each form's key, fields and submission counts (total, unread, trash). It is a read, so nothing is snapshotted.

Show unread submissions on form 128_a1b2c3 from the last 7 days.

Runs elementor-list-submissions with form, status unread and an after date, newest first, with counts for all, unread, read and trash. elementor-get-submission then reads one in full.

Export the demo request form as a CSV.

Runs elementor-export-submissions, which returns one column per form field, then Elementor's own columns such as form, id, created at, IP and referrer. CSV is the default, JSON is optional, and offset and limit page through up to 1000 rows per call.

Trash submission 90 and mark it read.

Runs elementor-update-submission-status with status trash and is_read true, once a site has opted in to writes. A before-image of that one row is taken, so rollback-operation puts it back.

What your AI can do

Real Elementor Pro Forms operations, every write reversible.

  • List Elementor Pro forms with their fields and submission counts
  • List, read and export submissions with the screen's own filters
  • Move a submission to or from the trash and set read or unread (opt-in)
  • Permanently delete a submission with confirm:true, reinsertable from the session
  • Restore a re-statused or deleted submission exactly

Example prompts

Example Elementor Pro Forms prompts.

How many submissions did the contact form get this month?

Export the unread submissions from the demo request form.

Mark the spam submissions on the newsletter form as trash.

Under the hood

The Elementor Pro Forms calls, under the hood.

wpmcp, elementor-pro-forms

plugin-data-read({ integration: "elementor-pro", operation: "elementor-list-submissions", args: { form: "128_a1b2c3" } }), the screen's own filters

plugin-data-write({ integration: "elementor-pro", operation: "elementor-update-submission-status", args: { id: 90, status: "trash" } }), opt-in; row before-image, reversible

Safety and access

What can be undone on Elementor Pro Forms, and what costs what.

Recoverable on Elementor Pro Forms

  • elementor-update-submission-status takes a before-image of the one submission row, and rollback-operation restores it.
  • elementor-delete-submission captures the submission, its values and its action log in one session before deleting.
  • rollback-session reinserts those rows with their original ids.

Elementor Pro Forms limits and opt-ins

  • Both writes are off until a site opts in with the wpmcp_enable_elementor_pro_write filter.
  • elementor-delete-submission is destructive and needs confirm:true; it removes the submission, its values and its action log. Trashing with update-submission-status is the lighter option.
  • Forms themselves are read only: no op creates a form or changes its fields or actions.
  • Submissions are personal data, so every op needs manage_options, as Elementor Pro's own submissions screen does.

Free or Pro: These ops are Pro, on the plugin-data pair, and need Elementor Pro active. They do not need an Elementor Pro licence key, because the reads go to the submissions tables directly, so a site whose licence has lapsed still answers. The reads work on any licensed WP MCP site. The two writes are off by default behind wpmcp_enable_elementor_pro_write, and the delete also asks for confirm:true.

Part of WP MCP Pro

The Elementor Pro Forms integration is part of WP MCP Pro.

One Pro licence unlocks the Elementor Pro Forms tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.

Frequently asked

Elementor Pro Forms MCP: questions, answered.

Does the Elementor Pro Forms integration need an Elementor Pro license key?

No. The reads work on the submissions tables directly, so a site whose license has lapsed still answers. If Elementor Pro has not created the tables yet, the ops say so and point to loading wp-admin once.

Is deleting a submission reversible?

A delete captures the submission, its values and its action log as a before-image first, so rollback-session reinserts them with their original ids. It still asks for confirm:true, since submissions are personal data.

Does the Elementor Pro Forms integration find forms that are no longer on a page?

Yes. elementor-list-forms also returns forms that Elementor's stored form snapshot remembers but that are gone from the page's data, marked in_page:false. That lets an agent still reach submissions of a form someone has since removed, using the same form key, which is the page id, an underscore and the element id.

Does the Elementor Pro Forms integration handle Elementor's atomic forms as well as the form widget?

Yes. elementor-list-forms recognises both the classic form widget and the newer atomic form, and reports which kind each one is. Submissions are identified the same way for both, so listing, reading and exporting work without the agent needing to know which kind a form is.

What if the submissions tables are not there yet?

Elementor Pro creates them on its next wp-admin load, so on a fresh install they can be missing. The ops then answer elementor_submissions_unavailable instead of an empty list, and elementor-list-forms reports tables_present as false. Loading any wp-admin page once creates the tables.

How many submissions can be listed or exported at once?

A listing takes per_page up to 100, 20 by default. An export defaults to 500 rows and takes up to 1000 per call, with offset to continue. You can also pass specific submission ids, up to 1000, to export exactly those instead of a whole form.

Point your AI at Elementor Pro Forms.