Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →If Contact Form 7 submissions are not appearing as leads in Odoo CRM, first check whether WordPress accepted the submission, then verify the separate integration that sends it to Odoo. Installing Odoo CRM alone does not connect a WordPress form to Odoo. A CF7 form needs a connector, custom code, or middleware; authentication, destination model, field mapping, and error logs are the next checks.
First, identify which contact-form architecture you use
Odoo’s native Website contact form and a WordPress Contact Form 7 form are different routes into CRM. Odoo’s version 13 documentation describes configuring its own website form to create CRM records; it does not establish an automatic connection from an external WordPress form. Odoo’s Website form documentation covers that native route.
As an Amazon Associate I earn from qualifying purchases.
| Route | Where the form lives | What sends data to CRM | Authentication and mapping | Where to investigate failures |
|---|---|---|---|---|
| Native Odoo Website form | On an Odoo website | Odoo’s website form configuration | Configured within the Odoo route; check the model and form settings for your installed version | Odoo website and CRM settings, plus the relevant CRM views |
| WordPress Contact Form 7 | On a WordPress site | A CF7 connector, custom integration, or middleware must pass submissions to Odoo | Depends on the integration; a connector may require Odoo connection details and explicit field mapping | CF7 submission status and the integration’s own logs |
If you use CF7, troubleshooting Odoo’s native website form settings will not fix a missing WordPress-to-Odoo connection. Identify the specific connector or code path before changing CRM configuration.
1. Confirm Contact Form 7 accepts the submission
Submit the form yourself and check its on-page response. A validation error or failed submission means the problem starts in WordPress, before the integration can create a CRM record. Check that required fields are filled correctly and that the form reports success. Contact Form 7’s official documentation index links to troubleshooting for configuration errors and AJAX behavior.
A successful message confirms that CF7 handled the submission; it does not, by itself, confirm that Odoo received it. Treat the form result and CRM record as two separate outcomes.
2. Find the component responsible for sending data to Odoo
Check the WordPress installation and any custom implementation to establish what should pass CF7 data into Odoo. It may be a plugin connector, custom code, or middleware. If no such integration is configured, there is no data-transfer step for Odoo CRM to receive.
For a connector, consult the setup instructions for the installed version rather than assuming every integration uses the same endpoints, settings, or compatibility requirements. One public connector repository documents its own configuration and says it ideally targets Odoo 14 or later for API-key support, with PHP 8.1 or greater. Those are statements about that connector, not universal Odoo requirements. See the connector README.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
3. Test Odoo authentication before changing field mappings
When an integration cannot authenticate, adjusting field mappings will not make it create records. For the connector documented in the public repository, setup includes the Odoo URL, database name, user email, and API key, and the README advises testing the connection first: “There is a test button for each connection row. Press this to make a test connection to check authentication before assuming the connection details are correct.”
Use the installed integration’s own connection test if it has one. Check the URL and database against the target Odoo instance, and verify that the configured user and credential are valid for that integration. The precise authentication method can vary by connector and Odoo version; use the instructions for your actual setup.
4. Confirm the destination is a lead, not a contact
A record can be successfully created in Odoo but still be absent from the CRM lead view if the integration is configured to create a different record type. Check the connector’s selected destination model and the Odoo screen where that record should appear.
Rank #3
- The cited connector README gives
crm.leadas an example for leads. - It gives
res.partneras an example for contacts.
These are examples for that connector, not mandatory model values for every integration or deployment. Confirm the intended record type and model in your connector’s configuration.
Free tools Windows power users keep installed
One-click scans. No signup required.
5. Check field mappings and submitted values
Once authentication works and the destination model is correct, compare the fields CF7 actually submits with the fields the integration maps into Odoo. A form label visible to a visitor does not prove that its submitted field name or value is mapped to the intended Odoo field. The connector workflow in the cited README uses explicit CF7-to-Odoo field mappings and allows constant values.
- Compare each configured mapping with the actual CF7 field name and submitted value.
- Check that the mapping targets fields on the selected Odoo model.
- Review any constant values and conditional or optional fields in the integration.
- Look for rejected or empty values in the integration’s error details.
There is no version-independent list of required lead fields established here. If Odoo rejects a record, use the error from your integration and the guidance for your installed Odoo version rather than adding guessed fields.
6. Read the integration’s error log
After reproducing the issue with a test submission, inspect the connector or middleware logs. The cited connector documents an “Odoo Submit Errors” tab for failures that prevented a form from submitting to Odoo. Other integrations may name or locate their logs differently; use the equivalent error view or logs for the software you installed.
Use the reported failure to choose the next check: an authentication problem points back to the connection settings; a model or field error points to the destination and mappings; and a WordPress validation failure belongs to CF7 configuration. Do not infer a connector-specific error code from CF7’s general troubleshooting documentation.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall7. Look in the correct Odoo CRM view
Verify the CRM record in the view that matches the configured record type and your Odoo version. Odoo’s version 13 website-form documentation says a website form configured to create opportunities can generate CRM records. Newer guidance found outside Odoo’s own documentation describes lead handling when the Leads setting is active, but the available evidence does not establish that behavior for every version or configuration. Check your own version’s CRM settings and views before concluding that no record was created.
Also distinguish the CF7 route from Odoo’s native website form: a native Odoo form can be configured to create a CRM record, but that does not mean an external WordPress form is connected.
When a form appears to work but no lead appears
A successful-looking form response and a missing CRM lead do not uniquely identify the failure. A historical report for Odoo 15.0 Enterprise, opened October 22, 2021, describes a native website form sending an email rather than creating a crm.lead. It is a version-specific report, not evidence that this is a general current cause for CF7 integrations. See the Odoo issue report.
For CF7, continue through the integration checks: confirm a sender is configured, test authentication, verify the model, compare mappings, inspect integration errors, and search the appropriate CRM view. A form response alone cannot tell you which of those stages failed.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
