You can create forms with the following sentence -

Create entity user with fields first name, last name, email address and phone number. Show a user form.

Key gotchas -

1. Forms are always built on top of entities. What are entities? Entities are nouns in your context. For example, if you are a grocery delivery business, your entities will be "user", "sku", "order", "route", "warehouse" and so on.
2. Entities you create in Tuneal have NOTHING to do with your backend entities (tables). This is so because when you are creating client applications, you need to think what the user would provide as input, not what your backend structure should be. The two are different problems. One is a usability problem, the other is a database-design problem. This is a critical mistake that many of the other no-code platforms make and it wreaks havoc. So when you are creating entities in Tuneal, always think what would make sense from the usability perspective. As long as you have APIs, you can bridge the input the user provides to your backend schema.
3. Entities are shared across the organisation. If you create an entity called "sku" once in a flow, you can simply use the entity in other flows. No need to create it again.
4. You can create entities by writing - "Create entity sku with fields name, id, image and price."
5. Once you have created an entity, you can create a form on top by writing - "Show a sku form."
6. If you click on the sentence in point 5 above, you will see all the fields of the entity. You can add labels, validations, extra configurations for each field in that popup. (screenshot below)
7. Supported input types are -
   • text
   • textwithsuggestions
   • select
   • checkbox
   • email
   • password
   • date
   • datetime
   • time
   • number
   • tel
   • textarea
   • radio / radiotwo (alternate radio)
   • map
8. For each field in your entity, you can configure the following. For each of these, you can either write static data or create JS expression using any of the application data you need.
   1. Input type - any from point 7 above
   2. Is required?
   3. Label
   4. Show if
   5. Rank - to determine order in which field should appear in a form
   6. Is read only?
   7. Valid if
   8. Invalid message