BITWARDEN n8n INTEGRATION: AUTOMATE BITWARDEN WITH N8N

This action retrieves all members belonging to a specific group in your Bitwarden organization. It's essential for auditing group compositions, verifying access levels, or building workflows that need to iterate over group members—like sending targeted communications or syncing permissions with external systems like Airtable.

Key parameters: Credential to connect with (select your Bitwarden account credentials from the dropdown menu, required for authentication), Resource (set to "Group"), Operation (set to "Get Members" to specify you want member retrieval), and Group ID (the unique identifier of the group you want to query, accepts text input including expressions for dynamic values, required).

Use cases: Audit which users have access to sensitive password collections by checking group membership, sync Bitwarden group members with Slack channels or Microsoft Teams, generate weekly reports of group compositions for compliance purposes.

This action modifies the details of an existing member in your Bitwarden organization. Use it to change member roles, update access permissions, or modify member properties as part of automated user lifecycle management.

Key parameters: Credential to connect with (your Bitwarden authentication credentials via dropdown, required), Resource (fixed to "Member"), Operation (set to "Update" to modify existing member data), Member ID (the unique identifier of the member to update, text field required), and Update Fields (click "Add Field" to specify which member properties to modify).

Use cases: Automatically elevate member permissions when they're promoted, bulk-update member types based on department changes from your HR system, revoke admin access and downgrade to standard user during role transitions.

This action permanently removes a member from your Bitwarden organization. It's the nuclear option for user offboarding—use it when someone leaves the company or when you need to revoke all access immediately.

Key parameters: Credential to connect with (Bitwarden account credentials via dropdown, required), Resource (pre-set to "Member"), Operation (fixed to "Delete"), and Member ID (the unique identifier of the member to remove, text input required).

Use cases: Automatic offboarding triggered by HR system termination events, emergency access revocation when a security incident is detected, clean up test or duplicate member accounts programmatically.

This action modifies the properties of an existing group in your Bitwarden organization. Use it to rename groups, change access settings, or update group configurations as part of organizational restructuring workflows.

Key parameters: Credential to connect with (your Bitwarden credentials via dropdown, required), Resource (fixed to "Group"), Operation (set to "Update"), Group ID (the unique identifier of the group to modify, text field required), and Update Fields (dynamic section where you click "Add Field" to specify which group properties to change).

Use cases: Rename groups to match updated team naming conventions, modify group access levels during security policy changes, batch-update group settings across multiple groups using a loop.

This action adds a new member to your Bitwarden organization. It's the foundation of automated user provisioning—connect it to your HR system or identity provider to automatically grant Bitwarden access when new employees join.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Member"), Operation (set to "Create"), Type (defines the member's role, defaults to "User", select from dropdown options like User, Admin, Owner, or Manager, required), Email (the email address for the new member, text field required), Access All (toggle switch determining whether the new member gets access to all collections, optional), and Additional Fields (add custom properties as needed).

Use cases: Auto-provision Bitwarden access when new employees are added to BambooHR or Workday, create members in bulk from a spreadsheet import, set up contractor accounts with limited access automatically.

This action modifies which groups a specific member belongs to. It's perfect for managing access at scale—when someone changes teams or takes on new responsibilities, update their group memberships in one action rather than editing each group individually.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Member"), Operation (set to "Update Groups"), Member ID (the unique identifier of the member whose groups you're updating, text input required), and Group IDs (the identifiers of groups this member should belong to, enter as comma-separated values, text field required).

Use cases: Sync group memberships when employees change departments, grant project-based access by adding members to temporary groups, implement role-based access control by mapping job titles to group assignments.

This action retrieves detailed information about a specific member in your Bitwarden organization. Use it to verify member status, check permissions, or pull member data into workflows that need to make decisions based on member properties.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (pre-set to "Member"), Operation (fixed to "Get"), and Member ID (the unique identifier of the member to retrieve, text input required).

Use cases: Verify a member exists before attempting to update their permissions, pull member details into notification messages or reports, check member type before allowing certain workflow branches to execute.

This action modifies the membership list of a specific group. Unlike "Update groups for a member" (which focuses on one member), this action lets you manage all members of a group at once—perfect for bulk operations.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Group"), Operation (set to "Update Members"), Group ID (the unique identifier of the group you're modifying, text input required), and Member IDs (the list of member IDs that should belong to this group, text input typically comma-separated, required).

Use cases: Sync a Bitwarden group with an Active Directory security group, rebuild group membership based on data from an external system, implement group membership automation triggered by Slack commands.

This action retrieves multiple members from your Bitwarden organization in a single request. It's more efficient than calling "Get a member" repeatedly and is essential for building reports, audits, or workflows that need to process your entire member list.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Member"), Operation (set to "Get Many"), Return All (toggle switch—when enabled, retrieves all members regardless of the limit setting, optional), and Limit (maximum number of members to retrieve, numeric input, defaults to 10, optional if "Return All" is enabled).

Use cases: Generate a weekly member audit report sent to security teams, export all members to a spreadsheet for compliance documentation, build a dashboard showing total member counts and types.

This action retrieves all groups that a specific member belongs to. It's the inverse of "Get group members"—instead of seeing who's in a group, you see which groups contain a particular user.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Member"), Operation (set to "Get Groups"), and Member ID (the unique identifier of the member whose group memberships you want to retrieve, text input required for accurate results).

Use cases: Audit a specific user's access levels across all groups, verify group assignments before making changes, build access reports showing each member's complete group profile.

This action retrieves multiple groups from your Bitwarden organization. Use it to get an overview of your group structure, build group selection interfaces, or process all groups in bulk operations.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Group"), Operation (set to "Get Many"), Return All (boolean toggle—enable to retrieve all groups without limit, optional), and Limit (maximum number of groups to return, numeric input, optional when "Return All" is enabled).

Use cases: Generate a complete group inventory for security audits, build dropdown menus populated with available groups, compare Bitwarden groups against groups in other systems for sync operations.

This action retrieves security and audit events from your Bitwarden organization. Events track everything from login attempts to password changes—essential for security monitoring, compliance reporting, and incident investigation.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Event"), Operation (set to "Get Many"), Return All (toggle to retrieve all matching events, optional), Limit (maximum events to return, defaults to 10, numeric input, optional), and Filters (click "Add Filter" to narrow results by date range, event type, or other criteria, optional but highly recommended for focused queries).

Use cases: Monitor for failed login attempts and alert security teams via Slack, generate weekly security audit reports for compliance, investigate incidents by pulling events within specific time windows.

This action modifies an existing collection in your Bitwarden organization. Collections organize credentials by project, team, or purpose—use this action to rename collections, change external IDs, or update other collection properties.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Collection"), Operation (set to "Update"), Collection ID (the unique identifier of the collection to modify, text input required), and Update Fields (click "Add Field" to specify which properties to change, optional).

Use cases: Rename collections to match updated project names, update collection external IDs for integration with external systems, batch-update collection settings during organizational restructuring.

This action retrieves detailed information about a specific group in your Bitwarden organization. Use it to verify group existence, check group properties, or pull group data into conditional workflow logic.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Group"), Operation (set to "Get"), and Group ID (the unique identifier of the group to retrieve, text input supporting expressions for dynamic values, required).

Use cases: Verify a group exists before attempting to add members, pull group details into notifications or approval requests, check group properties to determine workflow branching.

This action retrieves information about a specific collection in your Bitwarden organization. Collections are containers for organizing credentials—use this action to verify collection details or pull collection data into your workflows.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Collection"), Operation (set to "Get"), and Collection ID (the unique identifier of the collection to retrieve, text input required).

Use cases: Verify a collection exists before assigning it to a group, pull collection names into reports or notifications, check collection properties for conditional workflow logic.

This action retrieves multiple collections from your Bitwarden organization. Use it to audit your collection structure, build selection interfaces, or process collections in bulk.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Collection"), Operation (set to "Get Many"), Return All (toggle to retrieve all collections, optional), and Limit (maximum collections to return, numeric input, optional when "Return All" is enabled).

Use cases: Generate a complete collection inventory for auditing, build dynamic collection selection in custom interfaces, compare Bitwarden collections against project lists in other systems.

This action creates a new group in your Bitwarden organization. Groups are the foundation of access management in Bitwarden—use this action to automate group creation when new teams form or new projects launch.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Group"), Operation (set to "Create"), Name (the name for the new group, text input required), and Additional Fields (click "Add Field" to configure extra properties like external ID or access settings, optional).

Use cases: Auto-create Bitwarden groups when new Slack channels are created, provision project-specific groups triggered by project management tools like Notion, set up standardized group structures for new client onboarding.

This action permanently removes a group from your Bitwarden organization. Use it for cleanup operations—removing obsolete project groups, deprecated team structures, or groups created in error.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Group"), Operation (set to "Delete"), and Group ID (the unique identifier of the group to remove, text input or expression required).

Use cases: Clean up groups when projects are completed or archived, remove deprecated groups during organizational restructuring, delete test groups created during workflow development.

This action permanently removes a collection from your Bitwarden organization. Collections contain credential items—deleting a collection removes the organizational container while the underlying credentials may remain accessible through other collections or directly.

Key parameters: Credential to connect with (Bitwarden credentials via dropdown, required), Resource (fixed to "Collection"), Operation (set to "Delete"), and Collection ID (the unique identifier in UUID format of the collection to delete, text input required).

Use cases: Archive completed project collections automatically, clean up test collections from development workflows, remove deprecated collections during security audits.