Data Store

Data Node

Remember values between runs — dedupe items, count things, track what you've seen

Overview

The Data Store is your workflow's long-term memory. Unlike a normal variable, which forgets everything when a run ends, the Data Store keeps values safe from one run to the next. It's the tool you reach for when you need to avoid processing the same item twice, keep a running count, or remember the last thing you saw.

The classic use: don't repeat yourself

The "Check & Add" operation tells you whether a key is new. The first time it sees an order or listing it returns isNew = true and remembers it; every time after that it returns isNew = false — perfect for only acting on genuinely new items.

Parameters

Configuration options for this node

Store Name

Text Input

Required

A named bucket for your keys, tied to your account. Use one store per topic, like "seen-orders".

Default: default

Operation

Dropdown

Required

What to do: Check & Add (is it new?), Get, Set, Delete, Has (does it exist?), Increment (a counter), or Append (to a list).

Default: Check & Add

Key

Text Input

Required

The unique thing you're tracking — an order number, a listing ID, or a URL. Supports variables.

Example: order-{{ orderId }}

Value

Text / JSON

The value to store. Optional for Check & Add (defaults to the first-seen time); for Increment it's the amount to add (defaults to 1).

Example: {{ item.title }}

Output Variable

Text Input

Where the result lands, so later steps can read it — for example {{ dataStoreResult.isNew }}.

Default: dataStoreResult

Usage Example

Only notify me about new listings

Skip anything you've already been alerted about

Store Name: seen-listings

Operation: Check & Add

Key: {{ item.url }}

Then add an If Condition on {{ dataStoreResult.isNew }} and only send an alert when it's true.

Best Practices

Tip: One store per job

Give each workflow its own store name so their keys never mix. It keeps things easy to reason about and easy to reset.

Tip: Pick a stable key

Choose a key that never changes for the same item — an ID or a URL works well. If the key changes, the item will look "new" every time.

Data Store

Data Node

Remember values between runs — dedupe items, count things, track what you've seen

Overview

The classic use: don't repeat yourself

Parameters

Configuration options for this node

Store Name

Text Input

Required

A named bucket for your keys, tied to your account. Use one store per topic, like "seen-orders".

Default: default

Operation

Dropdown

Required

What to do: Check & Add (is it new?), Get, Set, Delete, Has (does it exist?), Increment (a counter), or Append (to a list).

Default: Check & Add

Key

Text Input

Required

The unique thing you're tracking — an order number, a listing ID, or a URL. Supports variables.

Example: order-{{ orderId }}

Value

Text / JSON

The value to store. Optional for Check & Add (defaults to the first-seen time); for Increment it's the amount to add (defaults to 1).

Example: {{ item.title }}

Output Variable

Text Input

Where the result lands, so later steps can read it — for example {{ dataStoreResult.isNew }}.

Default: dataStoreResult

Usage Example

Only notify me about new listings

Skip anything you've already been alerted about

Store Name: seen-listings

Operation: Check & Add

Key: {{ item.url }}

Then add an If Condition on {{ dataStoreResult.isNew }} and only send an alert when it's true.

Best Practices

Tip: One store per job

Give each workflow its own store name so their keys never mix. It keeps things easy to reason about and easy to reset.

Tip: Pick a stable key

Choose a key that never changes for the same item — an ID or a URL works well. If the key changes, the item will look "new" every time.

Data Store

Overview

The classic use: don't repeat yourself

Usage Example

Best Practices

Tip: One store per job

Tip: Pick a stable key

Related Documentation

Set Variable

If Condition

Apply to Each

Filter

Data Store

Overview

The classic use: don't repeat yourself

Usage Example

Best Practices

Tip: One store per job

Tip: Pick a stable key

Related Documentation

Set Variable

If Condition

Apply to Each

Filter