Review forms and their submissions
Inspect an existing form, check notifications, and manage a test submission.
Before you start
- A verified connection to a practice site.
- A supported active form plugin.
- EMCP Pro for integrations other than Contact Form 7.
- A test form and permission to view its entries.
Let’s do this, step by step.
Step 01
Check the integration tools
Open Setup → Tools → Plugins → Forms. Choose the section for your installed form plugin. Inspect dependencies and both read/write switches. Enable the actions for this task, choose Save changes, then reconnect.
Open EMCP Tools, then Setup, then Tools, then Plugins, then Forms. Choose the section for your installed form plugin. Inspect dependencies and both read and write switches. Enable the actions for this task, choose Save changes, then reconnect.
Step 02
Discover the active form integration
Ask the AI to list the operations available for the installed form plugin.
The supported operations differ between plugins. Contact Form 7 does not store entries; WPForms entries require its Pro edition.
Step 03
Read the form
List forms, choose the exact ID, and inspect its fields and notifications.
These tools manage existing forms. They do not build a new form structure. Create the form in its native editor if it does not exist yet.
Step 04
Review a notification change
Show the current and proposed notification settings. Enable only the required write tool and save the reviewed change.
Use a test recipient that you control. Read the saved settings back before trying the form.
Step 05
Submit a test
Open the form on the site and make one test submission. Check its expected notification and stored entry where supported.
A successful settings save does not prove email delivery. Test the actual form and confirm the message reaches the intended inbox.
Step 06
Handle a test entry
Where supported, mark the test entry read or spam, then inspect the result.
Use test data in recordings. Deleting entries needs explicit confirmation and may be permanent, so do not use a real customer submission as a demonstration.
Step 07
Flamingo: sort stored messages
With EMCP Pro and Flamingo, list stored messages with flamingo-read and read one with include_details. Enable Flamingo Write only to mark the test message as spam, trash or restore it, using the version you read, then undo the change from History.
Flamingo keeps what the form saved. Read the list first, open the test message, and change its status only once you know it is the right one. History can put the status back.
You’re done when…
A real test submission follows the intended notification and entry workflow.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.
A brief becomes a real page.