Contact Form 7
FormsSubmit and inspect Contact Form 7 forms on any WordPress site. Agents list forms, read field definitions and mail settings, and submit entries that run through the plugin's normal validation, mail, and spam checks.
What This Integration Enables
Contact Form 7 sits on millions of WordPress sites as the front door for leads, support requests, and inquiries, and every one of those forms carries configuration that took someone real effort: mail routing, autoresponder copy, spam filtering, notification recipients. The mistake most automation makes is bypassing all of it, writing leads straight into a CRM and orphaning the form's behavior. This connector takes the opposite position: the form is the pipeline, so agents should submit through it, not around it. FlowRunner agents discover the forms on a site, read each form's field definitions and mail settings, and submit entries that run through the plugin's normal validation, mail, and spam checks, exactly as if a visitor pressed send. - Route leads captured anywhere into an existing CF7 form's full mail and notification behavior - Inspect field names and mail settings before automating, no page-source archaeology - Handle every submission status explicitly: mail_sent, validation_failed, spam - Smoke-test production forms on a schedule so breakage surfaces in hours, not weeks - Note: CF7 does not store submissions by default, so treat the returned status as your record unless the Flamingo add-on is installed
Without FlowRunner
With FlowRunner
Use Case Scenarios
The chat lead that gets the same treatment as a form fill
A qualified conversation ends in a chat widget with a name, email, and question captured. The agent calls Get Contact Form to confirm the site's inquiry form still uses your-name, your-email, and your-message, maps the chat transcript summary into the message field, and calls Submit Feedback. The lead now triggers the same notification email to sales and the same autoresponder the website visitors get. On mail_sent, the agent also creates the contact in [HubSpot](/integrations/hubspot). One intake path, no orphaned configuration.
Migrating inquiries from a retired site
A company consolidates three regional WordPress sites into one. Inquiries still trickling into the old sites' inboxes get forwarded to a mailbox the agent watches through [Gmail](/integrations/gmail). Each forwarded inquiry is parsed, mapped to the surviving site's CF7 form, and submitted through Submit Feedback so it enters the standard queue with standard routing. The response status for every migrated entry lands in [Google Sheets](/integrations/google-sheets), which becomes the migration audit: what went through, what failed validation, what the spam filter caught.
The form that gets smoke-tested before Monday
Forms break quietly: a plugin update renames a field, an SMTP credential expires, and the lead flow goes dark for a week. On a schedule, the agent submits a clearly labeled test entry through Submit Feedback and checks the returned status. Anything other than mail_sent posts to [Slack](/integrations/slack) with the invalid fields or error attached, and the web team fixes the form before the weekend's leads hit it. The monitoring costs nothing but a scheduled flow, and the failure mode changes from "discovered by absence of leads" to "flagged within the hour."
Human-in-Loop Highlight
Submit Feedback is not a database write, it is a send. The moment it returns mail_sent, Contact Form 7 has dispatched real email to the recipients configured on the form, often a sales alias and an autoresponder straight to the submitted address, and none of that can be recalled. A batch import pointed at the wrong form, or a mapping that puts the message body in the email field, means dozens of malformed notifications in the sales queue and confused autoresponders in strangers' inboxes. So FlowRunner batch flows stage before they send: the agent maps the full batch, submits nothing, and presents a sample of rendered payloads to the ops owner through a [human-in-the-loop](/concepts/human-in-the-loop) step. The owner approves the mapping once, and only then does the run execute, with per-entry statuses logged as it goes. Single organic leads flow straight through; anything that would send email at volume waits for a person.
Agent Capabilities
3 actionsForms
2- List Contact Forms Lists all Contact Form 7 forms defined on the connected WordPress site, returning each form's ID, title, locale, and unit tag. The discovery step before any automation. Requires the Contact Form 7 plugin to be active.
- Get Contact Form Retrieves a single form by ID, including the form template markup, mail settings, messages, and additional settings under the properties object. The call that turns field-name guessing into field-name reading, and the first step of every mapping an agent builds. Requires the Contact Form 7 plugin to be active.
Submissions
1- Submit Feedback Submits a form entry exactly as if a visitor filled out and sent the form on the site. Field names must match the form's template. CF7 runs its normal validation, mail, and spam checks and returns a status such as mail_sent, validation_failed, or spam, along with any invalid fields. Contact Form 7 does not store submissions by default, so there is no way to read entries back unless the Flamingo add-on is installed.
Frequently Asked Questions
What can FlowRunner do with Contact Form 7?
FlowRunner agents can run List Contact Forms, Get Contact Form, and Submit Feedback in Contact Form 7.
Does connecting Contact Form 7 to FlowRunner require OAuth?
No. Contact Form 7 connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Contact Form 7 trigger a FlowRunner workflow automatically?
Contact Form 7 doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Contact Form 7
$100 in credits. No card required. Connect in minutes.