> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/routing-forms/contact-form-7.md).

# Contact Form 7

Connect a WordPress Contact Form 7 form to a Distro Form Router. Distro listens to the selected form's `.wpcf7` wrapper, so other forms on the page do not trigger that router.

## Connect and install

Create a [form mapping](/routing-forms/overview.md) with a stable selector for the form or its wrapper and the actual input names. Select it under **Form Submission → Connected form**, then configure, test, and activate the router.

Open **Install Router** and select **WordPress Contact Form 7**. Add the snippet on the page containing the form:

```html
<script src="https://app.distro.so/inbound.js"></script>
<script>
  window.distro = new Distro({
    routerId: "YOUR_ROUTER_ID",
    formType: "contactform7"
  });
  distro.schedule("#your-contact-form");
</script>
```

Replace the router ID and selector. The selector must identify the intended form or its Contact Form 7 wrapper.

## Verify

Distro listens for the wrapper's `wpcf7submit` event. This is a submission event, not proof of successful mail delivery. Check validation and mail delivery alongside routing, including invalid, qualified, and unqualified submissions.

Confirm the expected answers in **Routing Logs**, and verify that submitting another Contact Form 7 form on the same page does not route through this installation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.distro.so/routing-forms/contact-form-7.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.