I have a telegram message (voice or text) coming in from (customer or employees). The workflow must grab the message determine (voice/text), realize my ID (expand to employees later) the categorize into send invoice/- email/pay query/H7S meeting and send email. *Customer side is working perfect. TIA
What is the problem?
When my message comes in it doesn’t distinguish between “Send an Email” “Send an Invoice” “Pay Query” etc.
What have you tried so far?
When using a filter it didn’t work and always went to customer until I saw I had " " with Text operator Equal to so when I remove " " for numeric I started coming to my line, it process the message voice and text but now whether I used only the filter or even added the AI toolkit module it still can recognize the message topic as send an email, invoice etc and then it just stops there because its almost like it doesn’t know what to do with the message. Last 6 images will be what i text for example and how it sees and process the message module per module so you can see the output
Firstly - you’re passing in the entire array to your filter - not just the value. So the filer is not going to match the array.
Secondly - You’ve currently got the filter set to EQUALS “Send Email” - so unless the text matches “Send Email” exactly - including the “ “ - then it will not match.
Where is the first point that includes the variable options?
I see in the initial webhook the Text variable includes “send an email” (without the quotes)
If this text variable will include the different options then you could can use Text from this module as the variable in the filter and use Text Operator contains Send an email as the filter settings.
Either that or you can pass the Intent Value from ChatGPT into the filter. In this case the filter value would could be Text Operator EQUALS Send_Email to match the output of ChatGPT.
To take the value from ChatGPT directly (rather than a JSON Parse module after it) select YES to Parse JSON Response in ChatGPT. This will make the Intent Value available to add to the filter directly. This will also save you an module/operation.
I’ve run into similar errors when my filter blocks didn’t match the exact field names or types coming from the previous step. Once I double-checked the inputs and made sure each option referenced a valid attribute, the workflow ran without issues. A small mismatch can break the whole chain, so reviewing each connection usually reveals where things went wrong.
What is your goal?
What is the problem?
What have you tried so far?
Screenshots: scenario setup, module configuration, errors
