> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemmodeler/flowcharts/user-interaction.md).
# User Interaction
The user interaction node is used when there is an interaction with the user. These nodes translate into forms or pages where a wide range of user interaction components can be used (forms, lists, buttons, images, charts, etc.).
### Properties
The properties are accessed by selecting the node. The properties of the selected node are shown in the properties pane on the right hand side of the screen.
| **Item** | **Description** |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name** | Enter the name of the user interaction node This name also appears beneath the node on the flowchart canvas. |
| **Default button exit** | This dropdown list shows al defined button exits for this user interaction. When selected, this exit will be used when the user hits the 'enter' anywhere on the page. It is possible that this feature is disabled in the design template. This feature can also be enabled by using the "SetEnterKeyAction" widget. |
| **Show as overlay** | When this checkbox is checked, the user interaction is shown as an overlay. An overlay is a form that resides on top of you application (like a popup). You cannot access the rest of the application without closing the overlay. |
| **Exits** | These are the exits that are triggered by a button in the user interaction form itself (e.g. \`Save\` or \`Cancel\`). Whenever a button is added to the interaction node with a "Follow exit" event an exit is added to this list. Another option is adding an exit via the "New button exit" button. Exits added using this method will be visible when a button is dragged to the [Template editor ](/platform/template-editor/interaction-template-editor.md)canvas. |
| **Event Flowcharts** | This is only visible if the interaction template contains buttons that Execute a flowchart. You can find usages of these flowcharts through the context menu by right clicking the event items.
|
The `Edit template` button at the bottom of the properties form works the same as double-clicking the node: it opens the user interaction template editor.
### User Interaction Node Editor
The editor is where you create the form / interaction that is needed to communicate with users of the application. This editor is also referred to as the "template editor". This template editor has to many features to explain in this chapter. Therefore a separate section in this documentation is dedicated to the [template editor](/platform/template-editor/interaction-template-editor.md).
---
# 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:
```
GET https://docs.wem.io/platform/wemmodeler/flowcharts/user-interaction.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.