> For the complete documentation index, see [llms.txt](https://docs.eventflowapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventflowapp.com/eventflow-cms/forms-settings/duplicating-a-form.md).

# Duplicating a form

Learn how to duplicate a form with or without its webhook integrations.

Administrators can duplicate an existing form from the **Manage Forms** table.

1. Find the form and open its three-dot action menu.
2. Choose one of the following:
   * **Duplicate** creates a copy without any webhooks.
   * **Duplicate with webhooks (number)** creates a copy containing the form’s attached webhooks. The number in brackets shows how many webhooks will be copied.
3. Open the new form, which is titled with **(Copy)** and initially unpublished.
4. Review its settings and integrations before publishing it.

When webhooks are copied, Eventflow updates references to the duplicated form fields. The external destination and other webhook configuration are retained, so review the webhook URL, trigger rules, payload and authentication settings, then test the integration before collecting live submissions.

**Duplicate with webhooks** is unavailable when the original form has no webhooks.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.eventflowapp.com/eventflow-cms/forms-settings/duplicating-a-form.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.