Documentation

Schedule trigger

Starts the workflow by itself: every hour, every day, or on chosen days. Switch it on when the workflow is ready, and set the most it may spend on each run that starts by itself.

See the starting point “A post every day”: a new post with a picture every day, with nobody pressing Run.

Memories

A memory is a named list of short texts kept in your workspace, from one run to the next, for as long as you want it. Every workflow in the workspace can use it, so a list such as “Never say” is written once and read everywhere. Keeping and reading one is free: no model is asked.

• Save to memory — keeps the text that reaches it in a memory when the run gets here, for a Memory block to read on a later run, in this workflow or another. What you wrote yourself is never changed. Free: no model is asked. Each run adds an entry, or, if you set it to, replaces what earlier runs saved.
• Memory — hands on the newest entries (20 to begin with, or all of them) as one text, or as a list, an entry each. Write its name as a variable in a prompt, such as {{Posts made}}, and a Writer is told what is kept. At most 24,000 characters are handed on, newest first, and a memory that cannot be read stops the block rather than being read as empty.
• Memory, in the menu — every memory, what it holds and which workflows use it. Add an entry yourself, change one, take one out, search a long one, empty it or delete it.

A memory keeps 100 entries to begin with (10 to 200), each up to 4,000 characters, and a workspace up to 50 memories. When one is full, the oldest entry a run saved makes room; what you wrote yourself is never removed by a run. The same words are never kept twice.

A block that reads a memory is new work whenever the memory has changed, and is reused, at no cost, while it has not. Whatever a run saves comes back into prompts on later runs — words taken from a web page or written by a model too — so look at what a memory holds now and then, and take out anything you do not want a model to be told. A rule in a memory is something a model is told, and usually keeps, not a filter.

See the starting point “A post every day, never the same one”: a new post every day that never repeats one, kept in a memory you can change. Its memory, “Posts made”, is made with the workflow.

A Writer that remembers

Set a Writer block to remember, and it is shown what it wrote on earlier runs before it writes again — so a workflow that runs every day does not say the same thing twice. It is written anew each time, so it still costs what any other run of that block costs. It is the quickest way for one Writer not to repeat itself; use a memory when you want to see or change what is kept, add to it yourself, or share it between blocks and workflows.