Dynamic Input feature

What you show is how I'd do it! What's wrong with it?

Hi @Baptiste thanks for responding! I want to make single input field which will detects the type of input value, and change logic depends on input type.

Here is an example from my life - a bot in bank support after a request from a user to "get an account statement" should send it for processing and after the event is completed by the server notify the user that the statement is ready. At the same time it should respond to other requests while the statement is being generated.

There are other, but more specialized examples: when generating several pictures in midjourney/dall-e/sd, and others (and any content in general), the user can both click on the picture he likes, and text the correction for the prompt, without clicking any additional buttons. Similar problems will 100% exist when support for telegram bots is added, in which there is no lock on the type of events (the user can both click a button at any time, and write something at the same time)

In general, I still see the strong side of Typebot as a tool for "quickly make a form as a chat" (for which the tool is literally the best among competitors), and the weak side that it is hard to use it in tasks more complex than a form for data collection. This feature with dynamic event types could help extend the functionality of the tool for complex services within chat interface

Ok I totally get that. That's a very good point.

I'm still not sure what form it should take then, you provide several very different use cases here

That's good question, no idea honestly 🤔

I currently working on Typebot runtime based on golang, and i might not understand how exactly original runtime working, so need to think how percisely it might work at least in UI. In runtime i implemented it super easily with pre-validation of allowed input type (if there is no default flow) and switch/case