Lambda function input format –
currentIntent: It will contain information regarding the intent of the message sent by the user to the bot. It contains
the following keys:
name: intent name (for e.g orderBook, we defined this intent in our previous blog).
slots: It will contain a map of slot names configured for that particular intent, populated with values recognized by
Amazon Lex during the conversation. Default values are null.
confirmationStatus: It provides the user response to a confirmation prompt if there is one. Possible values for this
variable are:
None: Default value
Confirmed: When the user responds with a confirmation w.r.t confirmation prompt.
Denied: When the user responds with a deny w.r.t confirmation prompt.
inputTranscipt: Text input by the user for processing. In the case of audio input, the text will be extracted from
audio. This is the text that is actually processed to recognize intents and slot values.
invocationSource: Its value directs the reason for invoking the Lambda function. It can have the following two
values:
DialogCodeHook: This value directs the Lambda function to initialize the validation of user’s data input. If the intent
is not clear, Amazon Lex can’t invoke the Lambda function.
FulfillmentCodeHook: This value is set to fulfill the intent. If the intent is configured to invoke a Lambda function as a
fulfillment code hook, Amazon Lex sets the invocationSource to this value only after it has all the slot data to fulfill
the intent.
bot: Details of bot that processed the request. It consists of below information:
name: name of the bot.
alias: alias of the bot version.
version: the version of the bot.
userId: Its value is defined by the client application. Amazon Lex passes it to the Lambda function.
outputDialogMode: Its value depends on how you have configured your bot. Its value can be Text / Voice.
messageVersion: The version of the message that identifies the format of the event data going into the Lambda
function and the expected format of the response from a Lambda function. In the current implementation, only
message version 1.0 is supported. Therefore, the console assumes the default value of 1.0 and doesn’t show the
message version.
sessionAttributes: Application-specific session attributes that the client sent in the request. It is optional.
