Pipedream AWS Lambda steps in n8n
Updated 2026-10-21 · 3 min read · n8n: AWS Lambda (Native n8n node)
Teams that use Pipedream next to AWS often keep heavy logic in Lambda: a workflow receives a webhook, calls a function for the work Pipedream's step limits could not handle, and posts the result. n8n has a native AWS Lambda node that invokes functions; the rest of the AWS app maps to sibling nodes (S3, SQS, SNS).
The n8n side
AWS Lambda node (n8n-nodes-base.awsLambda), operation Invoke:
- Function: chosen from the list of functions in the credential's region.
- Qualifier: version or alias (default
$LATEST). - Invocation Type: Wait for Results (synchronous,
RequestResponse) or Continue Workflow (asynchronous,Event). - JSON Input: the payload.
On synchronous calls the function's response arrives as { result: … } on the item. There is no Lambda trigger node; to start an n8n workflow from Lambda, have the function POST to an n8n Webhook.
What maps where
Pipedream (app aws) |
In n8n | Status |
|---|---|---|
| Lambda - Invoke Function | AWS Lambda → Invoke | manual |
| Lambda - Create Function | HTTP Request to the Lambda API, or CI/CD | manual |
| SQS - Send Message | AWS SQS → Send Message | manual |
| SNS - Send Message | AWS SNS → Publish | manual |
| S3 - Upload Files | AWS S3 → File → Upload | manual |
| DynamoDB - Put Item | AWS DynamoDB → Item → Create or Update | manual |
| New S3 File, New SNS Messages (sources) | AWS SNS Trigger; for S3, an S3 event notification to SNS/SQS or to a Webhook (n8n has no S3 trigger) | manual |
AWS steps are not in the converter's mapped list. Each step arrives as a placeholder that keeps its props (region, function name, payload) in a comment; the report lists one AWS credential.
AWS Lambda credentials in n8n
- AWS (IAM): Region, Access Key ID, Secret Access Key, optional session token for temporary credentials, and custom endpoints (for example a VPC endpoint).
- AWS (Assume Role): n8n gets temporary credentials through STS for a role you name; better when the n8n host already has a base identity.
The IAM policy needs lambda:InvokeFunction on the function and lambda:ListFunctions so the node can list functions.
Typical migration: PDF processing
Pipedream: HTTP trigger → Lambda - Invoke Function (pdf-extract, payload with S3 key) → Slack Send Message with the result.
n8n: Webhook → AWS Lambda → Invoke (pdf-extract, Wait for Results, JSON Input {"key": "{{ $json.body.key }}"}) → Slack → Message → Send.
AWS Lambda migration pitfalls
- Payload size. Synchronous invocations accept up to 6 MB request and response; asynchronous ones much less (check the current AWS quota). Pass S3 keys, not files.
- Timeouts. A Lambda can run up to 900 seconds. With Wait for Results, the n8n execution waits that long; use async plus a callback webhook for long jobs.
- Errors. If the function returns an error (
errorMessage), the node fails. To branch on errors instead of stopping, turn on Continue On Fail and check the output. - Region. The credential's region decides which functions are listed; for functions in another region, use a second credential set to that region.
How to move your Lambda workflows
- Export from Pipedream.
- Upload on /convert; the free report lists every AWS step and its props.
- Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.
Code steps using @aws-sdk/client-lambda can be checked in the code step checker. Related: AWS SQS, AWS S3, OpenAI.
FAQ
- What does the n8n AWS Lambda node do?
- One operation: Invoke a function, with the function picked from a list, a JSON payload, a qualifier (version or alias) and an invocation type: wait for results or event (fire and forget).
- Where is Lambda in Pipedream?
- Inside the shared AWS app (aws): Lambda - Invoke Function and Lambda - Create Function. There is no Lambda-only app.
- Can n8n create or deploy Lambda functions?
- Not with the Lambda node. Lambda - Create Function needs an HTTP Request to the Lambda API with the AWS credential, or better, your normal deployment pipeline.
- Do Lambda steps convert automatically?
- No. They arrive as placeholders with their props (region, function name, payload), and the report lists one AWS credential for the workflow.