Cache

Add a cache command

In your workflow, add a command and choose Cache. The four commands use the same key to store, find or remove a value. Keys are case-sensitive: product-summary and Product-summary are different.

Use the familiar value selector to enter a key or choose a workflow variable. Give the command's result a name in Return as so later commands can use it.

View larger image

Choose where to share a value

This workflow keeps the key within the workflow that started the run. Calls to that workflow can reuse it. A function called from an endpoint shares the endpoint's cache scope for that run.

This workspace lets endpoints, server functions and events in the same workspace use the same key. Choose this when several workflows deliberately share the same temporary data. Other workspaces, including Dev and Prod, keep separate entries.

For private or user-specific data, include the current user's ID in the key, for example profile-summary-{{user_id}}. A key does not automatically separate users. Keep authentication and permission checks before reading private data. Shared public summaries can use a common key.

Set cache value

Choose a Key, the Value to save and how many seconds it should last. The default is 300 seconds (five minutes). Choose a whole number from 1 to 86,400 seconds (one day). Saving the same key again replaces its value and starts the chosen duration again.

The result is true when the value was saved and false when temporary storage was unavailable. The workflow should still be able to use the original value if storage fails.

View larger image

Get cache value

Choose the same key and sharing option used when saving. The result contains:

• found: true when the entry is available; false when it has expired, was removed or cannot be read.

• value: the saved data when found; otherwise null.

If Return as is cached_summary, check cached_summary.found with a condition. When true, use cached_summary.value. Otherwise, obtain a fresh summary and save it with Set cache value.

Check found rather than testing whether the value is true: false, 0, an empty list and null can all be valid cached values.

View larger image

Has cache value

Return true if the key currently exists, or false if it is missing or unavailable. This does not return its data. An entry can expire between commands, so use Get's found result when you also need the value.

Delete cache value

Remove a key when its original data changes. For example, after updating a product, remove its cached summary so the next request obtains the updated information.

The result is true if an entry was removed and false if it was already missing or storage was unavailable. Use the same sharing option as the Set command.

Test your workflow

Tests use their own cache, including tests with Use live data enabled. They do not read or change entries used by real calls. Repeated tests can share test entries, so use Delete or a different key when you need a fresh start.

Try Set, Get, Has and Delete with a short duration. Confirm Get returns found: false after expiry or removal. Cache commands are available in server workflows, not page workflows or database transactions.

This test stores a summary, reads it, deletes it and then confirms it is missing. The saved zero and false values are preserved.

View larger image

Limits and useful habits

Keep keys short and meaningful; each key supports up to 1,024 bytes. Values support ordinary text, numbers, booleans, objects, lists and null, up to 2 MiB. Avoid saving files or very large query results.

Dates, including dates within database results, are returned as ISO-formatted text, such as 2026-10-15T10:30:00.000Z. Convert them back to dates if a later command needs a date value.

A workspace supports up to 32 active entries for real calls and a separate 32 for tests. If all entries are in use, saving a new key returns false. Replace an existing key, delete an entry you no longer need or let it expire before saving another.

Entries may disappear before their chosen duration if temporary storage is cleared or unavailable. Choose durations that fit how often the original data changes. Concurrent requests can both miss a key and obtain fresh data; caching is not a lock and does not guarantee that an action runs only once.

Do not use cached values as your only record of payments, stock changes or other important actions. Existing authentication, API limits and workflow permissions still apply.