Contact Form 7 can collect enquiries while Airtable remains the team’s operational workspace. Integration for Airtable connects the saved CF7 form directly to a base and table, so staff do not need to retype email messages.
Why use this path
- Keep Contact Form 7 for the public form while Airtable stores structured records.
- If you retain CF7 mail or Flamingo, test each output alongside the Airtable connection.
- Review each mapped sync attempt in Sync History.
What you need
- Contact Form 7 active with at least one saved and published form
- An Airtable account with a target base and table
- Integration for Airtable installed and activated
If the workflow also uses CF7 mail or Flamingo, test those outputs and verify Airtable separately in Sync Logs.
Contact Form 7 to Airtable, step by step
- Go to Plugins → Add New and search for Integration for Airtable
- Install and activate it, then open Airtable Sync
Open Airtable Sync → Airtable Config and choose one path.
- Click Connect with Airtable and sign in
- Grant access to the target base
- Confirm Connected via OAuth in WordPress
- Create a token with
schema.bases:read,schema.bases:write,data.records:read, anddata.records:write - Give it access to the target base
- Paste it into Airtable Config and save
- Go to Airtable Sync → Forms and add a connection
- Choose Contact Form 7 and select the form by title
- Select a base and table, or create a table from the form fields
Map the saved CF7 tags, such as your-name, your-email, and your-message, to compatible Airtable columns.
- Use Long text for messages and Email or text for email tags.
- Map explicit form fields rather than assuming special mail-tags are available.
- Reopen the mapper after renaming a tag.
- If page attribution matters, add an explicit source field and confirm that it appears in the mapper.
- Save the connection and submit known values on the live form
- Check Airtable Sync → Sync Logs
- Confirm the Airtable record and mapped values
If the form also sends mail or stores entries elsewhere, verify each result before diagnosing the cause.
Send the error text and a screenshot to support@ripplestep.com.
Common Contact Form 7 workflows
01Contact enquiries
Send identity, message, consent, and page source to a Leads table.
02Quote requests
Map service and budget choices to compatible Airtable fields.
03Shared shortcode
Add an explicit source field and confirm it appears in the mapper when the same form appears on several pages.
04Multiple outputs
Test CF7 mail or Flamingo alongside Airtable, then verify each destination independently.
Contact Form 7 gotchas
- Changing a tag name requires a mapping update.
- Keep CF7 spam protection enabled and test rejected submissions before launch.
- Special mail-tags may not be exposed as normal form fields, so use explicit fields for required data.
- A connection targets the saved CF7 form. Test any page-source field you add for attribution.
Free vs Pro
| Capability | Free | Pro |
|---|---|---|
| Form connections | 1 active | Unlimited |
| Successful form syncs | Up to 300 per month | Unlimited |
| Field mapping | Core mapping | Core mapping |
| Delivery | Immediate or WP-Cron | Immediate or WP-Cron |
| Sync History | Yes | Yes |
Start on Free to validate one CF7 connection. See the Forms to Airtable product page for current plan details. Pro is $99/year.
Troubleshooting
CF7 shows a mail error
Check Sync History and the Airtable table as separate evidence. Then investigate the CF7 mail or SMTP path based on its own result.
A renamed tag is empty
Save the CF7 form, reopen its connection, and map the new tag name.
Unexpected rows appear in Airtable
Keep CF7 spam protection enabled and test rejected submissions. Review the original form submission and Sync Logs before changing the Airtable workflow.
Sync History reports a field type error
Align the Airtable column with the submitted value, or map uncertain values to text while testing.
FAQ: Contact Form 7 to Airtable
Can CF7 send submissions without Zapier?
Yes. Create the connection and field mapping inside WordPress.
Where do I see failed syncs?
Open Airtable Sync → Sync Logs and review the recorded error.
Do I still need CF7 email notifications?
Keep them if your workflow needs email alerts, then verify Airtable delivery separately in Sync Logs.
Does this work with Flamingo?
Test both plugins together and verify the Airtable result separately in Sync Logs.
Is OAuth required?
No. OAuth is recommended, and a correctly scoped Personal Access Token is also supported.
Next steps
- Install Integration for Airtable free.
- Map one saved CF7 form and submit known values on the front end.
- Confirm the result in Sync History and Airtable.
Also useful
Send Contact Form 7 entries to Airtable
Map one form and verify the first Airtable record in Sync History.
Install Integration for Airtable free