Grant Connect Customer access to your AWS Lambda functions

Publisher

Amazon Web Services

URL

https://docs.aws.amazon.com/connect/latest/adminguide/connect-lambda-functions.html

Published

unknown

Updated

unknown

Accessed

2026-10-02

HTTP status

200

License

AWS documentation, all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• An AWS Lambda function must be added to the Amazon Connect instance (console, Flows page, AWS Lambda section) before a flow can select it; adding it there for a same-Region function also adds the resource permissions that let Amazon Connect invoke it. in context
• Callers hear silence while a Lambda function invoked from a flow is running. in context
• Amazon Connect limits a sequence of Lambda functions in a flow to 20 seconds in total and times out with an error when the total is exceeded; putting a Play prompt block between functions breaks up the chain. in context
• To call a Lambda function in another Region or account, enter its ARN in the block and add a resource-based policy on the function with principal connect.amazonaws.com, source account set to the instance's account and source ARN set to the instance ARN. in context
• The flow takes the Error path for a Lambda call when Lambda cannot be reached, the function throws an exception, the response is not understood, or the function runs longer than the limit. in context
• A $.External reference to Lambda output always resolves against the most recently invoked function, so a value needed after a later Lambda call must first be saved as a contact attribute or passed as a parameter. in context
• Lambda return values used directly through $.External are not included in contact records; only values copied into contact attributes with Set contact attributes are. in context
• A Lambda response returned to an Amazon Connect flow must be smaller than 64 KB of UTF-8 data. in context
• If a flow's Lambda invocation is throttled, hits a general service failure (500), or returns an error, Amazon Connect retries up to three times within the timeout and then routes the contact down the Error branch. in context
• According to the Lambda integration guide page, when a synchronous Lambda call exceeds the block's timeout the contact routes down the Error branch. disputed in context

Cite this source record

APA

WarmTransfer. (2026, October 2). Grant Connect Customer access to your AWS Lambda functions. WarmTransfer. https://warmtransfer.net/knowledge/sources/aws-connect-lambda-functions

BibTeX

@misc{warmtransfer-aws-connect-lambda-functions,
  title  = {Grant Connect Customer access to your AWS Lambda functions},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/aws-connect-lambda-functions},
  note   = {Amazon Web Services, accessed 2026-10-02}
}