Ligantic
Knowledge Base
Tutorials
Updates
Search Articles
Login
Free Sign Up
Home
Get Started
Tutorials
How-to guides
Reference
Explanation
Spaces
Schemas
Flows
Experiences
Endpoints
SDK and CLI
Browse documentation
Home
Get Started
Spaces
Schemas
Flows
Experiences
Endpoints
SDK and CLI
Docs
/

Secret - Set

Type identifier: secret:set Category: Secret Operations

Description

The Secret - Set node securely stores a secret value in the secret store. Secrets are encrypted at rest and can be retrieved later using the Secret - Get node. Use this node to store API keys, passwords, tokens, and other sensitive credentials.

Input Handles

Handle

Type

Description

trigger

control

Triggers the set operation.

value

string

The secret value to store.

path

string[]

(Dynamic) Path to store the secret at.

Output Handles

Handle

Type

Description

success

control

Triggered when the secret is stored.

error

control

Triggered when storage fails.

Configuration Options

Option

Type

Default

Description

Path

string[] or dynamic

[""] (unselected)

Path for the secret in the store.

Value

string or dynamic

dynamic

The secret value to store.

For a literal path, the Secret picker lists existing Space secrets. Enable Advanced to enter a path manually, including a new path, or enable Dynamic? to supply the path through its input handle. An existing path that is not listed opens in Advanced mode without changing the saved path. If the list cannot load, an error is shown and the path remains editable manually. Changing between the picker and Advanced does not change the stored path or value.

New nodes start with no secret selected and Advanced off.

The unselected default is not a valid execution path. Select a secret or enter a complete path before running the Flow. Empty path segments are rejected without contacting the secret store; this applies in both picker and Advanced modes.

Behaviour

  1. Receives trigger and value
  2. Encrypts the secret value
  3. Stores at the specified path
  4. Triggers success or error control flow

Overwriting

If a secret already exists at the path:

  • The existing value is overwritten
  • No warning is provided

Security

  • Values are encrypted before storage

Examples

Store API Key

Configuration:

  • Path: ["external-api", "key"]
  • Value: dynamic

Input:

  • value: "sk-abc123..."

Rotate Credentials

Flow:

  1. Integration - HTTP: Request new API key
  2. Secret - Set: Store the new key (automatically replaces value)

Related pages

Secret - Get
The Secret - Get node retrieves a secret value from the secure secret store. Secrets are stored encrypted and are only decrypted when needed. The retrieved value is returned as a wrapped secret that can be passed to other nodes requiring credentials.
Page not found. It may have moved or may not be published.
Browse documentation