> 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/1.-description.md).

# 1. Description

When a visitor submits a form (of the CMS extension), by default only the shop owner receives an email with the summary. This app gives you the option of sending automatic confirmation emails to the sender when they have completed and sent the form.

The configuration for the confirmation emails takes place via the Flow Builder. The app provides a trigger for the flow builder for each individual form. You can therefore create a separate flow for each form, select one of the triggers provided by the plugin and then configure the email dispatch as the action. You have various options for sending emails, including the confirmation email to the sender. The email is then sent to the address that the sender has entered in the email field of the form.

You can create any email templates via Shopware Administration and select them for email dispatch in the Flow configuration. In the email templates, you can access the values filled in by the sender if you want to refer to them in the email.


---

# 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/1.-description.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.