Remember settings and timestamps between automation runs

Gives any automation a simple memory so it can pick up where it left off each time it runs.

How the work actually flows

It branches. Exactly one path is taken.

Pattern: Exclusive Choice (4) · Simple Merge (5)

flowchart TD trig>"automation run begins"]:::trig s0[("look up stored value")]:::store s1["decide stored value or default"]:::task s2["use value for this run"]:::task s3[("save updated value back")]:::store trig --> s0 s1 --> s2 s2 --> s3 gx{"× does a value exist"}:::gate s0 --> gx p00["use stored value"]:::task gx -->|"value found"| p00 p10["use default value"]:::task gx -->|"no value yet"| p10 jn{"○ value ready"}:::gate p00 --> jn p10 --> jn jn --> s1 out[/"a value persisted between runs"/]:::out pay{{"automations remember their own history"}}:::pay s3 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepA record or sheetOne path onlyPaths rejoinResultPayoff
Build size
Standard

A mid-size build with several tools working together.

Business functions
General Automation
Connects
Data Tables

The problem it solves

Without a way to remember what happened last time, an automation has no sense of history, so it either repeats work or misses new activity. You end up needing a workaround just to track a single value like a last-checked date.

Who it fits

Best for teams building or maintaining multiple automations that need to track a running value, like a last-checked date.

How it works

  1. An automation looks up a stored value by its name before it runs its main task
  2. If no value exists yet, a default is used
  3. The value is used to decide what work needs to happen this run
  4. The updated value is saved back for next time
What you get

Automations that pick up where they left off

You get automations that remember their last run and settings automatically, so every workflow you rely on stays in sync without extra setup.

What you get

A stored value, like a last-checked date, that stays consistent from one automation run to the next.

What you need

No extra account is needed beyond your existing automation platform.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Calculate shopping cart totals and apply discounts automatically

Automatically totals each shopping cart and applies a discount when the order is large enough.

Standard

Get alerted in Microsoft Teams when a site goes offline

Checks your Unifi network sites on a schedule and posts a Microsoft Teams alert the moment one drops offline.

Standard

Shorten long URLs automatically with a custom domain

Turns any long web link into a short, branded URL using your own custom domain in seconds.

Standard

Write personalized LinkedIn connection notes with AI

Reads each prospect's LinkedIn profile and uses AI to write a personalized connection request message.

Advanced
Back to the AI Playbook