Auto-fetch
While triggers are the push path from integrations, auto-fetch is the pull path. It runs continuously in the background, polling connected integrations on a sync interval and writing new content into the Memory Tree.
How it works
Integration → Backend polling → Content diff → Memory Tree
↓
Learning layer
The backend fetches new content, diffs it against the last sync, and writes only the delta into your Memory Tree.
Configuration
Per integration, you can set:
| Setting | What it does |
|---|---|
| Sync interval | How often to poll (e.g. every 5 min, every hour) |
| Scope | Which folders, labels, or projects to sync |
| Direction | Import only, or bidirectional |
What gets stored
- New emails, messages, documents
- Changes to tracked pages or files
- Calendar events within a rolling window
- Notion blocks modified since last sync
Daily budget
Auto-fetch is rate-limited by your API quota. You can cap it with a daily budget to avoid burning through a free tier.
See also
- Triggers - The event-driven counterpart
- Memory Tree - Where auto-fetch writes to