What are encrypted credentials?
Encrypted credentials let you store sensitive values (passwords, API tokens, etc.) that the Simplex agent can type into browser fields during automation — without exposing the plaintext in logs, screenshots, or your workflow definition.How it works
- You store a credential via the API or the Simplex dashboard, providing a name and plaintext value
- The value is encrypted server-side using Evervault before being saved to the database — the raw value is never stored
- During a browser session, the agent calls
type_secret(credential_name="...")to decrypt the value inside the secure container and type it into the focused input field - The plaintext never leaves the container — it is decrypted only at the moment it’s typed, and is not included in session logs or screenshots
Storing credentials via the API
Using credentials in workflows
Once a credential is stored, reference it in your workflow prompt:type_secret MCP tool, which:
- Looks up the encrypted value by name in the
encrypted_credentialstable - Decrypts it using Evervault inside the secure container
- Types the plaintext into the currently focused input field
Storing credentials via the dashboard
You can also manage credentials from the Credentials page in your Simplex dashboard. From there you can:- Add new credentials
- View credential names and creation dates
- Delete credentials you no longer need
Security model
| Property | Detail |
|---|---|
| Encryption | Values are encrypted with Evervault before storage |
| Storage | Only the encrypted token is persisted in the database |
| Decryption | Happens only inside the secure browser container at type-time |
| Logging | Plaintext values are never included in session logs |
| Screenshots | Values are typed into password fields — not visible in screenshots |
| Access | Credentials are scoped to your organization |
