AWS Lambda

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.

2 actions available

Upstream flow needs custom processing on a payload

Agent calls Get Function to confirm the target function is Active and the configuration matches expectations

Agent calls Invoke Function in RequestResponse mode with the payload as plain JSON

Agent inspects the response for a non-null functionError field

Operations channel gets the invocation summary

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

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

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.

Start building with AWS Lambda

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us