Write to Data Store: <DataStoreName>
Description
Stores a value under a key in a Data Store, replacing any entry already there. The value must be exactly the shape the Data Store declares. Entries never expire, and they count towards the plan's Data Store storage; the run fails if the storage is full.
When to use
Use Write to Data Store to keep a value beyond the end of the run. It is an upsert: a new key creates an entry, an existing key replaces it whole. A map-shaped store is also replaced whole, so to change one item, read the map, put the new item into it, and write it back.
Writes are checked before they are stored. The value has to be the Data Store’s own model in its declared shape, and the run fails with a message if it is not. Storage is limited by the plan: Essentials includes 100 KB, Extra 1 MB, and Enterprise is set per contract. A write that would go over fails the run with the amount used, and one entry cannot be larger than the whole allowance. Overwriting an entry with something no larger is always allowed, so an organization over its limit can still shrink what it stores. Nothing is evicted automatically: delete entries, or upgrade, to make room.
The value is stored exactly as written. A pipeline can write the value of a secret variable here, and it will then be visible to people who can open the Data Store, so store only what you would be comfortable showing there.
Data Store is not available on the Experimental plan. The node fails the run with a message saying so. It works in pipelines only, not in functions, and a pipeline that uses it cannot be published to the marketplace.
Pins
Input pins
| Pin | Type | Default | Notes |
|---|---|---|---|
| Key | string | — | The key to store the value under, 1 to 512 characters. |
| Value | model | — | The value to store, in the shape the Data Store declares: a single model, a list of models, or a map of key to model. Anything else fails the run. |
Output pins
| Pin | Type | Notes |
|---|---|---|
| Entry size (bytes) | integer | How much of the plan's storage the entry uses: the length of the key plus the length of the value as JSON. |
| Created new entry | boolean | True when the key was new, false when an existing entry was replaced. |
Execution pins
| Pin | Direction |
|---|---|
| In | Input |
| Out | Output |
Example
After computing a day’s totals, a pipeline builds a DailyTotals model with Make
and wires it into Write to Data Store: Daily totals with the key 2026-10-11. The
next morning’s report reads the key for yesterday with Read from Data Store, and a
monthly clean-up pipeline removes the entries it no longer needs.