AWS Lambda
AWS Lambda serverless function invocation
AWS Lambda is the serverless compute platform — run code without managing servers, billed per invocation + execution time. Tiny Command exposes two actions, no triggers (Lambda itself is the trigger destination — events from other AWS services fire Lambdas; for "workflow triggered by a Lambda" patterns, have your Lambda POST to a Tiny Command webhook trigger): Invoke Function (synchronously or asynchronously call a Lambda function with a JSON payload, get the response back for sync invocations), List Functions (every Lambda in the connected region/account). The connection uses AWS IAM credentials (access key + secret) with lambda:InvokeFunction permissions on the target functions, plus the region. The Invoke Function pattern is the standard cross-cloud workflow shape: when a Tiny Command workflow needs to run complex logic that's better expressed in Python/Node (image processing, ML inference, custom encryption), Invoke Function pushes the work to a Lambda and gets the result back. For sync invocations, the workflow waits for the Lambda response; for fire-and-forget, set invocation_type=Event.
Do anything AWS Lambda can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Invoke Lambda Function | Synchronously or asynchronously invokes a Lambda with a JSON payload. Sync waits for the response (up to 15 min, Lambda's max); async returns immediately with an InvocationId for fire-and-forget patterns. The right escape hatch when the workflow needs Python/Node logic that doesn't fit cleanly into a Code step. |
| List Lambda Functions | Returns all Lambda functions in the connected AWS account + region with name, runtime, and ARN. Useful for inventorying available functions when setting up an Invoke action. |
Pre-built AWS Lambda workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect AWS Lambda once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every AWS Lambda field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the AWS Lambda integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect AWS Lambda to Tiny Command?
What AWS Lambda triggers does Tiny Command support?
What AWS Lambda actions can I run from a workflow?
Is the AWS Lambda integration real-time?
Do I need to write code to use AWS Lambda with Tiny Command?
How much does the AWS Lambda integration cost?
More other apps people connect.
Same category as AWS Lambda, ordered by how often teams pair them. Hover the carousel to pause.
Do more with AWS Lambda.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
