Execute Cognigy NLU - Cognigy Documentation

Description

The Execute Cognigy NLU Node executes the Cognigy NLU pipeline and updates the Input or Context object. For example, you can use a Code Node to modify a user’s input and subsequently execute the NLU pipeline with the modified user input to obtain fresh NLU results. The Execute Cognigy NLU Node doesn’t trigger standard responses in Intents nor execute the Flow based on a triggered Intent.

Settings

Parameter	Type	Description
Text	CognigyScript	Use `{{ input.text }}` or the Answer Token.
Data	JSON	Data to send to the NLU pipeline. Can be used to modify `input.data`.
Mode	Select	Three modes are available to control how the output of the NLU pipeline is stored. The available selections are: Overwrite — overwrites the Input object with the result of the NLU pipeline. Input — stores the result of the NLU pipeline in the Input object under the key specified in the Input Key to write to field. This option is useful if you are running the NLU pipeline a second time with different text than the user input. Context — stores the result of the NLU pipeline in the Context object under the key specified in the Context Key to write to field.
Context Key to write to	CognigyScript	This field appears if the Write to Context option is selected. Store the result of the NLU Pipeline in the Context object.
Input Key to write to	CognigyScript	This field appears if the Write to Input option is selected. Store the result of the NLU Pipeline in the Input object.

Advanced

Parameter	Type	Description
Parse Intents	Toggle	Determine whether Cognigy should parse Intents in the child Flow. The parameter is enabled by default. If the parameter is enabled, the NLU pipeline reparses the Intents in the target Flow, using either input.text or the Optionally Injected Text. The NLU pipeline parses the input into the child Flow, and the NLU pipeline then scores this text using the available Intents in the child Flow, not based on Intents in the parent Flow.
Parse System Slots	Toggle	Determine whether Cognigy should parse System Slots in the child Flow. This parameter is enabled by default. If the parameter is enabled, the NLU pipeline reparses the Slots in the target Flow, using either input.text or the Optionally Injected Text. The NLU pipeline parses the input into the child Flow, and the NLU scores this text using the available Slots in the child Flow, not based on System Slots in the parent Flow.
Parse Slots	Toggle	Determine whether Cognigy should parse Slots in the child Flow. This parameter is enabled by default. If the parameter is enabled, the NLU pipeline reparses the Slots in the target Flow, using either input.text or the Optionally Injected Text. The NLU pipeline parses the input into the child Flow, and the NLU scores this text using the available Slots in the child Flow, not based on Slots in the parent Flow.
Find Type	Toggle	Identify the type of user input. This parameter is enabled by default. If the user’s answer contains words associated with a particular type of question, the system identifies the type of user input accordingly. The following types can be recognized: whQuestion — questions about specific details that include question words. For example, questions with `who`, `whom`, `when`, `where`, `why`, `whose`, or `what`. ynQuestion — questions that are answered with yes or no. These questions contain auxiliary verbs. For example, questions with `am`, `are`, `is`, `was`, `were`, `do`, or `does`. howQuestion — questions that start with the word `how`. Greeting — common expressions used to greet someone. For example, `hi`, `hello`, `greetings`, `hey`, or `howdy`. BGreeting — common expressions used to say farewell or goodbye. For example, `bye`, `goodbye`, or `see you`. nAnswer — negative responses or negations, including `no`, `nope`, `na`, `nah`, `not`, or `false`. pAnswer — positive responses or confirmations, such as `yes` or `super`. Statement — any other user responses. If the system cannot identify the type of user input or the Find Type is disabled, it classifies it as a statement. Note that certain user responses may be ambiguous and could potentially be misinterpreted by the agent. For example: The user input `Why not` is interpreted as a whQuestion. The user input `My name only, yes` is interpreted as a Statement. The user input `Could you help me?` is interpreted as a Statement
Process Intent Default Reply	Toggle	By default, this parameter is disabled, so the default reply isn’t processed. If the option is enabled, the default reply is handled in the same manner as when triggered by means other than the Execute Cognigy NLU Node.

Alternatives

When you need to process user input or other text in the middle of a Flow to retrieve an NLU result, and you want to restart the Flow from the Start Node, use the Think Node.

Last modified on November 11, 2026