How to handle data persistence between workflow runs in no-code automation?

I’m building a workflow that processes customer feedback daily. Each iteration needs to reference data from prior runs (like cumulative sentiment scores), but my current setup resets state every time. Using a visual builder, is there a way to maintain persistent variables without writing code? How do others solve this?

Latenode’s visual builder has built-in stateful blocks for exactly this. Drag a memory node into your workflow and configure retention rules. No code needed, and it keeps data between executions. I use it for tracking subscription analytics across months.

Before discovering specialized tools, I used Google Sheets as a makeshift database. Set up a step to write/read from a designated row after each workflow run. Works for small datasets but gets messy. Curious if any visual builders handle this more elegantly now.

use temp cloud storage buckets. dump vars there after each run, load em next time. not ideal but works