Resources · Zapier integration

AWS Lambda Zapier integrationAutomate AWS Lambda with Zapier.

The AWS Lambda Zapier integration gives you 1 trigger, 3 actions and 0 searches. It lets a Zap call a function you already deployed on AWS, or run a short piece of JavaScript, when no ready-made app does the job. It is a premium app: no free plan.

Premium app Zapier reserves this app to its paid plans.

See the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

Why plug AWS Lambda into a Zap

The AWS Lambda Zapier integration is the escape hatch for logic no other app covers. Zapier, the automation tool, hands data from any app to a function in your AWS account, or to a snippet of JavaScript you type in the editor, and passes the result on. You keep the code; Zapier handles the plumbing around it.

Three typical results. A calculated value back in the Zap: Invoke Function (Sync) waits for your function and hands its answer to the next step, so a pricing rule or a scoring formula feeds your CRM. A background job started: Invoke Function (Async) fires the function with your data and moves on without waiting. A quick transformation written on the spot: Run Code executes JavaScript you type in the browser, inside a Lambda function whose source Zapier provides.

What Zapier does not do here. It does not build, deploy or edit functions; the two Invoke actions only reach functions that already exist. The single trigger watches for new functions, not for function runs or errors, so it cannot tell you when your code fails on AWS. There is no search step either. And the app is premium, so even a two-step Zap needs a paid plan or the free trial.

To compare platforms, the AWS Lambda n8n integration treats the same app on n8n, and n8n vs Zapier puts the two tools next to each other.

Vocabulary

Zapier vocabulary, one line each

Defined once here, then used as is in the rest of the page.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the event happens.
Trigger
The event that starts the Zap. AWS Lambda has one: a new function showing up in the connected account.
Action
What the Zap does once it has started, like calling your function or running a snippet of code for you.
Task
What your plan counts: each Invoke or Run Code that finishes without error is one task, nothing more.
Polling vs instant
A polling trigger is checked by Zapier on a timer; an instant one is pushed by the app. New Function is polling.
Filter
A step that lets the Zap continue only when the data matches your condition, and stops it otherwise.
Premium app
An app Zapier keeps for paid plans and the free trial. AWS Lambda is one, so the free plan cannot use it.
Cost

What an AWS Lambda Zap costs on Zapier

Start with the blocker: AWS Lambda is a premium app, so it only runs on a paid plan or during the free trial.

  • Premium appYes, paid plans and free trial only
  • Free planNot available for this app
  • Trigger costNever a task
  • Action costOne task per successful run

Once you pay, the count is simple. The New Function trigger never costs a task, however often Zapier checks. Each Invoke or Run Code that succeeds costs one task, and one that fails costs nothing. Since you are on a paid plan anyway, adding a filter or a second action is not a new hurdle, but each extra action doubles the bill per run. Your AWS invoice for running the function itself is a separate bill.

Connect

Connect AWS Lambda to Zapier in 3 steps

  1. 01

    Open Apps in Zapier

    Go to Apps in your Zapier account and click + Add connection. You need an AWS account first, plus access to the functions you want the Zap to call if someone else owns them.

  2. 02

    Pick AWS Lambda

    Search for AWS Lambda in the dialog, select it, then click Add connection. A new tab opens on the AWS side, where the sign-in of the next step takes place.

  3. 03

    Sign in and allow access

    Sign in to AWS in that tab and grant Zapier access. The connection then sits in your list, and every AWS Lambda step in every Zap reuses it, so you only do this once.

First Zap

Your first AWS Lambda Zap

GoalEvery new test function in your account gets called once, and the team hears about the answer in a chat channel.

  1. 01

    Create the Zap and set the trigger

    Start a new Zap, pick AWS Lambda as the app and New Function as the event, then choose the AWS connection you just created.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent functions from the account, so you can map fields from a real one instead of a placeholder.

  3. 03

    Add a filter

    Click the plus icon and choose Filter. Pick the function name, a text rule and the word test, so production functions never get called by accident.

  4. 04

    Call the function

    Add Invoke Function (Sync). Map the function from the trigger into Function, and fill Arguments with the input your code expects.

  5. 05

    Post the result, test, publish

    Add the chat step with the answer from the previous step. Test each step once, read what came back, then click Publish.

Triggers

The AWS Lambda trigger

1 event starts a Zap when something happens in AWS Lambda. Zapier checks for them at the interval your plan allows.

1

New Function

Polling trigger

In Zapier“Triggers when a new function is added.”

Starts your Zap each time a function appears in the connected AWS account, and hands its details to the following steps. It watches the creation of functions only: not their runs, not their failures, not changes to an existing one. That makes it a tool for keeping track of what gets deployed, not for reacting to what your code does.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise
When to use it
post a note in the team channel, or log a row in a register, each time someone ships a new function.
Watch out
functions that existed before you switched the Zap on are never picked up.
Actions

The 3 AWS Lambda actions

AWS Lambda gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Invoke Function (Async)

Action

In Zapier“Invokes a pre-built function asynchronously providing only data.”

Sends data to one of your existing functions and lets it run on its own, without waiting for an answer. The Zap moves on straight away.

When to use it
a form submission should kick off a longer job on AWS that writes its result elsewhere.
Watch out
nothing comes back to Zapier, so no later step can use the function's output.
2

Invoke Function (Sync)

Action

In Zapier“Invokes a pre-built function synchronously and returns the result.”

Calls one of your functions, waits for it to finish, and returns what it produced to the Zap. Your Arguments arrive in the function as its event object.

When to use it
a rule lives in your code, such as a discount or a lead score, and the next step needs the number.
Watch out
the action only calls a pre-built function, so deploy it before mapping the Function field.
3

Run Code

Action

In Zapier“Write Javascript code directly in your browser and execute it in a Lambda function that we provide the source for.”

Executes JavaScript you type straight into the Zap editor, inside a Lambda function whose source code Zapier provides.

When to use it
a date needs reformatting or two fields need merging, and no built-in step does it cleanly.
Watch out
Input Object is required: it is where you hand your snippet the values from earlier steps.
When it breaks

When an AWS Lambda Zap breaks

Zapier links three help articles to this app, including one called Common Problems with AWS Lambda. Their content is not summed up here; the cases below come from how the operations work and from Zapier's general limits.

Read these before blaming your code. When a run fails anyway, the Zapier troubleshooting page is where to start.

  • The async call returns nothing

    Invoke Function (Async) hands over data and moves on. A later step that expects the function's answer gets an empty field; switch to the Sync action.

  • Older functions never trigger

    A Zap only reacts to what happens after you switch it on. Functions deployed before that are ignored, and listing them is a separate job.

  • A big deployment gets held back

    If a script creates a large batch of functions at once, Zapier's flood protection can hold the trigger back instead of firing for each one.

  • The function is not deployed yet

    Both Invoke actions only reach pre-built functions. One that is not deployed yet, or that lives in another AWS account, cannot be called.
Need help

Need help automating AWS Lambda with Zapier?

A person reads every message.

FAQ

AWS Lambda Zapier integration: common questions

01Is the AWS Lambda Zapier integration free?
No. AWS Lambda is a premium app on Zapier, which means it is reserved for paid plans and the free trial. The free plan cannot use it at all, not even in a simple two-step Zap. Once you are on a paid plan, the Zapier side is billed in tasks like any other app. Your AWS account bills the function runs separately, and this page does not cover AWS pricing. Try it during the trial before committing to a plan.
02How many tasks does an AWS Lambda Zap use?
One task per action that succeeds. The New Function trigger never costs a task, and Zapier checking for new functions is free however often it happens. Each successful Invoke Function (Async), Invoke Function (Sync) or Run Code counts as one task. A failed call is not counted. A Zap that calls your function and then posts the result in a chat tool uses two tasks per run, because every successful action is counted on its own. Some apps take more than one task per action, so check your usage after the first runs.
03Does the AWS Lambda trigger work in real time?
No, New Function is a polling trigger. Zapier checks the account on a timer: every 2 minutes on Professional, every minute on Team and Enterprise. The free plan does not apply, since the app is premium. On paid plans you can also run a check by hand from the editor while testing. The actions are a different story: they run as soon as the Zap reaches them, whatever started it, so a Zap triggered by an instant trigger from another app calls your function right away.
04What does it take to connect AWS Lambda to Zapier?
An AWS account, access to the functions you want to call, and a paid Zapier plan or the trial. In Zapier you open Apps, click + Add connection, search for AWS Lambda, then sign in to AWS and grant access in the tab that opens. The connection is reused by every Zap afterwards. Before building, deploy the function you want to call: both Invoke actions call a pre-built function, so it has to exist in the connected account first.
05Why does the next step get nothing back from AWS Lambda?
Most likely because the Zap uses Invoke Function (Async). That action sends your data to the function and moves on without waiting, so it never hands a result to the steps that follow. Use Invoke Function (Sync) whenever a later step needs the output: it waits for the function to finish and returns what it produced. Keep the async version for jobs that store their own result somewhere else, such as a database or a file, where waiting would only slow the Zap down.
06What if the AWS Lambda operation you need is not there?
Then Zapier does not offer it for this app. The integration covers one trigger and three actions: watching for new functions, calling a function with or without waiting, and running JavaScript. There is no trigger for failed runs, no search, and no way to create or update a function. The usual way around it is Run Code, which lets a short snippet do what no built-in step does. For anything bigger, write it as a function on AWS and call it with Invoke Function (Sync).
07Zapier, Make or n8n for AWS Lambda?
It depends on your criteria, not on a winner. Zapier is quick to set up and Run Code takes JavaScript typed in the editor, but AWS Lambda is premium there, so a paid plan is required from the first Zap. For n8n and Make, check which AWS Lambda operations each exposes and who on your team will maintain the flow. Weigh the number of calls per month against what each tool counts as a billed step.
Same platform

Other docs you might need on this stack.

Browse all integrations