Import Members and Groups
bitwarden.import_members_and_groups
ActionBusiness appsconnection required
Calls the Bitwarden API with the connection's credentials.
Import members and groups from an external directory by external id, the same call Directory Connector makes.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Bitwarden
- Secret shape
- the organization API key client_secret, or {"client_secret": "…"}
- Config it needs
- region, client_id, base_url, identity_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
members Members to import as a JSON array; each entry needs an 'externalId' plus 'email', and may set 'deleted' to remove one. | array | No | — | array of object | [{"email":"jsmith@example.com","externalId":"external_id_123456"}] |
groups Groups to import as a JSON array; each entry needs a 'name', an 'externalId' and optionally 'memberExternalIds'. | array | No | — | array of object | [{"externalId":"external_id_123456","name":"Development Team"}] |
overwrite_existing When true the import replaces the organization's existing directory data instead of adding to it. | boolean | No | false | — | — |
large_import Set true when sending more than 2000 members or groups; Bitwarden cloud refuses a larger import without it. | boolean | No | false | — | — |
- At least one of members, groups must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"groups": [
{
"externalId": "external_id_123456",
"name": "Development Team"
}
],
"large_import": false,
"members": [
{
"email": "jsmith@example.com",
"externalId": "external_id_123456"
}
],
"overwrite_existing": false
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
accepted True once Bitwarden accepted the import request. | boolean | — |
members_sent How many member rows were sent. | number | — |
groups_sent How many group rows were sent. | number | — |
overwrite_existing Whether the import replaced existing data. | boolean | — |
{
"accepted": false,
"groups_sent": 0,
"members_sent": 0,
"overwrite_existing": false
}Notes
- Bitwarden answers this call with an empty 200, so the output reports what was sent.
- Bitwarden reports no per-row outcome, so this node cannot say which rows were created, updated or skipped.
See Import Members and Groups run in a workflow.
In a technical demo we add the Bitwarden connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.