Connect Contact Form 7
Connect an existing WordPress Contact Form 7 form to in-chat collection and submission.
On this page
Before you configure the connection
Use an existing Contact Form 7 form on your WordPress site. Ask its maintainer for the form ID, public feedback endpoint, accepted field names and choice values, required hidden values, and reCAPTCHA site key when used.
Runs Agents collects and sends the configured fields. It does not automatically import the WordPress form definition. Changing a WordPress field does not update the Runs Agents questionnaire.
Create a reusable connection
In Form connections, choose Add connection, select Contact Form 7, give the connection a recognizable name, and supply the configured reCAPTCHA site key. The site key is public browser configuration; do not paste a reCAPTCHA secret key into that field.
A connection can deliver multiple forms. Each form still has its own endpoint and field mapping.
Set the form endpoint
In Forms, create or edit an In chat form and select the connection. Set Submission endpoint to the receiving Contact Form 7 feedback URL. A typical structure is:
https://www.example.com/wp-json/contact-form-7/v1/contact-forms/123/feedback
This is an example. Obtain the actual endpoint from the website maintainer. The page URL where a visitor normally sees the form is not its submission endpoint; put that page in Website URL if you want a fallback link.
Map fields exactly
For each receiving field, add the exact Form field name in Runs Agents. For example:
| Receiving field | Runs Agents configuration |
|---|---|
| your-name | Ask the visitor, Plain text, required. |
| your-email | Ask the visitor, Email address, required. |
| your-message | Ask the visitor, Free text, multi-line. |
| inquiry-type | Choice with the receiving form's exact option values. |
These are illustrative field names. Use the names from your form. Use fixed or copied fields only when the destination actually expects them. Verify the receiving form's own required fields and validation rules.
Configure spam protection
Have the website maintainer check that the reCAPTCHA configuration accepts the origin on which the chatbot runs, along with the form provider's setup. A successful website form does not by itself prove that the same configuration accepts chatbot delivery.
Runs Agents cannot bypass a receiving site's spam filters, blocked endpoint, authentication requirement, or incompatible security policy. Diagnose the actual destination response with the website maintainer.
Test the entire submission
- Make the form visible for your test language.
- Open Preview and select the form.
- Agree to assistance, provide synthetic answers, and correct at least one answer.
- Review and confirm once.
- Check the chatbot's result, the portal's saved answers, and receipt in WordPress or its configured delivery destination.
- Verify any expected notification email separately.
Repeat after changing endpoint configuration, field names, choices, required fields, translation settings, or reCAPTCHA. See Troubleshooting for failed or uncertain submissions.