Delete Collection
bitwarden.delete_collection
ActionBusiness appsconnection required
Calls the Bitwarden API with the connection's credentials.
Permanently delete a collection; this cannot be undone.
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
1 field, 1 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 |
|---|---|---|---|---|---|
collection_id The collection to act on, by its Bitwarden collection id. | string | Yes | — | — | 539a36c5-e0d2-4cf9-979e-51ecf5cf6593 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"collection_id": "539a36c5-e0d2-4cf9-979e-51ecf5cf6593"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
deleted True once Bitwarden accepted the deletion. | boolean | — |
collection_id The collection that was deleted. | string | — |
{
"collection_id": "",
"deleted": false
}Notes
- Bitwarden answers this call with an empty 200, so the output reports what was sent.
See Delete Collection 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.