List Events
bitwarden.list_events
ActionBusiness appsconnection required
Calls the Bitwarden API with the connection's credentials.
Read a page of the organization's event log, filtered by date, acting user or item; with no filter Bitwarden returns the last 30 days.
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
5 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 |
|---|---|---|---|---|---|
start Earliest event date as an ISO-8601 timestamp; must be before 'end'. | string | No | — | iso8601 format | 2026-09-01T00:00:00Z |
end Latest event date as an ISO-8601 timestamp; must be after 'start'. | string | No | — | iso8601 format | 2026-09-08T00:00:00Z |
acting_user_id Only events performed by this Bitwarden user id. | string | No | — | — | a2549f79-a71f-4eb9-9234-eb7247333f94 |
item_id Only events about this vault item id. | string | No | — | — | 3767a302-8208-4dc6-b842-030428a1cfad |
continuation_token The cursor from a previous call's 'continuation_token', to read the next page. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"acting_user_id": "a2549f79-a71f-4eb9-9234-eb7247333f94",
"end": "2026-09-08T00:00:00Z",
"item_id": "3767a302-8208-4dc6-b842-030428a1cfad",
"start": "2026-09-01T00:00:00Z"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The objects Bitwarden returned in this response. | array | — |
count How many objects are in 'items'. | number | — |
continuation_token Cursor for the next page, or null when Bitwarden sent none. | string | — |
{
"continuation_token": "",
"count": 0,
"items": []
}Notes
- Each event carries Bitwarden's numeric 'type'; the meaning of each number is in Bitwarden's event type reference.
- One call returns one page: follow 'continuation_token' to read the rest.
See List Events 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.