> 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/install-router-on-framer.md).

# Framer

Add a Form Router to the Framer page containing your form.

1. [Map the form](/routing-forms/overview.md) in Distro, including its selector and field names.
2. Connect the form to the router, configure its rules and event type, then test and activate the router.
3. Open **Install Router** and copy the installation code.
4. In Framer's project settings, open **Custom Code**, choose **Add Script**, and add the script for the intended page. Place it at the end of the body, after the form markup.
5. Publish the Framer site and test the form on the published page.

Use the actual router ID and form selector from Distro. A selector such as `#contact-form` must identify the intended form on the published site.

Framer's custom-code settings control where and when the script runs. See [Framer's custom code guide](https://www.framer.com/help/articles/how-to-add-custom-code/) for its current editor controls.

Confirm the original form submission still reaches its destination as well as checking the scheduler. A custom JavaScript form or provider integration can behave differently from a standard HTML form. See [Custom HTML forms](/routing-forms/custom-html-form.md) for the standard handler's submission behavior.


---

# 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/install-router-on-framer.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.