Filer Usecase
Put the Digest Where Your Team Already Looks
A Filer folder agent notices new updates, writes a digest, and logs it straight into your team's Notion database — no one has to copy it over by hand.
- File event
- Chat
What you get
A digest sent over chat is immediate, but it gets buried the moment the next message arrives — nobody scrolls back a week later to find it. A digest written to a local file sits in a folder nobody else opens. Either way, the one place your team actually goes looking for "what happened" doesn't get updated.
Point a Filer folder at where updates land instead. Its agent reads what's new, writes a short digest, and creates a page in your team's Notion database — the same place the team already searches for answers.
How to do it
Screenshots below are from a real run, using synthetic status notes in place of real team updates.
Needs: the Notion plugin, connected with an internal integration token and a target database.
What it needs
- A Filer folder set to Full Auto, so each file is logged while you are away — below Full Auto each save to Notion waits for your approval, and a run nobody answers within two minutes finishes without saving
- The Notion plugin connected — an internal integration token and a target database — and allowed for the folder if it limits its plugins (Filer AI › the folder › Plugins & Skills)
- An inference endpoint — Local AI, Frontier AI (API key), or a local LLM server
Connect Notion, once
Install the Notion plugin from Connect, paste in an internal integration token from Notion's own settings, and point it at the database new pages should land in. Filer never shows the token back to you once it's saved.
Updates land in a folder
Short status notes accumulate in the folder — the kind of thing a team drops in throughout the week. A short instructions file already in place says what to do with them: read every note, write a one-paragraph digest, and log it as a new Notion page.
It reads, summarizes, and logs it
A new note landing is the trigger — no one has to ask. The agent reads every note in the folder, works out one digest across all of them, and creates the page in Notion on its own. Filer's own activity log shows exactly which steps ran.
What the Notion page actually says Marketing reported a Q3 newsletter open rate of 42%, up from 37%, with the next campaign launching Monday. Invoices processed 3 vendor payments (Acme Supplies, Northwind Traders, Contoso Logistics), with 1 on hold pending a corrected tax document and no overdue payments. Support closed 4 tickets with an average first response time of 3 hours, and 1 ticket was escalated to engineering.
The screenshots and outputs on this page come from a real run of Filer, not a mockup.
Where else this applies
The mechanism is generic — read what accumulated, write one summary, log it where people already look. Notion isn't the only destination that fits, and status notes aren't the only source:
- Team wiki — an engineering runbook page kept current from scattered incident notes, instead of drifting stale.
- Support rollups — a week of individual ticket notes condensed into one trend-level entry.
- Client-facing status pages — internal updates condensed into the external summary a client account actually gets shown.
Other ways in
The walkthrough shows a new note's arrival as the trigger. You're not stuck waiting for the next one — the agent runs the same read-summarize-create-page sequence on demand, without any note needing to land first.
- Right-click
- The Notion plugin's bundled
Save to Notionaction logs a single file to the configured database immediately — the instant, single-file version of the same idea, without waiting on a folder-wide digest. - Chat
- No note has to land first to ask for one right now:
"Summarize this folder's notes and save it to our Notion knowledge base." - Other automation triggers
- A standing schedule works just as well as a file arrival for this — the same trigger scheduled-report shows, pointed at Notion instead of a chat channel.
- Other integrations
- The same digest can go to a chat channel instead of — or alongside — Notion; that's exactly the leg scheduled-report verifies over Telegram.
