> For the complete documentation index, see [llms.txt](https://docs.eventnook.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventnook.com/online-registration-setting/clone-event.md). # Clone Event The **Clone Event** feature allows you to quickly duplicate an existing event, saving time when creating similar or recurring events. *** ### 🧭 How to Access 1. Go to appv3.eventnook.com 2. Log in to your **EventNook account** 3. Select your event 4. Navigate to:\ **Settings → Clone Event** {% embed url="" %} *** ### ⚙️ How to Clone an Event 1. Enter a **New Event Title** * The system will auto-fill with “(Copy)” by default * You can rename it based on your new event 2. Select the settings you want to copy: * ✅ **Confirmation Email Template**\ Copies your existing confirmation email setup * ✅ **Thank You Page Message**\ Copies your customized thank you page * ✅ **Invoice / Receipt Settings**\ Copies billing and invoice configurations * ☐ **HTML Content & Behaviour** (optional)\ Copies your site content design and layout 3. Select the **Organization** (if applicable) 4. Click **“Clone Event”** *** ### 🔄 What Gets Cloned Depending on your selection, the following can be duplicated: * Email templates * Thank you page messages * Invoice & receipt settings * Event content and layout (if enabled) *** ### ⚠️ What to Review After Cloning After cloning, make sure to update: * Event **date and time** * Ticket types and pricing * Event description and content * Registration settings * Any outdated information *** ### 💡 Use Case Scenarios * **Recurring events** (e.g., monthly workshops, annual conferences) * **Multi-session events** with similar setup * **Template reuse** for faster event creation * **Testing setup** before launching a live event *** ### ⚠️ Important Notes * Cloning creates a **new separate event** * Changes made to the new event will **not affect the original event** * Always review all settings before publishing *** ### ✅ Best Practices * Use clear naming conventions (e.g., “Event Name – June 2026”) * Only copy necessary settings to avoid outdated content * Double-check payment, email, and registration settings * Test your new event before going live *** Cloning an event helps streamline your workflow and ensures consistency across similar events while reducing setup time. --- # 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://docs.eventnook.com/online-registration-setting/clone-event.md?ask=&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.