Resources · Make integration

LastPass Make integrationAutomate LastPass with Make.

What if new hires got their LastPass invite without anyone opening the admin console? The LastPass Make integration gives you 12 modules: 1 trigger, 10 actions and 1 search. It is built for the people who run LastPass accounts, and this page walks you from connection to a working scenario.

Try the LastPass integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the LastPass Make integration do for you?

The LastPass Make integration links your LastPass business account to Make, so user administration runs on its own. A scenario (the automation you build in Make, a chain of modules) can invite people, sort them into groups, push shared sites, force password changes and read the event log, all without code.

Onboarding without tickets. When a new person shows up in your HR or form tool, Invite a User sends the LastPass invitation, Add/Remove a User in Groups places them in their team's groups, and Push Sites to Users hands over the shared logins they need on the first morning.

Clean departures. The day someone leaves, Delete a User deactivates, removes or deletes their account, so access stops at the same moment the contract does. List User Info helps you check who is still active before and after.

Security follow-up. Watch Events reads new entries in the LastPass event reports, such as a user login or a pushed site. From there you can require a master password change or send a reset email to the person concerned.

What Make does not give you here: an instant trigger. Watch Events is scheduled, so it picks up events at the pace of your scenario, not the second they happen. Anything the listed modules skip goes through Make an API Call. New to the editor? The Make training covers the basics, Make pricing explains the plans, and if you are also looking at n8n, read n8n vs Make.

Connect

How do you connect LastPass to Make?

  1. 01

    Grab two values from the admin console

    In the LastPass admin console, open Dashboard and copy the account number shown at the top. Then go to Advanced, pick Enterprise API and copy the provisioning hash at the top of that page.

  2. 02

    Add a LastPass module in Make

    In your scenario, add any LastPass module and click Create a connection. A connection is your LastPass account linked to Make once, then reused by every LastPass module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the credentials and save

    Enter the account number and the provisioning hash you copied, then follow the on-screen instructions. From that point on, every LastPass module of the scenario can work on your users.

First scenario

Your first scenario: invite a new hire and place them in groups

GoalWhen a new hire is added to another tool, Make invites them to LastPass and puts them in their team groups.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Add the module of the tool where new hires first appear, such as your HR app or a form, and connect it.

  2. 02

    Add Invite a User

    Click the + on the right, search for LastPass and choose Invite a User. Click Create a connection if you have not yet, then map the new hire's email from the previous module.

  3. 03

    Place them in groups

    Add Add/Remove a User in Groups after the invite. Map the same email and set the groups that match the person's team.

  4. 04

    Test with Run once

    Click Run once with a test person. Each module shows the bundles it received (a bundle is one item passing from module to module), so you can check the invite went to the right address.

  5. 05

    Schedule and switch on

    On the first module, open the clock and keep the default of every 15 minutes or pick another interval allowed by your plan. Then switch the scenario on.

Triggers

What starts a LastPass scenario

1 module starts a scenario when something happens in LastPass. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by LastPass as soon as it happens.

LastPass1Watch Events

Watch Events

Scheduled trigger

In Make“Triggers when a new report is created. E.g. user login, pushed site, etc.”

Watch Events hands your scenario every new entry that LastPass records in its event reports, for example a user login or a site pushed to users. Each entry arrives as its own bundle, ready to filter, log or act on.

How it fires
scheduled. Make checks LastPass on the scenario's schedule, which is every 15 minutes by default and never under 15 minutes on the Free plan.
When to use it
you want a security log in a spreadsheet, or you want to react to specific events with a password reset.
Watch out
since it polls, an event can reach Make some time after it happened in LastPass.
Modules

What LastPass can do in Make

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

LastPass1

Add/Remove a User in Groups

Action

In Make“Adds/Removes a user in groups.”

Adds a person to LastPass groups or takes them out, in one step, so group membership follows their team without anyone clicking through the admin console.

When to use it
right after an invite, or when someone changes department and needs the new team's access.
Watch out
the same module both adds and removes, so double-check which direction you set before running it on real users.
LastPass2

Delete a User

Action

In Make“Deactivates/Removes/Deletes a user account.”

Closes a person's LastPass access by deactivating, removing or deleting their account, the step that matters most when someone leaves the company.

When to use it
when an offboarding record is completed in your HR tool.
Watch out
Make has no module to bring an account back, so test on a dummy account and prefer deactivation while you validate the flow.
LastPass3

Disable Multifactor

Action

In Make“Disables a user's multifactor authentication.”

Turns off multifactor authentication for one user, which lets them log in again when their second factor is no longer available to them.

When to use it
as the last step of an approved help desk request, for instance after a lost phone.
Watch out
this weakens the account, so keep it behind an approval step and never trigger it from an unchecked source.
LastPass4

Invite a User

Action

In Make“Invites a new user.”

Sends a LastPass invitation to a new person, so their vault is ready from the first day without anyone typing their address into the admin console.

When to use it
as soon as a hire is confirmed in your HR app or a signed onboarding form lands.
Watch out
map a clean work email, because the invite goes exactly where the data says.
LastPass5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the LastPass API with the connection you already have, which covers whatever the ready-made modules leave out.

When to use it
you need a LastPass operation that none of the other eleven modules offers.
Watch out
you build the request yourself, so keep the LastPass API documentation open while you set it up and test with Run once.
LastPass6

Push Sites to Users

Action

In Make“Pushes sites to users.”

Pushes saved sites to users, so the logins a team relies on appear in each member's vault without anyone sharing a password by message.

When to use it
after placing a new hire in groups, to hand them the tools of their role on day one.
Watch out
check the target users before a real run, since the sites land straight in their vaults.
LastPass7

Reinvite a User

Action

In Make“Reinvites a specific user.”

Sends the invitation again to one specific person, useful when the first email was missed or landed in spam and they still have no access.

When to use it
after a List User Info check shows someone who never finished signing up.
Watch out
filter carefully first, so people who already joined do not get a confusing second invite.
LastPass8

Require a Master Password Change

Action

In Make“Sends an email to a user requiring to change their master password. The user will be prompted to change their master password upon the next login.”

Emails a user to say they must change their master password, and LastPass asks them to do it at their next login.

When to use it
after a suspicious login shows up through Watch Events, or when a security review calls for fresh passwords.
Watch out
nothing changes until that next login, so let the person know why the prompt will appear.
LastPass9

Send a Password Reset Email

Action

In Make“Sends a password reset email to a user.”

Gets a password reset email into a user's inbox, so a locked-out colleague can recover without waiting for an admin to do it by hand.

When to use it
when a help desk form asks for a reset and the request is confirmed.
Watch out
unlike the master password module, this one only sends the email and does not force anything at next login.
LastPass10

Update User Email

Action

In Make“Updates user email and sends an email to a user for confirmation of the change.”

Changes the email address on a LastPass account and sends the user a message to confirm the change, keeping logins in step with a rename or a domain switch.

When to use it
when your directory records a new email for someone.
Watch out
the user has to confirm, so the switch is not complete until they act on that email.
LastPass11

List User Info

Search

In Make“Lists information about users.”

Returns information about your LastPass users, which gives you a clear picture of who has an account before you change anything.

When to use it
for an access review, or to find a user before a reinvite or a deletion.
Watch out
as a search, it can return zero, one or many bundles, and every module after it runs once per bundle, which counts operations on your plan.
Need help

Need help automating LastPass with Make?

A person reads every message.

FAQ

LastPass and Make: common questions

01Is the LastPass Make integration free?
Yes, on the Make side. LastPass is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle. Your LastPass subscription is separate and depends on LastPass.
02What do you need to connect LastPass to Make?
An active LastPass account, acceptance of the LastPass API Terms of Use, and access to the admin console. From there you copy two values: the account number at the top of the Dashboard, and the provisioning hash on the Enterprise API page under Advanced. In Make, click Create a connection on any LastPass module, optionally name it, paste both values and follow the on-screen steps. The same connection then serves all 12 LastPass modules.
03Does the LastPass Make trigger work in real time?
No. Watch Events is a scheduled trigger, marked with the clock badge in the editor. Make checks LastPass for new event report entries on the scenario's schedule, every 15 minutes by default. On the Free plan the interval cannot go below 15 minutes; paid plans allow 1 minute. There is no instant trigger for LastPass in Make, so if you need a faster start, begin the scenario from another app that calls Make and use LastPass modules as actions.
04What if a LastPass module is missing in Make?
Use Make an API Call. It sends any request to the LastPass API with the connection you already set up, so you are not limited to the 10 ready-made actions and the search. You write the request yourself, which means keeping the LastPass API documentation at hand and testing with Run once. Note also that the Make documentation page for LastPass is flagged as AI-generated from vendor material, so check important details with LastPass directly.
05Should you use Make or n8n for LastPass?
It depends on the rest of your stack rather than on LastPass alone. In Make, LastPass comes with 12 modules covering invites, groups, shared sites, password resets, multifactor and event reports, plus Make an API Call for the gaps. If your team already runs its automations in n8n, check whether a LastPass node exists there and compare it with this list for your own use case. The n8n vs Make comparison on this site lays out the general differences.
Same platform

Other docs you might need on this stack.

Browse all integrations