Resources · n8n integration

Bitwarden n8n integrationAutomate Bitwarden with n8n.

Your organization vault can be administered from a workflow instead of the web vault. The Bitwarden n8n integration covers 19 operations across 4 resources: collections, groups, members and the event log. No Bitwarden trigger ships with n8n, so a Schedule or Webhook node starts the run. Built for ops and IT.

Try the Bitwarden integration on n8nSee the 19 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Bitwarden n8n integration actually cover?

The Bitwarden node talks to the Bitwarden Public API on behalf of an organization. It reads and writes the four objects that make up organization administration: collections, the groups that get access to them, the members of the organization, and the event log that records what happened. Everything a workflow does here is admin work, driven by the Organization API Key you configure once in n8n.

The first thing this node solves is offboarding. Someone leaves, and their access has to disappear the same day. A workflow that starts on a Schedule Trigger, a node that fires at a fixed interval, reads the leavers from wherever your HR data lives, then calls member.getGroups to record what that person could reach, and member.delete to remove them from the organization. The record of what was revoked lands in Google Sheets or a table in Postgres, which is what an auditor asks for later.

The second is the quarterly access review nobody enjoys running by hand. collection.getAll lists the collections, group.getAll lists the groups, and group.getMembers resolves who sits in each one. Loop the three and you get a full map of who can open what, posted into a Slack channel for the managers who have to sign it off. When a manager answers, group.updateMembers or member.updateGroups applies the change without anyone touching the admin console.

The third is keeping the event log somewhere you can query. event.getAll reads the organization events, with Start Date and End Date to bound the window, and Acting User ID or Item ID when you are chasing one person or one entry. A nightly workflow appends that window to Supabase and you stop being limited to what the web vault shows you on screen.

Two things are worth knowing before you build. The Bitwarden Public API is only available on Teams and Enterprise organization plans, so the credential simply will not authenticate on anything else. And whatever falls outside these 19 catalog operations goes through the HTTP Request node, which calls any endpoint of the API while reusing the same Bitwarden credential through predefined authentication.

If you are picking your platform rather than building today, the n8n review goes through the trade-offs in detail, and the n8n training covers the expression syntax these workflows lean on.

Connect

How do you connect Bitwarden to n8n?

  1. 01

    Generate an Organization API Key

    Bitwarden only makes the Public API available to Teams and Enterprise organization accounts, so start by checking which plan the organization runs on. Then generate the key from the organization settings, not from a personal account. Generating it gives you two values, a Client ID and a Client Secret, and both belong to the organization rather than to the person who created them.

  2. 02

    Create the credential in n8n

    In the Credentials menu, add a Bitwarden credential, which is the stored set of secrets n8n reuses across workflows. Paste the Client ID and the Client Secret from the previous step. You create this once. Every Bitwarden node you drop into any workflow afterwards picks it from its dropdown, so rotating the key later is a single edit instead of a hunt through your workflows.

  3. 03

    Set the Environment

    The credential asks for an Environment. Choose Cloud-hosted if you do not self-host Bitwarden, and nothing else is required. Choose Self-hosted if Bitwarden runs on your own server, and fill the Self-hosted domain field with the address of that server. Save, then run any read operation once to confirm the credential answers.

Actions

The 19 Bitwarden operations, one by one

The Bitwarden node exposes 19 operations across 4 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet ManyUpdateDeleteGet GroupsGet MembersUpdate GroupsUpdate Members
Collection✓✓✓✓
Event✓
Group✓✓✓✓✓✓✓
Member✓✓✓✓✓✓✓

Collection

4 operations
01

Delete a collection

collection.delete

What you see in n8n

Notes & use cases

Removes a collection from the organization, so the items it grouped stop being shared through it. One collection per call.

Key parameters

  • Collection ID: the identifier of the collection, a value shaped like 5e59c8c7-e05a-4d17-8e85-acc301343926, not the collection name you read in the vault.
Use cases
when a client engagement ends, a cleanup workflow archives the details somewhere else and then deletes the collection that held the shared logins for it.
02

Get a collection

collection.get

What you see in n8n

Notes & use cases

Reads one collection and returns its current state. This is the read you run before a write, when you want to know what you are about to change.

Key parameters

  • Collection ID: the identifier of the collection. When it comes from an earlier node, fill it with an expression, the n8n syntax that pulls a value from the incoming item, written {{ $json.field }}.
Use cases
an approval workflow reads the collection, sends its details to the owner for confirmation, and only then runs the update step.
03

Get many collections

collection.getAll

What you see in n8n

Notes & use cases

Lists the collections of the organization. Most Bitwarden workflows open with this one, because every other collection operation needs an identifier you do not have yet.

Key parameters

  • Return All: on, n8n walks through the API pages until every collection has been returned.
  • Limit: with Return All off, the maximum number of collections a single run brings back.
Use cases
a monthly inventory that writes one row per collection into a spreadsheet, so access reviews start from a list nobody had to retype.
04

Update a collection

collection.update

What you see in n8n

Notes & use cases

Changes which groups a collection is shared with, and the external identifier attached to it.

Key parameters

  • Collection ID: the identifier of the collection to modify.
  • Update Fields: required, opened with Add Field. Leave it empty and the node has nothing to write.
  • Group Names or IDs: the group to assign this collection to, picked from the list or given as IDs through an expression.
  • External ID: the external identifier to set on the collection, handy for matching it with a project reference in another tool.
Use cases
a project moves to another team, and the workflow reassigns its collection to that team's group.

Event

1 operation
05

Get many events

event.getAll

What you see in n8n

Notes & use cases

Reads the organization event log, which is where Bitwarden records what happened and who did it.

Key parameters

  • Return All: on, the node keeps paging until the whole window has been read.
  • Limit: the ceiling on returned events when Return All stays off.
  • Start Date and End Date: the bounds of the search window.
  • Acting User ID: narrows the log to the user who performed the actions.
  • Item ID: narrows it to the item the event describes.
Use cases
a nightly run copies yesterday's window into a database so security questions get answered with a query.

Group

7 operations
06

Create a group

group.create

What you see in n8n

Notes & use cases

Adds a group to the organization. Groups are how access is granted at scale, since a collection is shared with a group rather than with people one at a time.

Key parameters

  • Name: the name of the group to create, required.
  • Access All: on, the group reaches every collection in the organization and this overrides any collection assignment.
  • Collection Names or IDs: the collections assigned to the group at creation.
  • External ID: the external identifier to set on the group.
Use cases
a new department appears in the HR system and the workflow creates its group with the right collections already attached.
07

Delete a group

group.delete

What you see in n8n

Notes & use cases

Removes a group from the organization. The access that came through it goes with it, which makes this the last step of a decommissioning run rather than the first.

Key parameters

  • Group ID: the identifier of the group, in the form 5e59c8c7-e05a-4d17-8e85-acc301343926.
Use cases
a temporary group created for a migration is deleted once the migration is signed off, after a previous node has listed its members for the record.
08

Get a group

group.get

What you see in n8n

Notes & use cases

Returns a single group as it currently stands, which is the cheapest way to confirm a group exists before a workflow starts writing to it.

Key parameters

  • Group ID: the identifier of the group to read.
Use cases
a self-service request asks for access to a named group, and the workflow reads that group first so the ticket fails politely instead of erroring when the group is gone.
09

Get many groups

group.getAll

What you see in n8n

Notes & use cases

Brings back the groups of the organization, which is the map you need before deciding where a person belongs.

Key parameters

  • Return All: on, every group comes back, page after page.
  • Limit: the cap applied when Return All is off, useful while you are still testing the workflow.
Use cases
the first node of an access review, feeding each group into the members lookup that follows.
10

Get group members

group.getMembers

What you see in n8n

Notes & use cases

Returns the members attached to one group, answering the question an access review always opens with: who is actually in here?

Key parameters

  • Group ID: the identifier of the group whose members you want.
Use cases
after listing the groups, a loop runs this operation on each one and posts the result to the manager who owns that group for confirmation.
11

Update a group

group.update

What you see in n8n

Notes & use cases

Edits an existing group without recreating it, so its identifier stays valid everywhere else in your workflows.

Key parameters

  • Group ID: the identifier of the group to modify.
  • Name: the new name of the group.
  • Collection Names or IDs: the collections assigned to the group, chosen from the list or given as IDs.
  • Access All: on, the group reaches every collection in the organization, overriding the assignments above.
  • External ID: the external identifier to set on the group.
Use cases
a department is renamed, and one node keeps the group label aligned with the org chart.
12

Update group members

group.updateMembers

What you see in n8n

Notes & use cases

Sets the membership of a group in one call. What you send becomes the group, so this is a replacement rather than an addition.

Key parameters

  • Group ID: the identifier of the group being rewritten.
  • Member IDs: a comma-separated list of the IDs of the members to set in the group. Build it from a previous listing step, otherwise you silently drop whoever you forgot.
Use cases
a project group whose membership is recalculated every morning from the assignment sheet the project leads maintain.

Member

7 operations
13

Create a member

member.create

What you see in n8n

Notes & use cases

Adds a member to the organization with a role and, if you want, their access already set.

Key parameters

  • Type: the role, required, chosen from Owner (0), Admin (1), User (2) and Manager (3).
  • Email: the address of the member, in the form name@email.com.
  • Access All: whether this member reaches every collection.
  • Collection Names or IDs: the collections assigned to the member, picked from the list or given as IDs.
  • External ID: the external identifier to set on the member, useful for matching the record with an outside HR system.
Use cases
onboarding day one, with the role read from the job title column.
14

Delete a member

member.delete

What you see in n8n

Notes & use cases

Removes a member from the organization. This is the operation the whole offboarding workflow exists to reach, and it is worth putting a confirmation step in front of it.

Key parameters

  • Member ID: the identifier of the member to remove, not their email address.
Use cases
a departure recorded in the HR tool triggers the run, a previous node captures the person's group list for the audit trail, and this node closes the door.
15

Get a member

member.get

What you see in n8n

Notes & use cases

Fetches one member of the organization. Useful as a guard clause: run it, and the rest of the workflow only continues on someone who is really there.

Key parameters

  • Member ID: the identifier of the member to read, typically carried over from a listing step through an expression such as {{ $json.field }}.
Use cases
a helpdesk workflow that looks up the requester before opening an access ticket on their behalf.
16

Get groups for a member

member.getGroups

What you see in n8n

Notes & use cases

Returns the groups one member belongs to, which is the other half of an access review: not who is in a group, but what one person can reach.

Key parameters

  • Member ID: the identifier of the member whose groups you want.
Use cases
a manager asks what an employee has access to before a role change, and the workflow answers with a list instead of a screenshot of the admin console.
17

Get many members

member.getAll

What you see in n8n

Notes & use cases

Lists the members of the organization, which is the roster you compare against your HR source to find the accounts nobody closed.

Key parameters

  • Return All: on, the node pages through until the full roster is back.
  • Limit: the maximum number of members returned when Return All is off.
Use cases
a weekly reconciliation that flags every Bitwarden member with no matching row in the employee list.
18

Update a member

member.update

What you see in n8n

Notes & use cases

Changes the role or the access of an existing member, without removing and recreating the account.

Key parameters

  • Member ID: the identifier of the member to modify.
  • Type: the new role, Owner (0), Admin (1), User (2) or Manager (3).
  • Collection Names or IDs: the collections assigned to the member.
  • Access All: whether the member reaches every collection.
  • External ID: the external identifier to set on the member.
Use cases
a promotion into a lead role, applied the same day the HR record changes.
19

Update groups for a member

member.updateGroups

What you see in n8n

Notes & use cases

Rewrites the list of groups one member belongs to. The list you pass replaces the previous one, so send the full set, not the difference.

Key parameters

  • Member ID: the identifier of the member being reassigned.
  • Group IDs: a comma-separated list of the IDs of the groups to set for that member.
Use cases
an internal transfer, where the workflow reads the person's current groups, drops the ones tied to the old team, and sends the resulting list back in one call.
Need help

Need help automating Bitwarden with n8n?

A person reads every message.

FAQ

Bitwarden and n8n, the questions that come next

01Is the Bitwarden n8n integration free?
Yes on the n8n side. The Bitwarden node ships with n8n, so there is nothing to install and nothing extra to pay for it, whether you run n8n Cloud, the hosted offer from n8n, or your own instance under the Community Edition and its Sustainable Use licence. A self-hosted instance and n8n Cloud run the same workflow with the same 19 operations. The Bitwarden side is a different question: the Public API this node calls is only available on Teams and Enterprise organization plans, so an organization on another plan cannot authenticate the credential at all.
02What credentials does the Bitwarden node need?
An API key, and specifically an Organization API Key rather than a Personal API Key. The credential form asks for three things: the Client ID and the Client Secret that Bitwarden gives you when you generate the key, and an Environment. Pick Cloud-hosted if you do not self-host Bitwarden, and nothing else is needed. Pick Self-hosted if Bitwarden runs on your own server, then enter your Self-hosted domain in the field below. You create this credential once in the Credentials menu and every Bitwarden node in every workflow offers it in its dropdown afterwards.
03What are the limits of the Bitwarden node in n8n?
The node exposes 19 operations across 4 resources, collections, events, groups and members, and anything outside that catalog goes through the HTTP Request node. That node calls any endpoint of the Bitwarden Public API while reusing the same credential through predefined authentication, so you are not stuck when a workflow needs something the dedicated node does not list. The other thing to plan for is reading: listing operations return up to Limit items unless you switch Return All on, in which case n8n pages through the API until everything has come back.
04Can a workflow react to Bitwarden in real time?
No, because Bitwarden has no trigger node in n8n. A workflow that involves Bitwarden starts with another starter: a Schedule Trigger that fires at a fixed interval, an n8n Webhook, which is a URL an outside service calls, or the trigger of another tool in your setup. In practice the scheduled route covers most of it. Run the workflow every morning, call event.getAll with a Start Date and an End Date covering the previous window, and branch on what came back. For anything event-driven, let the system that owns the event, your HR tool or your ticketing system, call an n8n Webhook and use Bitwarden as the action.
05n8n or Make for Bitwarden?
It depends on where your secrets are allowed to live. Make is a hosted automation platform with no self-hosting option and billing per operation, while n8n runs on n8n Cloud or on your own server. For vault administration that difference matters more than usual: self-hosting keeps the workflow that reads your event log and rewrites your group membership inside your own perimeter. The cost model differs too, per operation on one side against an instance you run on the other, and a group review that loops over every group burns operations fast. If your team prefers a hosted visual builder and the volume stays low, Make is a reasonable answer.
Same platform

Other docs you might need on this stack.

Browse all integrations