Keystore

Use Keystore to manage reusable project data and configuration values.

A keystore contains a schema or default payload and can also store key-based data rows. Keystores can use either JSON or RAW format.

Open Keystore

To open Keystore:

1. Open a project.
2. In the left navigation, go to Storage.
3. Select Keystore.

View keystores

The Keystore overview lists the keystores in the selected project.

The table includes:

Column	Description
Keystore ID	The keystore identifier. A description may appear below the identifier.
Type	The keystore format, such as JSON.
Created	The date and time the keystore was created.
Updated	The date and time the keystore was last updated.
Last response	The most recent response information, when available.
Actions	Available row actions for the keystore.

Create a keystore

To create a keystore:

1. Select New Keystore.
2. Choose JSON or RAW.
3. Enter the schema or default payload.
4. Select Save.
5. Enter the keystore identifier and optional description.
6. Save the keystore.

note

The keystore identifier must use lowercase letters, numbers, or underscores.

Edit a keystore

Open a keystore from the overview to view or edit its schema.

JSON keystores open in a tree editor. You can expand and collapse nodes, search within the structure, and edit values.

RAW keystores open in a code editor.

Select Save to store your changes.

important

Take care when editing a keystore schema. Your changes will affect new flows that use it.

Open keystore data

Keystores can contain individual key payloads.

From the Keystore overview, open the data for a keystore to view its stored keys. The data list lets you search, sort, add new keys, open payloads, and delete key rows when your permissions allow it.

Edit a key payload

Open a key from the keystore data list to view its payload.

The payload editor matches the keystore type:

Keystore type	Editor
JSON	JSON editor
RAW	RAW editor

Select Save to update the payload.

Validation and errors

Flowize validates keystore and key data before saving.

Keystore identifiers must be unique.

A keystore cannot be deleted while it still has stored data rows.