# Forms

Note

There is an in-depth tutorial [here](https://blog.rasa.com/building-contextual-assistants-with-rasa-formaction/) about how to use Rasa Forms for slot filling.

### [Configuration File](https://legacy-docs-v1.rasa.com/1.9.0/core/forms/#configuration-file)

### [Form Basics](https://legacy-docs-v1.rasa.com/1.9.0/core/forms/#form-basics)

Using a `FormAction`, you can describe _all_ of the happy paths with a single story. By “happy path”, we mean that whenever you ask a user for some information, they respond with the information you asked for.

```yaml
## happy path
* request_restaurant
    - restaurant_form
    - form{"name": "restaurant_form"}
    - form{"name": null}
```

### [Custom slot mappings](https://legacy-docs-v1.rasa.com/1.9.0/core/forms/#id4)

### [Validating user input](https://legacy-docs-v1.rasa.com/1.9.0/core/forms/#id5)

After extracting a slot value from user input, the form will try to validate the value of the slot.

### [Handling unhappy paths](https://legacy-docs-v1.rasa.com/1.9.0/core/forms/#id6)

Of course your users will not always respond with the information you ask of them. Typically, users will ask questions, make chitchat, change their mind, or otherwise stray from the happy path.

### [The requested_slot slot](https://legacy-docs-v1.rasa.com/1.9.0/core/forms/#id7)

The slot `requested_slot` is automatically added to the domain as an unfeaturized slot. If you want to make it featurized, you need to add it to your domain file as a categorical slot.

### [Handling conditional slot logic](https://legacy-docs-v1.rasa.com/1.9.0/core/forms/#id8)

Many forms require more logic than just requesting a list of fields.

### [Debugging](https://legacy-docs-v1.rasa.com/1.9.0/core/forms/#id9)

The first thing to try is to run your bot with the `debug` flag.