Thanks to @flat-plumber-75402, i have found that using the query knowledge base card is better than querying straight from the raw input card. i want to add a fallback to the node if it cant find an answer in the Kb, but since adding the text card that displays the KB answer, it doesnt go straight to my fallback node, it first says "undefined" and then moves onto the fallback. is there a way around this? i set the fallback condition to "workflow.kbAnswer === undefined" because if i use "!turn.KnowledgeAgent.responded" and the answer is found, it will provide the answer but still head to the fallback node. Any help would be greatly appreciated @User https://cdn.discordapp.com/attachments/1223597218154418226/1223597218720776202/image1.png?ex=661a6eb6&is=6607f9b6&hm=590b511eea7391cdfe5ee9ec8b6bb49432e9639580c4a2cf04beca161de0f645& https://cdn.discordapp.com/attachments/1223597218154418226/1223597219018440795/image2.png?ex=661a6eb6&is=6607f9b6&hm=edc30a749be444d20c5368eff2d36429ed3422418b65429974f9a116d738016c&

Hey there, You should use !turn.KnowledgeAgent.answer

Thanks, i’ve watched the first one, but can’t seem to think of a way to get rid of the “undefined” response before the fallback happens? I didn’t have this issue before when i was using the raw input to query the Kb. but that was causing issues with finding the right data, so i switched to the query KB card

Put your text card with @workflow.kbAnswer after the expression card that checks if it found an answer, but before the always card

will give it a go 👍 thank you boss

You are very welcome