Option2: If you want Amazon Connect to interact directly to Lambda, you can use Lex to collect userSSN and secretWord and then build a separate Lambda function that Amazon Connect calls directly using an "Invoke AWS Lambda Function" step to perform the database lookup. From there, Amazon Connect can access that value as $. Option1: You can configure Lex to insert the Account Balance into a slot called "AccountBal", then "return parameters to client".
$.Lex.SessionAttributes.(sessionAttributeKey).In order for Amazon Connect to read back something from Lex, you will need to use one of the following in your Play prompt step: Lex is calling Lambda, so any response you get back to Amazon Connect will be coming from Lex, not Lambda. In your case, Amazon Connect is interacting with Lex. $.External is only used if Amazon Connect is calling upon a Lambda function directly. Your Amazon Connect contact flow appears to be referencing $.External.(something) after matching the "ReasonForCalling" intent. Invoking the function through Amazon Connect results in an Error.Īny ideas on how to save the return from Lambda in Connect with proper formatting? * Updated to add updated lambda code and Lex configuration image. Lambda function returns properly when testing Lex chatbot.
0 kommentar(er)
