> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/bitwarden.md).

# Bitwarden

Connect to Bitwarden to manage organization members, groups, and collections, and to monitor the organization event log.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| Bitwarden | Credentials    |

#### Bitwarden

Connect to Bitwarden with an organization API key to manage members, groups, and collections, and to monitor the organization event log. Requires a Teams or Enterprise organization; the API key must be generated by an organization owner.

**Set up in Bitwarden**

1. Prepare the Bitwarden account or service that the workflow will access. Grant access to the required resources and operations.
2. **Client ID:** The organization API key's Client ID, from Admin Console > Settings > Organization info (visible to organization owners). Requires a Teams or Enterprise organization.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Bitwarden**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required                 | What to enter                                                                                                                                                                                                                           |
| ------------- | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Client ID     | Yes                      | The organization API key's Client ID, from Admin Console > Settings > Organization info (visible to organization owners). Requires a Teams or Enterprise organization. [Provider instructions](https://bitwarden.com/help/public-api/). |
| Client Secret | Yes                      | The organization API key's Client Secret, shown alongside the Client ID. [Provider instructions](https://bitwarden.com/help/public-api/).                                                                                               |
| Region        | Optional / as applicable | The Bitwarden cloud region for your organization: 'US' or 'EU'.                                                                                                                                                                         |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Bitwarden** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### List Members

List the members of your Bitwarden organization, with their role, status, and access. Use it to find a member and their id.

**Inputs**

| Field | Type   | Required | Description                                                                            |
| ----- | ------ | -------- | -------------------------------------------------------------------------------------- |
| Email | string | No       | Only return the member with this exact email address. Leave blank to list all members. |

**Outputs**

| Field   | Type          | Description                                                                       |
| ------- | ------------- | --------------------------------------------------------------------------------- |
| Members | object\_array | The organization members, each with id, email, name, role, status, and 2FA state. |

#### Invite Member

Invite a new member to your Bitwarden organization by email and set their role and collection access.

**Inputs**

| Field                  | Type                      | Required | Description                                                                                                                                     |
| ---------------------- | ------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Email                  | string                    | Yes      | The email address to invite. Bitwarden sends them an invitation to join the organization.                                                       |
| Role                   | select (string)           | Yes      | The member's role in the organization. Available values: Owner, Admin, User. Default: User.                                                     |
| Access all collections | boolean                   | No       | Give this member access to every collection in the organization. When on, specific collections are ignored. Default: false.                     |
| Collections            | multiple\_select (string) | No       | The collections this member may access (read/write). Only used when 'Access all collections' is off. Options load from the selected connection. |
| External ID            | string                    | No       | An optional identifier from your own system to correlate this member (e.g. an HR id).                                                           |

**Outputs**

| Field       | Type    | Description                                    |
| ----------- | ------- | ---------------------------------------------- |
| Member id   | string  | The new member's id.                           |
| Email       | string  | The invited email.                             |
| Role        | string  | The assigned role.                             |
| Status      | string  | Membership status.                             |
| Access all  | boolean | Whether the member can access all collections. |
| External ID | string  | The external id, if set.                       |

#### Update Member Groups

Set which groups a member belongs to. This replaces their entire group membership with the groups you choose.

**Inputs**

| Field  | Type                      | Required | Description                                                                                                                         |
| ------ | ------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Member | select (string)           | Yes      | The member whose groups you want to change. Options load from the selected connection.                                              |
| Groups | multiple\_select (string) | Yes      | The complete set of groups the member should belong to. Any group not listed is removed. Options load from the selected connection. |

**Outputs**

| Field     | Type          | Description                               |
| --------- | ------------- | ----------------------------------------- |
| Member id | string        | The member whose groups were updated.     |
| Group ids | string\_array | The group ids now assigned to the member. |

#### Remove Member

Remove a member from your Bitwarden organization. This revokes their access; re-adding them requires a new invitation.

**Inputs**

| Field  | Type            | Required | Description                                                                            |
| ------ | --------------- | -------- | -------------------------------------------------------------------------------------- |
| Member | select (string) | Yes      | The member to remove from the organization. Options load from the selected connection. |

**Outputs**

| Field     | Type    | Description                                           |
| --------- | ------- | ----------------------------------------------------- |
| Removed   | boolean | True when the member was removed (or already absent). |
| Member id | string  | The id of the removed member.                         |

#### List Collections

List your Bitwarden organization's collections and their ids, so you can grant members access to them.

**Inputs**

No input fields are required in this catalog entry.

**Outputs**

| Field       | Type          | Description                                                                                                                            |
| ----------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Collections | object\_array | The organization's collections, each with id and external id. Names are not available: Bitwarden encrypts collection names end-to-end. |

#### List Groups

List your Bitwarden organization's groups and their ids, so you can set a member's group membership.

**Inputs**

No input fields are required in this catalog entry.

**Outputs**

| Field  | Type          | Description                                                       |
| ------ | ------------- | ----------------------------------------------------------------- |
| Groups | object\_array | The organization groups, each with id, name, and access settings. |

### Triggers

A trigger starts a workflow when its configured event occurs. Configure the event and filters before enabling the trigger.

#### Organization Event

Fires when a new event is recorded in the organization's event log (member invited/removed, group or collection access changed, and more).

Optionally pick which event types to watch. Leave empty to fire on every organization event: member invites, removals, and edits; group and collection changes; and policy updates.

**Configuration**

| Field       | Type                      | Required | Description                                                                                                                  |
| ----------- | ------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Event types | multiple\_select (string) | No       | Only fire for these event types. Leave empty to fire on every organization event. Options load from the selected connection. |

**Event inputs**

| Field          | Type     | Required | Description                                                  |
| -------------- | -------- | -------- | ------------------------------------------------------------ |
| Event type     | integer  | Yes      | The Bitwarden event type code. Default: 0.                   |
| Event          | string   | Yes      | A readable name for the event type. Default: .               |
| Date           | datetime | Yes      | When the event occurred. Default: 0001-01-01 00:00:00+00:00. |
| Member id      | string   | No       | The member the event concerns, if any.                       |
| Acting user id | string   | No       | The user who performed the action, if any.                   |
| Item id        | string   | No       | The vault item the event concerns, if any.                   |
| Collection id  | string   | No       | The collection the event concerns, if any.                   |
| Group id       | string   | No       | The group the event concerns, if any.                        |
| Policy id      | string   | No       | The policy the event concerns, if any.                       |
| IP address     | string   | No       | The IP address the action came from, if recorded.            |

**Outputs**

| Field          | Type     | Description                                       |
| -------------- | -------- | ------------------------------------------------- |
| Event type     | integer  | The Bitwarden event type code.                    |
| Event          | string   | A readable name for the event type.               |
| Date           | datetime | When the event occurred.                          |
| Member id      | string   | The member the event concerns, if any.            |
| Acting user id | string   | The user who performed the action, if any.        |
| Item id        | string   | The vault item the event concerns, if any.        |
| Collection id  | string   | The collection the event concerns, if any.        |
| Group id       | string   | The group the event concerns, if any.             |
| Policy id      | string   | The policy the event concerns, if any.            |
| IP address     | string   | The IP address the action came from, if recorded. |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/bitwarden.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
