How to use static data in n8n?

To use static data in n8n, you store it on the workflow level using the built‑in $input.item.json-like object called $workflow.staticData. n8n keeps this data between workflow executions, so you can read and write to it without a database. It’s meant for small, simple state like counters, timestamps, or configuration values you don’t want hard‑coded in nodes.

 

What Static Data Is (and Why It Matters)

 

Static data is a special JSON object attached to a workflow. Unlike normal node data, which only exists during a single run, static data is persisted by n8n and is available on the next execution. Think of it as tiny permanent storage built into the workflow.

You access it in expressions or in Function / Function Item nodes through $workflow.staticData. If the workflow uses triggers (Cron, Webhook, etc.), static data will survive between runs as long as your n8n instance can persist executions (most setups do).

• Use cases: counters, remembering last fetched IDs, storing config, caching.
• Not for: large datasets, logs, secrets, anything requiring heavy writes.

 

How to Read and Write Static Data

 

You typically interact with it inside a Function or Function Item node. Here’s a clean example that increments a counter:

// Access staticData in "global" mode (persists across executions)
const data = $workflow.staticData;

// Initialize if missing
if (!data.counter) {
  data.counter = 0;
}

// Update it
data.counter++;

// Return current counter
return [{ counter: data.counter }];

This counter will survive every time your workflow runs. No database needed.

 

Static Data Modes: Global vs. Node

 

Static data comes in two flavors:

• $workflow.staticData: shared across the entire workflow. Most common.
• $node["NodeName"].staticData: scoped to a specific node. Rarely used but available if you need node‑local state.

Both persist across executions. Global is what most production workflows use.

 

Using Static Data in Expressions

 

You can also read static data directly in UI expressions without a Function node. For example:

// Example expression
{{$workflow.staticData.lastRunTimestamp}}

This is helpful if you store configuration values and want to reference them anywhere.

 

When Static Data Updates Persist

 

Static data only saves when the workflow successfully finishes. If the workflow errors, the changes to static data are not written. This is intentional so you don’t corrupt your “saved state” mid‑execution.

• A normal successful run → static data is saved.
• A failed run → static data reverts to the previous saved version.

This behavior affects things like counters or pagination trackers, so plan accordingly.

 

Important Production Considerations

 

• Static data resets if you export the workflow JSON (it is not included in the export).
• Static data is stored in your n8n database, so it survives restarts.
• Not designed for large objects (keep it small: numbers, small strings, a few keys).
• Don’t use it for secrets — use Credentials.
• Don’t use it for high‑frequency writes — there’s a small write cost at the end of every run.

 

Simple Real-Life Example: Remember Last Processed ID

 

This is common when pulling from an API that doesn’t support webhooks.

const data = $workflow.staticData;

// read last ID or set default
const lastId = data.lastId || 0;

// call your API here (this is an example)
const newId = lastId + 5; // pretend we got new data

// store the updated ID
data.lastId = newId;

// output something
return [{ lastProcessed: newId }];

This makes sure the next time the workflow runs, it knows where it left off.

 

In short: using static data in n8n is the simplest way to give your workflow memory. It’s small, reliable, and perfect for lightweight state that needs to persist across executions.