View source: R/lexmodelsv2_operations.R
lexmodelsv2_create_intent | R Documentation |
Creates an intent.
See https://www.paws-r-sdk.com/docs/lexmodelsv2_create_intent/ for full documentation.
lexmodelsv2_create_intent(
intentName,
description = NULL,
parentIntentSignature = NULL,
sampleUtterances = NULL,
dialogCodeHook = NULL,
fulfillmentCodeHook = NULL,
intentConfirmationSetting = NULL,
intentClosingSetting = NULL,
inputContexts = NULL,
outputContexts = NULL,
kendraConfiguration = NULL,
botId,
botVersion,
localeId,
initialResponseSetting = NULL,
qnAIntentConfiguration = NULL
)
intentName |
[required] The name of the intent. Intent names must be unique in the locale that contains the intent and cannot match the name of any built-in intent. |
description |
A description of the intent. Use the description to help identify the intent in lists. |
parentIntentSignature |
A unique identifier for the built-in intent to base this intent on. |
sampleUtterances |
An array of strings that a user might say to signal the intent. For example, "I want a pizza", or "I want a {PizzaSize} pizza". In an utterance, slot names are enclosed in curly braces ("{", "}") to indicate where they should be displayed in the utterance shown to the user.. |
dialogCodeHook |
Specifies that Amazon Lex invokes the alias Lambda function for each user input. You can invoke this Lambda function to personalize user interaction. For example, suppose that your bot determines that the user's name is
John. You Lambda function might retrieve John's information from a
backend database and prepopulate some of the values. For example, if you
find that John is gluten intolerant, you might set the corresponding
intent slot, |
fulfillmentCodeHook |
Specifies that Amazon Lex invokes the alias Lambda function when the intent is ready for fulfillment. You can invoke this function to complete the bot's transaction with the user. For example, in a pizza ordering bot, the Lambda function can look up the closest pizza restaurant to the customer's location and then place an order on the customer's behalf. |
intentConfirmationSetting |
Provides prompts that Amazon Lex sends to the user to confirm the completion of an intent. If the user answers "no," the settings contain a statement that is sent to the user to end the intent. |
intentClosingSetting |
Sets the response that Amazon Lex sends to the user when the intent is closed. |
inputContexts |
A list of contexts that must be active for this intent to be considered by Amazon Lex. When an intent has an input context list, Amazon Lex only considers using the intent in an interaction with the user when the specified contexts are included in the active context list for the session. If the contexts are not active, then Amazon Lex will not use the intent. A context can be automatically activated using the For example, if there are two intents with different input contexts that respond to the same utterances, only the intent with the active context will respond. An intent may have up to 5 input contexts. If an intent has multiple input contexts, all of the contexts must be active to consider the intent. |
outputContexts |
A lists of contexts that the intent activates when it is fulfilled. You can use an output context to indicate the intents that Amazon Lex should consider for the next turn of the conversation with a customer. When you use the |
kendraConfiguration |
Configuration information required to use the
|
botId |
[required] The identifier of the bot associated with this intent. |
botVersion |
[required] The version of the bot associated with this intent. |
localeId |
[required] The identifier of the language and locale where this intent is used. All of the bots, slot types, and slots used by the intent must have the same locale. For more information, see Supported languages. |
initialResponseSetting |
Configuration settings for the response that is sent to the user at the beginning of a conversation, before eliciting slot values. |
qnAIntentConfiguration |
Specifies the configuration of the built-in |
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.