AWS API Gateway Lambda Trigger
Use the AWS API Gateway Lambda trigger to start your flow as a Lambda function using an API Gateway.
Trigger Settings
Field | Description |
---|---|
AWS Connection Name | (Mandatory) Name of the AWS connection that you want to use for deploying the flow as a Lambda connection. |
Execution Role Name | Permission of the Lambda function to execute. The role must be assumable by Lambda and must have CloudWatch logs permission execution role. A default role with the AWS predefined
AWSLambdaBasicExecutionRole permission is created if you do not specify anything in this field.
By default, Cloud watching is enabled. |
API Deploy Stage | Name of the API Gateway deployment stage.
Note: Spaces or special characters are not allowed.
You can use this field to create different deployment stages such as Testing, Production, and so on. You can also create this stage on the AWS console after deployment. |
Method |
The operation which the flow implements. For example - GET, PUT, POST, or DELETE. You can select only one method at a time. |
Path | The resource path for the operation. By default, the path displayed here is the resource path you had entered when you created the flow. |
Output Validation |
When set to True, the incoming data (body, headers, and query parameters) is validated against the configured JSON schema. Default: False |
Output Settings
Map to Flow Inputs
This tab allows you to map the trigger output to flow input.
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 | API Gateway default schema which can be mapped with the schema of AWS API Gateway Lambda trigger |
Reply Settings
Field | Description |
---|---|
Reply Data Schema | The schema used for the reply data of the trigger. Be sure to use straight quotes for element names and values in the schema. |
Map from Flow Outputs
Map the flow output to the trigger reply in this tab.
Field | Description |
---|---|
code | HTTP code |
body | Body of the reply |