HashiCorp Vault

Manage secrets, authentication, and encryption via HashiCorp Vault.

Detail	Value
Category	Security
Base URL	https://vault.example.com/v1
Authentication	API Key
Endpoints	6
Connector key	hashicorp-vault

Using HashiCorp Vault in a workflow

1. Go to Connections and click New Connection.
2. Pick HashiCorp Vault from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET /secret/data/{path}	Read a secret
POST /secret/data/{path}	Write a secret
DELETE /secret/data/{path}	Delete a secret
GET /sys/health	Check Vault health
GET /sys/mounts	List secret engines
POST /transit/encrypt/{name}	Encrypt data

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /secret/data/{path}

Read a secret

Detail	Value
Operation ID	security.readSecret
Method	GET
Path	/secret/data/{path}

Parameters

Name	Location	Type	Required
path	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your HashiCorp Vault connection from the Connection dropdown.
3. In the Operation dropdown, select security.readSecret.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream HashiCorp Vault API reference.

POST /secret/data/{path}

Write a secret

Detail	Value
Operation ID	security.writeSecret
Method	POST
Path	/secret/data/{path}

Parameters

Name	Location	Type	Required
path	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your HashiCorp Vault connection from the Connection dropdown.
3. In the Operation dropdown, select security.writeSecret.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream HashiCorp Vault API reference.

DELETE /secret/data/{path}

Delete a secret

Detail	Value
Operation ID	security.deleteSecret
Method	DELETE
Path	/secret/data/{path}

Parameters

Name	Location	Type	Required
path	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your HashiCorp Vault connection from the Connection dropdown.
3. In the Operation dropdown, select security.deleteSecret.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream HashiCorp Vault API reference.

GET /sys/health

Check Vault health

Detail	Value
Operation ID	security.checkHealth
Method	GET
Path	/sys/health

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your HashiCorp Vault connection from the Connection dropdown.
3. In the Operation dropdown, select security.checkHealth.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream HashiCorp Vault API reference.

GET /sys/mounts

List secret engines

Detail	Value
Operation ID	security.listMounts
Method	GET
Path	/sys/mounts

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your HashiCorp Vault connection from the Connection dropdown.
3. In the Operation dropdown, select security.listMounts.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream HashiCorp Vault API reference.

POST /transit/encrypt/{name}

Encrypt data

Detail	Value
Operation ID	security.encrypt
Method	POST
Path	/transit/encrypt/{name}

Parameters

Name	Location	Type	Required
name	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your HashiCorp Vault connection from the Connection dropdown.
3. In the Operation dropdown, select security.encrypt.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream HashiCorp Vault API reference.