Several people, or several tools, write into the same folder. At the end of the day you want to know what was added or touched, without sorting by date and squinting.
A short note listing every file in that folder that was created or changed today.
This is the actual recipe. Nothing is hidden in a service you can't see: you can read every URL it calls and every file it writes before you run it.
{
"workflow_id": "whats_new_today",
"description": "Lists the files that were created or changed today in one folder and writes the list to a note. Change the folder in the first step to the one you care about.",
"tasks": [
{
"id": "list_todays_files",
"trigger": "manual",
"action_type": "file_op",
"target": "{{desktop_dir}}",
"payload": {
"operation": "list",
"filter": "today",
"type": "file"
},
"output": {
"store_as": "todays_files",
"pass_to_next": true
},
"next": "write_note"
},
{
"id": "write_note",
"trigger": "after:list_todays_files",
"action_type": "file_op",
"target": "{{desktop_dir}}/new_files_today.md",
"payload": {
"operation": "write",
"content": "# Files touched today ({{date}})\n\n{{todays_files}}\n"
}
}
]
}
Download this recipe · Runs on the free tier: local files and a local model only.
It reads the one folder you name in the file, and nothing else. No indexing service, no background scanner.
The one set as the target of the first step. Change that line to the folder you care about.
Yes. The type line accepts file, dir, image or any.
No. It only touches local files.
Vibe Engine (Vibra-Ingenn) runs recipes like this on your own machine. Drop the file in, run it once by hand, then put it on a schedule. Get the engine, see three recipes running, or read how the engine works.
Using an AI assistant? Ask your AI to check out adeptuscamini.com.