Share feedback, ideas and get community help

Updated last week

Message buffer: Has anyone implemented it? Can you help?

At a glance
The community member wants to create a message buffer in Typebot before sending it to an LLM (Large Language Model). The comments suggest creating a variable to store the messages, and then sending the list of messages to the LLM. However, the community member is unable to find a way to exit the loop after a certain time, such as 10 seconds. The community members discuss the use case, where the community member has WhatsApp connected to Typebot, and the user can send "chopped" messages, so the community member needs to implement a buffer routine to send the complete message to the LLM. The community members conclude that there is currently no timeout feature for the Input block in Typebot, and the only solution is to let the user know to send their message in a single message for the bot to respond, which is a fair approach.
I would like to create a message buffer into Typebot before sending to LLM.
Marked as solution
The only thing that would help the user understand the UX better is to let them know to say what they want to say in 1 single message, for the bot to respond, which is fair
View full solution
A
j
7 comments
You could create a new variable called message_buffer that's an empty list, and each new message would be appended (pushed) to that list, and then you'd give that list to your LLM (either raw ["string", "string"...] or concatenated/joined "string string" with your custom delimiter, a space or a line break for example).
Sounds close to your expected end result?
Not really, because I didn't find a way to get out of the loop after some time, 10s for example, you know?
What's your use case then? What do you want to happen and when? How do you picture a "message buffer" to work for your use case?
I have WhatsApp connected to typebot, which cannot prevent the user from sending "chopped" messages, so I need to implement a buffer routine, and only then send it to LLM to process. Got it?
Aah, I get it now. Sadly, there is currently no timeout feature for the Input block.
It's been requested many times, so it's maybe in the project roadmap.
Because your use case would required you to have an Input block, with a set timeout. When the timeout is not reached, you loop back to the Input so it keeps asking the user for their input, otherwise if the timeout is reached, send the messages to the LLM.
So, you could only do that if/when the feature gets implemented. I can't think of a workaround for now
The only thing that would help the user understand the UX better is to let them know to say what they want to say in 1 single message, for the bot to respond, which is fair
Add a reply
Sign up and join the conversation on Discord