Vault Client
The Vault client provides secure credential management with AES-256-GCM encryption. Store usernames, passwords, and other sensitive data for use in workflow executions.All sensitive fields (
user_name, password, and tfa_secret) are automatically encrypted by the SDK before being sent to CloudCruise servers. Plaintext credentials are never transmitted or stored.Setup
encryption_key is required for vault operations. Get it from CloudCruise Settings.
Creating a Vault Entry
Useclient.vault.create() to store new credentials:
Parameters
VaultEntryInput Fields
Provider-Backed Credentials (1Password)
If your workspace has a 1Password connection, you can bind a vault entry to a 1Password item instead of storing auser_name and password. CloudCruise resolves the username, password, and one-time code from 1Password at run time — the secret values are never stored in CloudCruise.
Use client.secret_providers to discover the connection and item reference, then pass secret_provider_id and secret_ref to create() (or update()):
SecretProvider Fields
SecretProviderItem Fields
Validation enforced by the SDK before the request is sent:
secret_provider_idandsecret_refmust be provided together.- A provider-backed entry cannot also include
user_name,password, ortfa_secret— those are resolved from the provider. secret_cache_ttl_secondsrequiressecret_provider_id/secret_refand must be a non-negative integer.
Getting Vault Entries
Retrieve vault entries with optional filtering:GetVaultEntriesFilters
When filtering, both
domain and permissioned_user_id must be provided together.Updating a Vault Entry
Update an existing vault entry:Required Fields for Update
All other
VaultEntryInput fields are optional. Include only the fields you want to change.
Deleting a Vault Entry
Delete a vault entry by domain and user ID:Using Vault Entries in Workflows
Reference vault credentials in workflow runs by passing thepermissioned_user_id as an input variable:

