Think¶

Description¶
This Node is used to re-execute the Flow within one invocation.
Upon reaching this Node, the Flow will stop and then restart executing at the Start Node.
You may specify an input text and input data which will then be treated as a simulated message from the user.
Think NLU
When a Flow gets executed again via a Think Node, the new message will be sent through the NLU pipeline again, finding Slots and matching Intents.
Settings¶
Parameter | Type | Description |
---|---|---|
Text | CognigyScript | A simulated message text from the user. |
Data | CognigyScript JSON | Simulated message data from the user. |
You can select two Advanced options to integrate a Think Node functionality in your Flow:
- Think Text (default setting)
- Trigger Intent
Using the Trigger Intent option, you can re-execute the flow while forcing that a specific intent is found, instead of getting the intent result from our NLU engine. It is exactly the same behaviour as described in Trigger Intent.
You can trigger an intent with a user input like "cIntent:orderFood", then the intent "orderFood" will be triggered. Using the Think Node you can have the same behaviour by choosing the "Trigger Intent" option, and "orderFood" in the "intent to trigger" field.
Alternatives¶
When you need to process user input or other text in the middle of a Flow to retrieve an NLU result, and you do not want to restart the Flow from the Start Node, use the Execute Cognigy NLU Node.