--- title: "AWS Lambda Integration" description: "Invoke AWS Lambda functions as a step in any flow. Agents run functions synchronously to compute or transform data, fire-and-forget for background work, or dry-run to validate parameters before going live." url: https://flowrunner.ai/integrations/lambda-service date_modified: 2026-08-01T02:40:32-07:00 --- # AWS Lambda [Developer Tools](https://flowrunner.ai/integrations/category/developer-infrastructure) Invoke AWS Lambda functions as a step in any flow. Agents run functions synchronously to compute or transform data, fire-and-forget for background work, or dry-run to validate parameters before going live. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 2 actions · API key · available [AWS Lambda website](https://aws.amazon.com/lambda/) · [Platform Documentation](https://docs.aws.amazon.com/lambda/latest/dg/welcome.html) · Capability data verified 2026-06-27 1. Upstream flow needs custom processing on a payload 2. Agent calls Get Function to confirm the target function is Active and the configuration matches expectations 3. Agent calls Invoke Function in RequestResponse mode with the payload as plain JSON 4. Agent inspects the response for a non-null functionError field 5. Operations channel gets the invocation summary 6. Repeated function errors get routed to the on-call engineer with the payload, statusCode, and error details ## What This Integration Enables Agents invoke Lambda functions in three modes. RequestResponse waits for the result and returns the parsed payload, so the agent can use the output downstream. Event fires-and-forgets, returning as soon as the service accepts the request, which fits background processing. DryRun validates parameters and permissions without running the function, which fits pre-flight checks. Get Function inspects the function's runtime, handler, memory, timeout, state, and ARN, which lets the agent confirm readiness or detect configuration drift before invoking. The connector covers Lambda invocation and inspection; the flow decides what payload to send, what to do with the response, and when a function error should pause the line. ### Without FlowRunner **Ad-hoc Lambda calls in glue code**: Each consumer maintains its own AWS SDK setup, signing, and error handling **Silent function errors**: A function error returns a 200 with an error envelope that callers often miss **Cross-account access via shared secrets**: One-off scripts hold IAM credentials and rotate inconsistently ### With FlowRunner **Lambda as a flow step**: Invoke Function is a node in a workflow with retries, error routing, and observability **Errors surfaced as flow exceptions**: A non-null functionError lifts the call into an exception path the agent can route **One configuration for both auth modes**: API Key and IAM Role are selected per-flow; the same connector serves single- and cross-account invocations ## Use Case Scenarios ### Inline Compute Step A workflow needs custom enrichment that does not fit any out-of-the-box connector. The agent calls Invoke Function in RequestResponse mode with the input data as plain JSON. The function runs, returns its result, and the agent passes the parsed payload to the next step. Lambda becomes the inline-compute escape hatch that keeps the rest of the flow declarative. ### Queue-Driven Background Processing The agent receives a batch of work items from SQS, then for each item calls Invoke Function in Event mode so the function processes the item without blocking the flow. The agent deletes the SQS message immediately and moves to the next item. A separate flow watches the function's CloudWatch logs or DynamoDB-backed status table for completions. ### Pre-Flight Validation Before a Production Run Before a production deployment fires its first real invocation, an ops flow calls Invoke Function in DryRun mode to validate the invoker has permission and the payload shape is accepted. Get Function confirms the configuration matches the release notes. If either check fails, the deployment pauses and the on-call engineer is notified before any real traffic hits the function. ## Human-in-Loop Highlight A function error is the exact place an agent should stop and ask. The agent invokes the function, inspects the response, and if functionError comes back non-null, it pauses. It posts to the on-call channel: "Lambda \[name\] returned functionError \[type\] on payload \[reference\]. statusCode \[code\]. Retry, skip this item, or pause the flow?" The engineer decides. The agent does the durable thing: it stops the loop rather than retrying into a tight error cycle that costs money and corrupts the downstream state. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 2 actions ### Invocation 1 - **Invoke Function** Invokes a Lambda function. RequestResponse mode waits for and returns the parsed payload; Event mode fires-and-forgets; DryRun mode validates parameters without running the function. The response includes statusCode, functionError (non-null when the function raised an error), and the parsed payload. ### Inspection 1 - **Get Function** Inspects a Lambda function's runtime, handler, memory, timeout, state, and ARN. Used to confirm readiness before invoking or to detect configuration drift against a release manifest. ## Frequently Asked Questions ### What can FlowRunner do with AWS Lambda? FlowRunner agents can run Get Function and Invoke Function in AWS Lambda. ### Does connecting AWS Lambda to FlowRunner require OAuth? No. AWS Lambda connects to FlowRunner with an API key, no OAuth flow required. ### Can AWS Lambda trigger a FlowRunner workflow automatically? AWS Lambda doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at AWS Lambda?** This integration exposes AWS Lambda to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/lambda-service. Site index: https://flowrunner.ai/llms.txt