Skip to main content
Secrets allow you to securely store API keys, credentials, and other sensitive values that modules and integrations need at runtime. Secrets are scoped to your organization and securely encrypted at rest. They are made available to processing modules during execution. Secrets management page showing list of configured secrets with names and types

​
Managing Secrets

​
Adding a Secret

1

Click Add Secret

Open the secret creation form from the Secrets page.
2

Enter Name and Value

Provide a name (used to reference the secret in modules) and the secret value. Names must contain only letters, numbers, hyphens, and underscores.
3

Save

The secret is encrypted and stored securely. The value will not be displayed again after saving.
Add Secret dialog showing name and value fields
Secret values are write-only. Once saved, you cannot retrieve the original value. You can only replace it with a new value.

​
Using Secrets in Modules

Modules can reference organization secrets by name. When a module executes, the platform injects the requested secrets into the module’s runtime environment.

​
Using Secrets in Service Bridges

Service Bridges can reference organization secrets for authentication headers. When a service bridge proxies a request, the platform resolves any secret references and injects the values into the outgoing request headers.

​
Secrets API

Secrets are managed through the organization-scoped API:
OperationEndpoint
List secret namesGET /api/organizations/{orgId}/secrets
Create or updatePOST /api/organizations/{orgId}/secrets
DeleteDELETE /api/organizations/{orgId}/secrets/{secretName}
Secret values can only be retrieved by the platform during module execution (via execution tokens). The API does not expose secret values to regular users.
Use descriptive names for secrets (e.g., OPENAI_API_KEY, AWS_ACCESS_KEY) so it is clear what each secret is used for.