Resources · Zapier integration

LastPass Zapier integrationAutomate LastPass with Zapier.

LastPass Zapier integration: 0 triggers, 2 actions, 0 searches. Zapier can give a newcomer a LastPass account as soon as another app reports the hire, and send your own request to LastPass when the ready-made action stops short. Nothing inside LastPass can start a Zap, though.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the LastPass Zapier integration actually does

The integration lets a Zap (an automation that runs a set of steps each time something happens in an app) add people to your LastPass account without anyone typing them in. LastPass only ever sits at the end of the chain: it receives work from other tools, it never kicks a Zap off on its own.

Three results people actually get out of it. A seat ready on day one: your HR tool or a signed-offer form starts the Zap, and Create User adds the newcomer with the email the first step carried. An onboarding sheet that does the admin: each new row with an address becomes a LastPass user, and a filter keeps out the rows that should not get one. The call the menu does not list: API Request (Beta) reuses your LastPass connection to send a request someone on your team has written by hand, for anything beyond creating a user.

Now the part the app page leaves out. Zapier offers no trigger and no search for LastPass. A Zap cannot react to something that changes inside your vault, and it cannot check first whether a person already has an account, so a duplicate address will reach Create User unless you filter it upstream. There is no ready-made action to remove or suspend a user either: offboarding stays manual, or goes through a hand-written request.

If you are weighing tools, see our LastPass Make integration page and our n8n vs Zapier comparison.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every Zapier screen. Here is what each one means in plain terms.

Zap
The automation you build on Zapier: one starting event, then one or more steps that run each time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it. LastPass has none, so another app plays this role.
Action
What the Zap does after it starts: the step that writes, sends or creates something for you, like a new LastPass user.
Task
The unit Zapier bills: one action that the Zap completes successfully. The allowance on your plan is a count of those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app the moment the event happens.
Filter
A step that lets the Zap carry on only when the incoming data matches a rule you set, and stops it quietly otherwise.
Connection
Your LastPass account linked to Zapier once, then reused by every step of every Zap that talks to LastPass.
Multi-step Zap
Any Zap with more than one trigger and one action. A second action or a filter turns it into one, and it then needs a paid plan.
Cost

What it really costs in tasks

LastPass is not a premium app, so it works on the free plan. The bill is counted in tasks, and only finished actions count.

  • Trigger checks0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps only
  • Premium appNo, available on the free plan

The trigger never costs a task, however often Zapier checks the other app. Each Create User or API Request (Beta) that goes through costs one; a call that fails costs nothing. The free plan gives 100 tasks a month but only two-step Zaps: one trigger, one action. Add a filter, or a second action, and the Zap needs a paid plan. How fast the Zap starts depends on the trigger app and on your plan's polling interval below.

Connect

Connect LastPass to Zapier in three steps

  1. 01

    Open your Apps page

    In your Zapier account, go to Apps and click + Add connection. This is where every connection lives, so you set LastPass up once and pick it from any Zap later.

  2. 02

    Pick LastPass

    Type LastPass in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the LastPass side to finish the link.

  3. 03

    Sign in and allow access

    Log in to LastPass in that tab and grant Zapier access to the account. Use an account that can act on everything the Zap will touch: read or write rights on what you do not own yourself.

First Zap

Your first Zap: onboarding sheet to LastPass user

GoalEach new row with an email that passes your filter becomes a LastPass user.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap and choose the app that holds your new hires as the trigger, here a spreadsheet row. LastPass cannot start a Zap, so the first step always belongs to another tool.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent rows from the connected sheet. Pick one with a real email so the next steps are mapped on actual data.

  3. 03

    Add the filter

    Add a Filter step from the plus icon and set the field, the rule and the value. Use a text rule on a text column, or the filter never passes. This makes the Zap multi-step.

  4. 04

    Add Create User

    Add LastPass as the action, pick Create User, choose your connection and map the email column into the Email field. Leave nothing else to guess.

  5. 05

    Test and publish

    Test the action once and check that the user appears in LastPass. Then click Publish to switch the Zap on. Only rows added after this moment will be picked up.

Actions

LastPass actions in Zapier

LastPass gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create User

Action

In Zapier“Creates a new user.”

Adds a person to your LastPass account from an email address passed along by an earlier step, so nobody has to open LastPass to set the account up by hand.

When to use it
a signed offer, a new onboarding row or a fresh record in your HR tool should give the newcomer a LastPass seat before their first morning.
Watch out
Email is the only required field, and a trigger that sometimes arrives without one makes this step fail.
2

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

Lets you send a request you write yourself to LastPass while Zapier signs it with the connection you already set up, for jobs that Create User does not cover.

When to use it
a technical teammate knows exactly which LastPass feature to call and wants it inside the Zap rather than in a separate script.
Watch out
the address must belong to a domain tied to LastPass, and the required Stop on error choice decides whether a failed call halts the Zap.
When it breaks

When the Zap breaks

Zapier attaches no help article to LastPass and lists no limit specific to it. What breaks is the general behavior of Zaps, and it bites hard on account creation.

Most failures here start upstream, in the app that triggers the Zap, and land on Create User. Read the four cases below before switching the Zap on, and check the run history when a newcomer has no account. For repairs, see our Zapier troubleshooting page.

  • People hired before the Zap are ignored

    A Zap only reacts to what happens after you publish it. Employees already in the sheet stay without a LastPass account, and moving that backlog is a separate job.

  • A loop that eats your tasks

    If a later step writes back into the sheet the trigger watches, the Zap sets itself off again and again, and each round creates users and burns tasks.

  • A bulk import gets held back

    Paste a whole team into the sheet at once and the trigger returns a huge batch. Zapier's flood protection can hold it, so those users wait.

  • The same row will not fire twice

    Zapier remembers what it has already seen on a polling trigger. Editing an old row to fix an email will not send it to LastPass again.
Need help

Need help automating LastPass with Zapier?

A person reads every message.

FAQ

LastPass Zapier integration: frequent questions

01Is the LastPass Zapier integration free?
Yes, as long as the Zap stays simple. LastPass is not a premium app, so it works on the free plan, which gives 100 tasks a month. The catch is the two-step ceiling: the free plan builds one trigger and one action, nothing more. A Zap that adds a filter, or a second action after Create User, becomes a multi-step Zap and needs a paid plan. Plan prices change often, so check the current grid on Zapier before choosing.
02How many tasks does it use?
One task per action that succeeds, and nothing else. The trigger in the other app is free, however often Zapier checks it, and looking for new data costs nothing either. So a Zap that creates one LastPass user uses one task per newcomer. An action that fails, for example because the email was blank, is not counted against your plan. If you chain a second action after Create User, each successful run then costs two tasks instead of one.
03Does it run in real time?
That depends entirely on the other app, because LastPass has no trigger of its own. If the app that starts the Zap reports events instantly, the user is created right away whatever your plan. If its trigger is a polling one, Zapier checks on a timer: every 15 minutes on Free, every 2 on Professional, every minute on Team and Enterprise. The Zapier editor shows a lightning bolt on Zaps built on an instant trigger, which is the quickest way to tell.
04What is needed to connect a LastPass account?
A LastPass account and a few clicks. Open Apps in Zapier, click + Add connection, search for LastPass, confirm with Add connection, then sign in to LastPass in the tab that opens and grant access. The account you connect needs read or write rights on everything the Zap will touch that you do not own yourself. The connection is stored once and reused by every Zap that works with LastPass. No paid plan is required for the connection itself.
05Can Zapier check whether a LastPass user already exists?
No, not with a ready-made step. Zapier offers no search for LastPass, so the Zap cannot look up an address before calling Create User. The practical answer is to stop duplicates upstream: keep one row per person in the source sheet, and add a filter on a column such as status so only new hires go through. Remember that a filter makes the Zap multi-step, so it needs a paid plan.
06What if the LastPass action you want is not in the list?
Use API Request (Beta). It lets someone write the request by hand while Zapier reuses the LastPass connection already set up, so there is no separate sign-in to manage. Two fields matter: the address must point to a domain tied to LastPass, and Stop on error decides whether a failed call stops the Zap or lets it carry on. Each successful call costs one task, like any action. It is the route for offboarding, since no removal action exists.
07Zapier, Make or n8n for LastPass?
It comes down to criteria, not a winner. On Zapier, LastPass offers two actions and no trigger, works on the free plan, and the setup takes three steps with no code. If offboarding or checks for existing users are part of the job, look at whether the other platform covers those steps for LastPass before deciding. Compare the operations each platform exposes for LastPass, the billing unit, and who on your team will maintain the workflow.
Same platform

Other docs you might need on this stack.

Browse all integrations