On this page
Free
What happens after you save: history, undo, offline queue, and editing saved content.
History
Every save Filed makes is recorded in your local history. Access it from two places:
Side panel → History tab: A compact list of recent saves. Each entry shows the page title, destination database, and how long ago it was saved. Click any entry to see full details or undo it.
Options page → History: The full history log with search and filter. Open via the hamburger menu (≡) → History or by clicking View full history at the bottom of the side panel's History tab.
History is stored locally in your browser. It is not synced to Filed's servers or to Notion.
Undo
Undo reverses a save by moving the Notion page to Trash.
Three ways to undo:
- Success toast: a toast appears at the bottom of the page for 30 seconds after every save. Click Undo in the toast to reverse immediately.
- History tab: find any past save and click Undo. No time limit. As long as the Notion page still exists, the undo will work.
- Workflows tab (workflow deletion only): a 5-second banner appears after deleting a workflow, with an Undo option that restores it from local storage.
What undo cannot do: If you've moved or modified the Notion page after saving, undo may fail or may delete a page that no longer matches the original save. Undo is a best-effort deletion, not a transactional rollback.
Notion's Trash retains deleted pages for 30 days. Undone saves are recoverable from Notion's Trash if needed.
Offline queue
If you save while offline or the Notion API is unreachable, Filed queues the save and retries automatically when your connection is restored.
Queued saves appear in the History tab with a "Queued" status indicator. No action is needed. The retry is automatic. If a retry fails, the entry moves to "Failed" status and you can trigger a manual retry from the History tab.
Queue limits: Screenshots and audio files are not queued. If a capture that includes a screenshot or audio file fails to upload at save time, those attachments are discarded. The text content (title, URL, note, transcript) can still be queued and retried, but the attachment will not be re-captured.
Editing a note after saving
You can add or edit the note on a saved page directly from the History tab. Click any history entry → edit the Note field → click Update. The change is written to the existing Notion page, not a new one.
Only the Note field is editable from history. To change the destination, workflow, or other fields, edit the Notion page directly.
Moving a save to a different database
From the History tab, click any entry → Move. Pick a new destination from your workflows. Filed moves the Notion page to the new database and updates its properties to match the destination schema.
Move is available with no time limit. It works on any save that still exists as a Notion page.
Saving to a specific heading
When saving to an existing Notion page (not a database), you can choose which heading to append the content under.
From the side panel: After picking a page destination (not a database), a Save under heading option appears. Select a heading from the list. Content is appended as a child block under that heading.
Useful for appending to a running note, a meeting page, or a project log.
Draft resume
Unfinished side panel captures survive tab reloads and browser restarts. While you're building a capture (blocks added, title set, workflow chosen), the draft is silently saved in the background. When you return to the same URL with the same workflow selected, the draft is restored automatically.
A Discard draft action is always available to clear the current draft.
Draft resume is local, not synced across devices. The draft is tied to the specific URL and workflow combination.