> For the complete documentation index, see [llms.txt](https://docs.momocode.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.momocode.de/en/shopware-6/confirmation-mails-for-forms-cms-extension/3.-configuration.md).

# 3. Configuration

As soon as you have created a new form of the CMS extension, a new trigger is automatically provided in the Flow Builder. To activate the confirmation email, you must first create a new flow in the Flow Builder. You can then select the trigger of the form and select "Send email" as the action. In the action settings, you can then select the option "Form confirmation" under "Recipient". This will send the email to the address specified by the sender in the form. It is important that there is a field in the form with the internal name "email", as the confirmation email will then be sent to the address entered in this field.

You can choose any template as an email template. If you want to refer to the data sent by the sender in the template, you can use the same variables that are available in the template for the email to the shop owner. You can copy these from the email template with the type "Custom Form" that was created by the CMS extension.

**Attention:**

If you change the internal name of a form for which a flow has already been configured, you must then reconfigure the flow, as the triggers are based on the internal names of the forms and the old name is then still stored as the trigger of the flow. Such flows are then automatically deactivated as long as they have not been updated.


---

# 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.momocode.de/en/shopware-6/confirmation-mails-for-forms-cms-extension/3.-configuration.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.