Resources · Make integration

bitwarden Make integrationAutomate bitwarden with Make.

Can Make keep your bitwarden collections in order without a script? The bitwarden Make integration gives you 4 modules: 3 actions and 1 search, all about collections. This guide is for IT and ops admins, and it walks you from the connection to a first working scenario.

Try the bitwarden integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the bitwarden Make integration do for you?

The bitwarden Make integration links your bitwarden organization to Make, a no-code tool where you chain apps into a scenario (the automation you build, brick by brick). Its modules read your collections one by one or all at once, and change a collection when another tool asks for it. Anything else in the bitwarden API stays reachable through Make an API Call.

An inventory you never type by hand. List all collections returns every collection as a separate bundle (one item passed to the next module). Send those bundles to a spreadsheet or a ticketing tool and your audit starts from a real list instead of a guess.

Collections that follow your org chart. When a team is renamed in your HR tool or a client project closes in your CRM, Update a collection applies the change in bitwarden. Pair it with Get collection first if you want to check what the collection looks like before you touch it.

A safety net for the rest. The listed modules stop at collections. For another part of the bitwarden API, Make an API Call reuses the same connection, so you do not rebuild the login.

What the integration does not do: it has no trigger, so bitwarden never wakes Make up by itself. Your scenario starts on a schedule or from another app. Make also flags its bitwarden documentation as AI-generated, so double-check anything critical against bitwarden. If you are still picking a platform, read our n8n vs Make comparison; bitwarden has an n8n node too, covered on the bitwarden n8n integration page. New to the editor? The Make training covers the basics.

Connect

How do you connect bitwarden to Make?

  1. 01

    Prepare your bitwarden credentials

    You need an active bitwarden account and an access token generated for a machine account. For the Client ID and Client secret, open Settings, then Organization Information, and scroll down to the API key section.

  2. 02

    Open the connection window in Make

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

  3. 03

    Paste the credentials and save

    Paste what you copied from bitwarden, or follow the on-screen instructions Make shows. Once saved, the connection appears in the dropdown of each bitwarden module, and you will not have to enter those keys again for this account.

First scenario

Build your first scenario with bitwarden

GoalWhen the scenario runs, Make lists the collections of your bitwarden organization and hands each one to Update a collection.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. Since bitwarden has no trigger, this first brick will be a search that Make starts on its own schedule.

  2. 02

    Add List all collections

    Search for bitwarden, pick List all collections and choose your connection (or click Create a connection if you skipped the previous section). Each collection will come out as its own bundle.

  3. 03

    Test the list with Run once

    Click Run once. It executes the scenario a single time. Open the bubble above the module to read the bundles: this shows you what bitwarden actually sends back before you change anything.

  4. 04

    Add Update a collection

    Click the + on the right of the first module and add Update a collection. Map the collection from the previous module so Make knows which one to edit, then fill in the changes. It runs once per collection, so test on a small organization first.

  5. 05

    Run it again, then switch it on

    Run once more and check the result in bitwarden. Then set the clock on the first module (every 15 minutes by default, adjustable) and turn the scenario on. Each module run counts as an operation on your plan.

Modules

What each bitwarden module does

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

bitwarden1

Get collection

ActionIn the docs only

Pulls one collection from bitwarden so the next modules can read its details. You get a single bundle, which keeps the scenario simple.

When to use it
before an update, to confirm you are pointing at the right collection, or when a request from another tool names one collection you need to check.
Watch out
it needs to know which collection you mean; map it from List all collections or from the tool that started the scenario rather than typing it once and forgetting it.
bitwarden2

List all collections

SearchIn the docs only

This search returns every collection of your organization, each one as a separate bundle. It is the natural starting point of a bitwarden scenario, since the app has no trigger.

When to use it
for an access review, to copy the list into a sheet, or to loop through collections and act on some of them.
Watch out
every bundle flows into the next modules, so each following module runs once per collection and uses one operation each time. Keep that in mind before you chain an update after it.
bitwarden3

Make an API Call

ActionIn the docs only

Calls any endpoint of the bitwarden API with the connection you already set up. It covers what the three collection modules cannot, without a separate login.

When to use it
when your idea goes beyond collections and none of the listed modules fits the job.
Watch out
here you work with the raw API, so you write the request yourself instead of filling ready-made fields. Test it with Run once before plugging it into a live scenario.
bitwarden4

Update a collection

ActionIn the docs only

Changes an existing collection in bitwarden with the values you send from earlier modules. It is the only module of this app that writes into your bitwarden organization.

When to use it
when a change starts somewhere else, like a renamed team in your HR tool or a project closed in your CRM, and bitwarden should follow.
Watch out
an update lands on a real collection your team relies on. Test on a spare collection with Run once, and read it back with Get collection before you go live.
Need help

Need help automating bitwarden with Make?

A person reads every message.

FAQ

bitwarden and Make: common questions

01Is the bitwarden Make integration free?
Yes, on the Make side. bitwarden is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution 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. You still need your own bitwarden account; its pricing is on the bitwarden side and not covered here.
02What do you need to connect bitwarden to Make?
An active bitwarden account and an access token generated for a machine account. In bitwarden, go to Settings, then Organization Information, and scroll to the API key section to copy the Client ID and the Client secret. In Make, add a bitwarden module, click Create a connection, give it a name if you like, and paste those values. The connection is then shared by every bitwarden module in your scenarios, so you only do this once per account.
03Can bitwarden trigger a Make scenario in real time?
No. The bitwarden app in Make has no trigger at all, neither scheduled nor instant. You start the scenario another way: set a schedule on its first module (every 15 minutes by default, down to 1 minute on paid plans), or begin with a trigger from another app, such as a new row in a sheet or a form entry. In both cases, List all collections or Get collection then fetches what the rest of the scenario needs from bitwarden.
04What if the bitwarden module you need is missing?
Use Make an API Call. It reaches any endpoint of the bitwarden API with the same connection, so you can go beyond the three collection modules without new credentials. You do write the request yourself, so start small and test it with Run once. Keep in mind that Make labels its bitwarden documentation as AI-generated and possibly wrong in places, so check any detail that matters against bitwarden before a scenario touches real collections.
05Should you use Make or n8n for bitwarden?
It depends on where the rest of your automations live. bitwarden exists in both tools. On Make, you get 4 modules centered on collections, a no-code editor, and Make an API Call for anything else the listed modules leave out. The n8n node has its own set of operations, described on our dedicated n8n page. Compare the operations each one offers against the job you have in mind, and pick the tool your team already uses for its other scenarios.
Same platform

Other docs you might need on this stack.

Browse all integrations