Live Sources
Keep Contexts fresh with scheduled website crawls, RSS feeds, YouTube videos, and connected cloud folders — without re-uploading files every week.
Quick mental model: Static uploads are snapshots. Live Sources keep your Context up to date automatically.
What Live Sources Are
A Live Source is a scheduled connection between a Context and changing information on the web or in your cloud storage. When the source refreshes, Springbase re-ingests the content so Chat, Recipes, and Plans can ground answers in the latest material.
Live Sources live on the Live Data tab inside a Context — not on the Documents tab.
When To Use Live Sources
| Situation | Use Live Data? |
|---|---|
| Help center or docs site that changes weekly | Yes — sitemap or RSS |
| Competitor pages you monitor | Yes — web page or sitemap |
| Policy PDFs that rarely change | No — static upload is enough |
| Google Drive folder of sales decks | Yes — connected folder sync |
| One-off research PDF | No — upload once |
Combine static uploads (stable reference material) with live sources (material that changes) in the same Context when they support the same job.
Prerequisites
Live Data requires a Pro or Max plan. Free users see an upgrade prompt on the Live Data tab with a link to Billing.
You also need a Context first. Create one at Contexts → Create New Context before adding sources.
Add Your First Live Source
- Open Contexts and select your Context.
- Click the Live Data tab (next to Documents).
- Choose how to add a source:
- Add first source or Add source
- Browse source types for website options
- Google Drive or OneDrive for cloud folders
- Configure the source:
- Paste a URL, pick a folder, or connect your account
- Set How often should we check? — every hour, 6 hours, daily, or weekly
- Choose an ingestion mode (see below)
- Click Start auto-updates (or equivalent confirm action).
- Wait for the first run to complete, then test in Chat by attaching the Context.
Source Types Available Today
Website links
| Type | Best for | Example |
|---|---|---|
| Web page | A single URL that updates | Pricing page, changelog |
| Sitemap | Entire doc sites | yoursite.com/sitemap.xml |
| RSS feed | Blogs and release notes | Product blog RSS |
| YouTube video | One video's transcript | Launch keynote |
Note: YouTube syncs once when you add it — it does not run on a recurring schedule like web pages.
Connected apps
| App | What syncs |
|---|---|
| Google Drive | A file or folder |
| OneDrive | A file or folder |
You authorize through the same connected-apps flow used elsewhere in Springbase. The same connection can power Agent mode and Live Data.
Ingestion Modes
When you create a source, choose how Springbase stores updates:
| Mode | What you get |
|---|---|
| Save each item (recommended) | Full text of each page or file, best for precise Q&A |
| Daily AI summary | A digest document per day |
| Weekly AI summary | A digest document per week |
For precise support or product answers, prefer Save each item. Use digest modes when you mainly want trend summaries.
Manage Sources
Each source card shows status, last run, and recent activity. From the card you can:
- Run now — trigger an immediate refresh (subject to a short cooldown between manual runs)
- Pause / Resume — stop or restart scheduled checks
- Remove — delete the source definition
If a source fails repeatedly, Springbase may auto-pause it after several consecutive errors. Fix the URL or permissions, then resume and run manually.
Use Live Data in Chat
Live Sources only help when the Context is attached:
- Open Chat.
- Attach the Context from the context picker, or type
@your-context-namein the message. - Ask questions that require fresh material: "What changed on our pricing page this week?"
Answers can include citations back to ingested documents.
Limits and Quotas
| Limit | Typical value |
|---|---|
| Live Data feature | Pro or Max plans |
| Live sources per Context | Up to 10 on paid plans |
| Sitemap pages crawled | Up to 500 on paid plans |
| Schedule intervals | 1 hour, 6 hours, 24 hours, 7 days |
| Manual run cooldown | About 5 minutes per source |
Exact quotas may vary by plan tier. Check Billing if you hit a limit message.
Example Workflows
Competitor monitoring
- Create Context Competitor Intel.
- Add sitemap live sources for 2–3 competitor doc sites (weekly schedule).
- Create a Recipe: "Summarize what changed in @Competitor-Intel this week."
- Run the Recipe every Monday.
Always-fresh help center
- Context Support Knowledge Base with uploaded internal SOPs (static).
- Add help center sitemap live source (daily schedule).
- Support team attaches Context in Chat for ticket replies.
Drive folder sync
- Context Sales Enablement.
- Connect Google Drive folder where marketing drops new decks.
- Sales asks: "@Sales-Enablement What's our latest case study for healthcare?"
Troubleshooting
| Problem | What to try |
|---|---|
| Live Data tab shows upgrade prompt | Upgrade to Pro or Max |
| Source stuck in error | Check URL loads in a browser; click Run now |
| Source auto-paused | Fix root cause, Resume, then Run now |
| Chat answers feel stale | Confirm source last run succeeded; attach correct Context |
| Empty after add | Wait for first ingestion; check robots.txt isn't blocking crawlers |
Related Guides
- Contexts — build the knowledge base Live Sources feed
- Chat — attach Contexts and ask grounded questions
- Recipes — automate weekly digest prompts
- Content Engine — research workflows with live feeds
Related docs
Learn how to build living knowledge bases in Springbase with documents, notes, shared access, live sources, community Contexts, and grounded Chat.
Learn how to use Springbase Chat with Contexts, @mentions, shared knowledge, live sources, saved outputs, permissions, and practical prompt templates.
Turn reliable prompts into reusable templates with variables, optional Contexts, scheduling, sharing, and Agent mode for connected apps.
Research with Live Data, draft with Recipes, repurpose with Plan Mode, and publish from Canvas — a repeatable content workflow without legacy Pipelines.
Fix generic Chat answers, Context and Live Data issues, Recipe inconsistency, Agent failures, meeting processing, Plan Mode errors, and credit limits.