Find broken and forgotten Fluent Forms with AI
One read-only sweep: every form, the pages that use it, and the pages pointing at a form that no longer exists.
Prerequisites
A site connected to WPVibe with the free Fluent Forms plugin (tested on 6.2.15) and an administrator account.
Audit the Fluent Forms forms on my site. This is read-only: don't change or delete anything.
Never pass the fields parameter on a /fluentform/v1 route: Fluent Forms answers with an object that WordPress can't trim, and the site returns a critical error. Raise max_length instead.
1. List every form with rest_api GET /fluentform/v1/forms?per_page=100 (page on with &page=2 if last_page is more than 1): id, title, status, total_Submissions.
2. For each form, GET /fluentform/v1/forms/ID/findShortCodePage. Its locations are the posts of every public type, including drafts, that embed that form with a shortcode or block, and shortcodes inside Elementor, Beaver Builder and Bricks layouts.
3. Find embeds of forms that are deleted or unpublished: GET /wp/v2/pages and then /wp/v2/posts with search=fluentfo, status=publish,draft,private,pending,future, context=edit, per_page=100 and fields id,title,status,link,content.raw (fields is fine on /wp/v2 routes). In each content.raw, collect the form ids in [fluentform id="N"] shortcodes and in fluentfom/guten-block blocks ({"formId":"N"}; the block name really is spelled fluentfom). Any id that is not in step 1, or whose status there is unpublished, is a broken embed: that page shows nothing where the form was.
4. For each form found nowhere, check for recent entries with GET /fluentform/v1/submissions?form_id=ID&per_page=1&date_range[0]=[90 days ago, YYYY-MM-DD]&date_range[1]=[today] (max_length 4000, read total). A form with entries is in use somewhere you can't see. Conversational forms (they have a conversion_preview link in step 1) are usually shared by that link, not embedded.
5. Give me one table: form id, title, status, entries, where it is used (page titles with their status), and a note. Then the broken pages with their links, the form id and whether it is deleted or unpublished. Then the forms you found nowhere and with no entries in 90 days, as "possibly unused", with what you could not check: popups from other plugins, widgets, synced patterns, theme templates, Elementor's own Fluent Forms widget and other builders.
6. Suggest fixes (publish the form again, point a broken page at an existing form, or remove the empty block) and wait for me to ask before doing any of them.
Skip pasting the full prompt. Drop this into your AI on a site that already has WPVibe:
Run the “Find broken and forgotten Fluent Forms with AI” recipe from the WPVibe cookbook on my connected site.
Forms pile up. There is the one from last summer’s offer, the copy someone made to test a field, and the page that still points at a form that was deleted or unpublished, where visitors now see a blank space and no error. Fluent Forms shows you where one form is used, but not the whole picture.
Ask your AI assistant and it lists every form, asks Fluent Forms where each one is embedded (shortcodes and blocks in pages, posts and drafts, and shortcodes inside page builder layouts), then searches your pages and posts for embeds of forms that are deleted or unpublished. You get one table: each form, where it is used, and which pages are broken. It changes nothing.
Use the “possibly unused” list as a starting point, not a delete list: a form can also live in a popup, a widget, a synced pattern, theme code or Elementor’s own Fluent Forms widget, and conversational forms are usually shared by link. The assistant leaves out forms that got entries lately, says what it could not see, and suggests fixes for you to approve separately.
Outcome
A table of every Fluent Forms form with where it is used, the pages with a broken form, and the forms that look unused.