The secrets manager is the encrypted vault for every API key, token and credential your process needs. Reference a secret by name inside functions, workflows and connectors — the actual value stays hidden, even from the people who use it.
Store and manage secure configuration values for this process
Name is fixed. You can update the secret value.
Real processes call out to the outside world — payment gateways, messaging providers, databases, AI models. Each needs a key. The secrets manager keeps those keys encrypted and out of sight, so your logic stays clean and your credentials stay safe.
Every value is encrypted before it lands in storage. Plaintext is never written to disk, logs or backups — only the application can decrypt it at the moment of use.
The list shows a name, a type and a masked preview — never the full value. Once saved, a secret can be referenced and rotated, but not read back in plaintext.
Functions, workflows and connectors point at a secret by its name. The platform resolves it to the real value at runtime — your configuration only ever stores the reference.
A secret moves through three stages — and at no point does its plaintext value sit in your logic. The reference travels with your configuration; the value is fetched and injected only when the call actually fires.
The raw key is entered once and immediately masked.
Functions, workflows and connectors point at the name — never the literal value.
The value lives only for the duration of the outbound call.
Anywhere a credential is needed, the secrets manager quietly supplies it. Here's what pulls from the vault.
Connectors for Slack, Gmail, Stripe, WhatsApp, S3, banking and e-sign authenticate with stored secrets.
Explore →
Reference a secret by name inside any workflow step that calls an API — the value never sits in your logic.
Explore →
Shared assets and configuration that pair with secrets to define how your process talks to the outside.
Explore →
Multi-org, multi-process governance and RBAC decide who can manage secrets and where they're scoped.
Explore →
Add a secret once, reference it everywhere, and never paste a raw credential into a workflow again. Encrypted, masked and scoped — built into the platform.