A chatbot is only as good as the last time it read your docs. If someone updates pricing in Notion and the chatbot doesn't know for two weeks, it'll confidently give a wrong answer — which is worse than not answering at all.
Turning it on
Each connected source (Notion, Google Drive, or a website crawl) has an auto-sync toggle and a sync interval. Turn it on and the source is re-checked automatically on that schedule — no manual re-sync required for routine updates.
Choosing an interval
There's no single right answer; it depends on how often the underlying content actually changes:
- Fast-moving docs (a changelog, active FAQ) — sync more frequently so edits show up in chatbot answers quickly.
- Stable reference material (a terms page, an onboarding guide that rarely changes) — a longer interval avoids unnecessary sync runs without meaningfully delaying updates.
Manual sync still works
Auto-sync doesn't replace the manual Sync now action — if you just published something and don't want to wait for the next scheduled run, trigger a sync directly from the source's page.
What happens on a sync
Only what changed gets reprocessed — a sync doesn't re-chunk and re-embed your entire source from scratch every time, so frequent syncing isn't wasteful. If a sync fails (a revoked permission, a deleted file), the source shows the error so you can fix it rather than silently falling behind.
Related reading
- Turning your docs into an AI chatbot — the full setup flow auto-sync plugs into.
- Connecting Notion as a chatbot source — one of the source types auto-sync keeps current.
- Seasonal traffic prep for your AI chatbot — why source freshness matters most right before a spike.
- 5 things everyone gets wrong about AI chatbots for support — including the myth that setup is a one-time task.
Set it once per source and stop thinking about it — configure auto-sync on your existing sources so the next doc update reaches your chatbot on its own.