Keeping a Knowledgebase Current
How Google Drive and Notion syncs behave, which files sync, the limits, and how to keep a Knowledgebase current from your own systems.
Keeping a Knowledgebase Current
Agents and Flows read a Knowledgebase when they run, so anything you add, change or remove there is what they use on their next run. Nothing needs to be republished. There are three ways to keep one current:
- Synced sources for Google Drive and Notion. See Synced Sources to set one up.
- Website crawls for a site or a section of one.
- The API or MCP, for content that lives in your own systems, such as docs in a repository.
Google Drive syncs
- One folder, not its subfolders. A sync covers the files directly inside the folder you choose. Files in its subfolders are not synced. To sync a subfolder, pick it as the folder to sync, or add a second sync for it.
- Picked files stay picked. When you sync selected files instead of a folder, only those files stay in sync. New files added to their folder are not picked up.
- One flat folder in the Knowledgebase. Each sync becomes one folder named after the Drive folder; the Drive folder structure is not copied. A file you move elsewhere in the Knowledgebase stays where you put it.
- Removals follow Drive. A file you delete or trash in Drive is removed from the Knowledgebase at the next sync.
- Stopping a sync leaves its folder and the files it imported in place.
File types
| Type | Synced as |
|---|---|
| Plain text (.txt), CSV (.csv), Markdown (.md) | As is |
| Word (.docx) | As is |
| Google Docs | PDF, named <name>.pdf |
Google Sheets, Slides, Forms and Drawings, images, and every other type are skipped.
Notion syncs
A Notion sync covers one database. Each row becomes one document: its title, a short header with the row's properties, then the page's content. Page trees outside a database aren't synced. The database has to be shared with the connected Notion integration, or the sync finds no rows.
Schedules
Every sync has a schedule: Hourly, Daily, Weekly or Manual (only when you run it). Sync now runs one at any time. On each run, new and changed items come in, and items removed at the source are removed here.
The Syncs board
Knowledgebase → Syncs shows every Drive, Notion and website sync in the workspace on one board, so you can watch them all without opening each Knowledgebase. Each sync appears as a card in one of four columns:
- Scheduled - its next check. The time is close, not exact: a busy minute can push it to the next one.
- Running - a sync in progress.
- Needs you - the last run failed: out of credits, a lost Drive or Notion connection, or a site that could not be read. The card says why.
- Done - the last run of every other sync. Runs from before today fold into a single Earlier card so the column stays short.
Every card names the Knowledgebase it fills and offers Sync now. Changing a sync's schedule or stopping it is done on its row in that Knowledgebase. The board is open to every member.
When a sync fails
A sync that can't run (a Drive or Notion connection that lost access, a site that can't be read) keeps everything it already synced, and your Agents keep using it. You hear about it in three places:
- On its row in the Knowledgebase, with the reason, and in the Needs you column of the Syncs board.
- In Alerts and messages, in your account menu, until a run succeeds again.
- By email, once, when a sync that was working starts failing. It goes to the person who set the sync up, or to the workspace's owners and admins if that person has left. A sync that stays broken doesn't email again, and the same sync never emails more than once a day.
Running out of credits doesn't send a sync email: the credit usage email already told owners and admins. The sync picks up again at its next scheduled run, or when you click Sync now, once credits are back.
Limits
- File size: 25 MB per synced file.
- Per run: the whole folder or database is listed, up to 5,000 items, and up to 50 new or changed items are imported per run. The rest follow in the next runs, about once an hour, until the sync has caught up.
- Files per Knowledgebase: synced files count toward your plan's limit like any other File. Items past the limit are skipped, and the sync says why on its row.
| Plan | Files per Knowledgebase |
|---|---|
| Free | 3 |
| Creator | 10 |
| Pro | Unlimited |
| Agency | Unlimited |
| AppSumo Tier 1, 2, 3 | 3, 10, 15 |
| AppSumo Tier 4 | Unlimited |
From your own systems
To keep a Knowledgebase in step with content you manage elsewhere, such as Markdown docs in a repository, update it from your CI with the REST API or MCP.
- Pages (Docs): create a page once, then edit it in place with anchored edits (
PATCH /v1/knowledgebases/{id}/pages/{pageId}, orsave_pagewith anidover MCP). The page keeps its id, so links to it keep working. - Documents (Files): add with
POST /v1/knowledgebases/{id}/sources(orupload_source), and remove withDELETE /v1/knowledgebases/{id}/sources/{sourceId}(ordelete_source).
Removing documents
Removing a document takes it out of that Knowledgebase at once: Agents stop finding it on their next search. Whether it is also deleted for good depends on where else it is used and who asks:
- Deleted for good (its search index entry, stored file and record) when no other Knowledgebase uses it and the request comes from an org key, an owner or an admin.
- Only taken out of this Knowledgebase otherwise: when another Knowledgebase still uses it, when a member asks, or when your organization reviews changes before they apply. It stays in your organization's Files library, where it can be added back.
The answer says which happened:
| Field | Meaning |
|---|---|
deleted | true when the document is gone for good, false when it was only taken out of this Knowledgebase |
stillUsedBy | How many other Knowledgebases still use it |
synced | true when it comes from a Drive or Notion sync or a website crawl. The next sync adds it back unless it is removed at the source too |
Removing needs the knowledge:write scope and a member role or above. If the search index can't be reached, nothing changes and the answer is search_unavailable: retry it.