Receive Lambda Invocation
Use the Receive Lambda Invocation trigger for AWS to start your flow as a Lambda function. The Receive Lambda Invocation trigger can be configured only in blank flows. It must not be used with flows that are created with another trigger.
Trigger Settings
- An app can contain only one Lambda trigger. An app that has a Lambda trigger cannot contain any other triggers including another Lambda trigger. Also, as the Lambda trigger supports only one handler per trigger, it can have only one flow attached to it. However, the apps that contain a Lambda trigger can contain blank flows that can serve as subflows for the flow attached to the Lambda trigger.
- For overriding app properties, use the FLOGO_APP_PROPS_JSON environment variable only. You cannot override app properties using the FLOGO_APP_PROPS_ENV environment variable.
| Field | Description |
|---|---|
| AWS Connection Name | Name of the AWS connector connection you want to use for the flow. |
| Execution Role Name |
(optional) ARN of the role to be used to execute the function on your behalf. The role must be assumable by Lambda and must have CloudWatch logs permission execution role. |
Output Settings
Enter the payload schema for the request received on the Lambda function invocation on AWS.
Map to Flow Inputs
Map the trigger output to the flow input on this tab.
| Field | Description |
|---|---|
| Function | Information about the Lambda function |
| Context | Envelope information about this invocation |
| Identity | Identity for the invoking users |
| ClientApp | Metadata about the calling app |
| API Gateway Request | Displays the elements in the payload schema that you entered on the Output Settings tab. The elements are displayed in a tree format. |
Reply Settings
Enter a schema for the trigger reply in the Reply Data text box.
Map from Flow Outputs
Map the flow output to the trigger reply on this tab.