Skip to main content
Stores are managed key-value resources that workflow Store nodes use to persist values across runs and workflows. Each store holds a timestamped series of entries indexed by key, written by workflow runs and optionally added or edited by hand. Open Settings and select Stores to manage your stores.

​
Creating a store

  1. Click New Store
  2. Enter a Name for the store. The name is how workflow Store nodes identify it in the node editor
  3. Optionally enter a Description to remind your team what the store is for
  4. Set the Retention limits that control how much data the store keeps (see below)
  5. Build the Value schema that every entry in this store must match (see below)
  6. Click Save
Once created, the store appears in the stores list and is available for selection in any workflow’s Store node.

​
Value schema

Every store requires a Value schema: a JSON object schema with at least one property, describing the object held under each key. Every value written to the store, whether by a workflow Store node or by hand, must match it. Ingestly adds a key property carrying the entry key to every stored value automatically, and an entryId property carrying the entry ID to entries written with one. Do not declare key or entryId in the schema: a schema that declares either is rejected on save, and a top-level entryId in a value written without an entry ID is removed.
Entries are capped at 256 KB each. A larger value is rejected, and a workflow Store node that tries to write one fails the step.

​
Retention settings

Every store has retention limits that cap storage automatically. Both values are required when you create or edit a store. Both limits are enforced independently: an entry is removed when it violates either rule.
Retention is applied asynchronously. Entries past the limit may remain briefly visible after a write before the cleanup runs.

​
Managing stores

Click a store row to open it and browse its entries in a paginated table (see Browsing entries below). From the row actions menu you can:
  • Edit: update the store’s name, description, retention settings, or value schema. Changes take effect immediately for new writes; existing entries are not retroactively affected by retention or schema changes until the next cleanup cycle
  • Download Excel: export every entry in the store to an .xlsx file. The workbook has one row per entry with the key, its entry ID (if any), its stored value, and the UTC timestamp it was last written
  • Clear: delete all entries in the store while keeping the store itself. Use this to reset accumulated data without reconfiguring workflows
  • Delete: permanently remove the store and all its entries

​
Browsing entries

Click a store to open its detail page, which lists the stored entries in a paginated table. Each row shows the key, the entry ID (a dash for entries written without one), the stored value, when it was first stored and last updated (UTC), the run that wrote it (linking to that run), and the source document. An entry that a Store node replaced through its Entry ID, or that you edited, shows the later Updated On time. Filter by key to narrow the list, or sort by the stored date. The detail page also has its own Download Excel button for the full export. Entries added by hand have no originating run, so the run column shows a Manual badge instead of a run link, and they have no source document.

​
Managing entries

You can add, edit, and delete individual entries directly from the store detail page.
  • Add an entry: click New Value in the page header to open the New Value dialog. Enter a Key (required, up to 500 characters) that identifies the time series; the key is set only on create and cannot be changed afterward. Optionally enter an Entry ID (up to 256 characters, a single value such as a slip number rather than a list or object) to name this entry under the key, the same way a Store node’s Entry ID does; it is set only on create. An entry ID that already exists under the key is rejected, so edit that entry instead. Enter the Value (JSON) in the JSON editor: it must be valid JSON and must match the store’s value schema. Click Create Value to save.
  • Edit an entry: click the Edit action on an entry row to open the Edit Value dialog. Only the value is editable; the key and entry ID cannot change. Click Save Changes to save.
  • Delete an entry: click the Delete action on an entry row to permanently remove that single entry after confirming in the dialog.
These actions affect one entry at a time and are distinct from the store-level Clear (removes all entries) and Delete (removes the whole store).
A workflow Store node caps its key at 256 characters, so an entry added by hand with a longer key can never be read back by a workflow. Keep manual keys within 256 characters unless the series is for reference only.

​
Importing entries

Click Import Excel on the store detail page to bulk-load entries from an .xlsx workbook with a header row, a Key column, a Value column, and an optional Entry ID column. A file produced by Download Excel imports as-is; its Stored On (UTC) column is ignored, and imported entries are timestamped when they land.
  • A row with an Entry ID replaces the stored entry with that key and entry ID, or creates it; when the file repeats an entry, the last row wins. A row without one adds a new entry. An entry ID that is a list or object stops the import.
  • Rows with an empty key are skipped; a row with an empty value stops the import.
  • Keys and entry IDs are capped at 256 characters, matching what a Store node can read.
  • Every value must match the store’s value schema.
  • The import is all-or-nothing (up to 10,000 rows): if any row is rejected, the error names the row number and nothing is written.
Imported entries are recorded as manual entries, so they show the Manual badge and are subject to the store’s retention limits like any other write.
Deleting a store that a workflow references breaks that workflow: the Store node shows Store not found in the editor, the workflow fails validation on the next save, and any step that still runs against the deleted store fails. Update or remove the Store nodes in affected workflows before deleting the store.

​
Plan limits

The number of stores available depends on your subscription plan. When you reach your plan’s store limit, the New Store button is disabled. Upgrade your plan or delete unused stores to create more. See subscription for plan details.

​
Permissions

Managing stores requires the Account.Store permission. The per-entry actions are gated by that permission’s individual actions: the New Value and Import Excel buttons require the create action, the Edit action requires the update action, and the Delete action requires the delete action. Each control only appears when you have the corresponding action. See roles and permissions for details.

Store node

Read from and write to a store inside a workflow

Connectors

Connect Ingestly to external services via OAuth

Roles and permissions

Control who can manage stores in your organization

Subscription

View plan limits and upgrade options