FormDexSecure form operations
Try FormDex
FormDexSecure form operations

A product by MeshDex

FormDex is a secure form operations platform for collecting, validating, and routing website submissions. Manage protected endpoints, email notifications, webhook delivery, and submission history from one reliable workspace.

Product

PlatformPricingDocumentation

Access

LoginRegisterReset password

Legal

Privacy PolicyTerms of ServiceRefund PolicyContact Us
  1. Home
  2. Documentation
  3. Integration
  4. Connect WordPress and Contact Form 7
Docs home

Integration guide

Connect WordPress and Contact Form 7

Install the FormDex connector, route one or many CF7 forms, preserve dynamic fields, and inspect delivery failures without editing theme files.

Step by step

1

Install the connector

Download formdex-cf7.zip from the FormDex Integrate tab. In WordPress, open Plugins › Add New › Upload Plugin, upload the ZIP, install it, and activate FormDex for Contact Form 7.

2

Choose routing

Open Settings › FormDex CF7. Use the default destination plus “Send all” when many CF7 forms belong to one FormDex form. Use per-form rows when different CF7 form IDs must reach different FormDex endpoints.

3

Paste credentials

Copy the exact endpoint and API key from FormDex. The connector stores the key in WordPress settings and sends it through the X-API-Key header over HTTPS.

4

Match the honeypot

Enter the exact FormDex honeypot field name. The connector adds this field with an empty value; a mismatch removes the intended protection.

5

Test and inspect

Submit the real CF7 form, confirm the entry in FormDex Submissions, then visit the debug URL shown at the bottom of Settings › FormDex CF7 to inspect the latest HTTP status and response.

Honeypot in this integration

Where it belongs and who validates it

In Settings › FormDex CF7, enter the exact Honeypot field name shown in FormDex Protection settings. You do not add a visible CF7 input: the connector automatically sends that key with an empty value. This exact-name match is required for the configured trap to remain consistent.

Read the honeypot fundamentals →

Working example

Example routing plan

Default destination
Endpoint: https://YOUR_FORMDEX_DOMAIN/api/forms/FORM_ID
API key: YOUR_API_KEY
Send all CF7 forms: enabled
Honeypot field: company

Optional per-form override
CF7 form ID: 456
Endpoint: https://YOUR_FORMDEX_DOMAIN/api/forms/ANOTHER_FORM_ID
API key: ANOTHER_API_KEY

Troubleshooting

401 Invalid API key

Replace the saved key with the current key from FormDex; rotate only when you can update WordPress immediately.

403 Origin not allowed

Add the exact WordPress site origin, including https:// and excluding paths.

Unknown field validation

Add the field to the schema or enable Dynamic fields.

No FormDex request

Confirm the CF7 form ID is mapped or enable the default route for all forms.

Before you start

  • • An active Contact Form 7 installation
  • • A FormDex form endpoint and active API key
  • • The production WordPress origin added in FormDex Protection settings
  • • Dynamic fields enabled when CF7 sends keys not listed in the FormDex schema

Production notes

  • • The connector forwards original CF7 field names and adds wordpress_form_id, wordpress_form_title, and wordpress_site_url.
  • • Checkbox or multi-value fields are converted to comma-separated strings.
  • • A successful FormDex submission uses one credit. Keep WordPress and FormDex notification behavior intentional to avoid duplicate emails.
View the complete integration overview →