Restore Member Access
bitwarden.restore_member
ActionBusiness appsconnection required
Calls the Bitwarden API with the connection's credentials.
Restore a revoked member to the status they held before revocation.
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 |
|---|---|---|---|---|---|
member_id The member to act on — the organization member id, not the Bitwarden user id. | string | Yes | — | — | e68b8629-85eb-4929-92c0-b84464976ba4 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"member_id": "e68b8629-85eb-4929-92c0-b84464976ba4"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
restored True once Bitwarden accepted the restore. | boolean | — |
member_id The member whose access was restored. | string | — |
{
"member_id": "",
"restored": false
}Notes
- Bitwarden answers this call with an empty 200, so the output reports what was sent.
- Bitwarden cloud has this endpoint; a self-hosted server older than the release that added it answers 404.
See Restore Member Access 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.