- Reordering Table columns - an easy way to lookup a specific record field based on a user response, and validate if there is a record that exists or not. Example: we ask what their email is, and then we check the record if that email exists, and if not: create a new record. Currently you can only look up by ID, or pull in the whole record, and there is no intuitive way to figure out how to use that record, and the generative code doesn't know what a "table" is. - tables to dynamically update the knowledgebase, but only have certain records go to certain knowledge bases. Example: User asks a question, AI asks three followup questions for context, and then gives it's best shot at answering it. I only want the accepted answer to go in, and not the context fields that are particular to the user... and I also don't want unanswered questions to go in either. And depending on the topic, I would only want certain records to go to certain knowledge bases. If topic 1: KB 1. - An option in the get card to retrieve the first record that matches. Use case: A table of user questions, i want to have the chatbot lookup records with the answer field empty, and then display just the question field, and possibly 1 or 2 other fields thatgive more context to the question. (i.e. follow up questions the bot asked the user)

Sounf like a good useacase👍

🆙🆙🆙⬆️