Short answer: Drop the "AWS Lambda → Invoke Lambda Function" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Function Name or ARN function_name | string | Required | Lambda function name, partial ARN, or full ARN. Function must exist in the connected region. |
Event Payload payload | object | Optional | JSON event the function receives. Whatever your handler expects. |
Invocation Type invocation_type | options | Optional | — |
Version or Alias qualifier | string | Optional | Optional version number or alias. Defaults to $LATEST. |
{"function_name": "my-function OR arn:aws:lambda:us-east-1:123456789012:function:my-function","payload": "{{trigger.payload}}","invocation_type": "{{trigger.invocation_type}}","qualifier": "$LATEST"}
{"body": "{ \"message\": \"Hello from Lambda\" }","statusCode": 200}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.