Stop feeding AI old files: automate your source intake

AI gets stale as soon as its sources do. A proposal changes, a new operating procedure lands in Drive, and next month's report arrives. Yet many teams keep asking the same notebook questions as if nothing has changed.

Google has made the boring part automatable. A new Workspace Studio step can add documents, links, and text to Gemini Notebook whenever a flow runs. For a small team, the benefit is simple: the person making a decision can work from a source bank that keeps receiving approved material without relying on someone to remember every upload.

This is not an autopilot for every decision. It improves the intake of knowledge the AI is allowed to use. That distinction is what makes the update useful.

What Google launched on August 7

Google Workspace Studio is Google's tool for building flows across products including Gmail, Drive, Chat, and Gemini. A flow starts with a trigger, such as a file being added to a folder, and continues with one or more steps.

The new step is called Add a source to Gemini Notebook. It can send four kinds of content to a selected notebook:

• Copied text.
• A link to a Drive file.
• A web address.
• A YouTube link.

Google began rolling out the feature on August 6 to Business Starter, Standard, and Plus, Enterprise Standard and Plus, and several Education editions. The rollout may take up to 15 business days. Administrators can control whether Gemini steps are available in Workspace Studio.

Source: Automatically add sources to your Gemini Notebooks in Workspace Studio.

Gemini Notebook, previously NotebookLM, is a collection of sources for one bounded project. It answers from the material in that notebook and can create summaries, reports, audio overviews, flashcards, and other outputs. One notebook does not automatically search across your other notebooks.

Source: Create a notebook in Gemini Notebook.

Why automated source intake beats another clever prompt

A good prompt cannot rescue old facts. If the price list in the notebook is from April while the approved August version sits forgotten in Drive, you get a polished answer based on the wrong material.

This happens easily in organizations where the same knowledge changes a little at a time:

• A restaurant updates its menu, allergens, or supplier terms.
• A consultant receives new client requirements and project decisions.
• A school adds course materials and local instructions.
• An online shop changes product information, return policies, and campaign plans.

When intake is manual, the source bank depends on one person's memory. When intake sits inside the workflow, each approved file has a defined path in. A person still decides what is approved. The machine handles transport.

The useful starting point is not add everything. Choose one type of decision and one owner, then build the source bank around that work.

Build a 45-minute flow for a living source bank

The example below suits a team that receives reports, pricing inputs, meeting decisions, or other material each week and needs to search it later. The flow adds a Drive file to Gemini Notebook when someone places the file in a designated folder.

Minutes 0–5: choose the question the source bank must answer

Write the sentence in your own words: This notebook will help us answer [question] using evidence from [sources].

A useful example is: This notebook will help us prepare the weekly customer follow-up using approved meeting notes, proposals, and delivery reports.

If the sentence covers the whole business, it is too broad. Narrow it to a recurring decision rather than a general wish to collect knowledge.

Minutes 5–10: create a private notebook

Create a new Gemini Notebook for the task. Give it a name that describes the decision, such as Customer follow-up – approved sources.

The new Workspace Studio step only lists notebooks that are private to you. A shared notebook will not appear. The flow therefore needs a clear owner. Share a reviewed weekly output through Docs or Chat instead of trying to turn the source notebook into a team archive on day one.

Google also describes each Drive import as a copied or automatically synced version of the source file. You need at least view access. If you lose access or the file is deleted, the source becomes unavailable to the notebook.

Source: Add or discover new sources for your notebook.

Minutes 10–20: build a clear intake folder in Drive

Create a private folder with a name that says its contents are approved for AI use, such as To source bank – customer follow-up.

Set a simple rule for what may enter:

• The document has an owner.
• The filename includes a date or version.
• The content belongs to the chosen question.
• A superseded file is marked as old or moved out of the folder.

Workspace Studio has restrictions around shared drives and shared folders. Google says flows may fail when they use those files and that files need to be private to the flow owner. Check the design in your own Workspace environment before making it a team routine.

Source: Guide to Starters & Steps in Workspace Studio.

Minutes 20–30: build the flow in Workspace Studio

Open Google Workspace Studio and create a new flow.

1. Choose the When an item is added to a folder trigger.
2. Select your private intake folder in Drive.
3. Add the Add a source to Gemini Notebook step.
4. Select the notebook you just created.
5. Choose Drive link as the input type.
6. Insert the file link from the trigger as a variable.
7. Save the flow with a clear name, such as Approved report to customer source bank.

If your intake begins in Gmail, you can instead use an email trigger and pass copied text or a link. Start with the Drive folder. It creates a visible checkpoint where a person approves the material before it enters the notebook.

Minutes 30–38: test with a dated file

Add a document containing one unique, harmless test fact, such as a project name and decision date. Open the flow's run history and confirm that the step succeeded.

The source is added quickly, but Google says indexing can take a few minutes. Wait until it appears in the notebook, then ask a question that only the test file can answer. Confirm that the answer points to the right source.

Move the test file out of the intake folder afterward if it should not remain in the live source bank.

Minutes 38–45: define the weekly owner routine

The automation needs a short editorial routine. Put 10 minutes in the calendar each week and have the owner:

• Check which sources were added.
• Mark old versions and remove material that should no longer govern answers.
• Note gaps in the evidence.
• Share one reviewed output with the team.

That keeps the source bank alive without turning it into a dumping ground.

Copy-ready prompt for the weekly source check

Paste this prompt into Gemini Notebook, replace the dates, and adjust the headings to fit your work:

Use only the sources in this notebook.

Run a source check for [DATE–DATE].

1. List new sources with date, title, and the work question each one affects.
2. Identify facts that conflict with an older source. Cite both sources and suggest which one should govern, but do not make the decision for us.
3. Flag sources with no date, owner, or clear version.
4. Summarize what has actually changed in no more than seven bullets.
5. Propose the next work action for each change and state who must approve it.
6. End with "Missing from the evidence" and list questions the sources cannot answer.

Do not invent missing facts. Keep source references next to every factual claim.

Run the prompt in the notebook itself when you need source references. Google's guide says the Workspace Studio Ask Gemini Notebook step can return text but does not support citations. That step may be fine for an internal draft, but not for a decision where the reader must trace a claim back to its source.

Four workflows that fit the new feature

Customer follow-up: Put approved meeting notes, proposals, and delivery reports in an intake folder. Use the notebook to find changed commitments, open questions, and the next contact point before the weekly sales meeting.

Market monitoring: Send new reports and web addresses to a source bank for each market or topic. The weekly check separates genuinely new facts from material that repeats what you already know.

Internal procedures: Add approved instructions and versioned process documents. Ask Gemini to compare the latest procedure with older material and flag conflicts before anyone updates the handbook.

Teaching preparation: Add approved course materials and the teacher's local instructions to a private notebook. Then create a source-based lesson plan or question bank for the teacher to review before using it with students.

The common pattern is controlled intake. Do not point AI at the whole of Drive. Give the source bank one job, one owner, and one inbox.

What still needs a person

The new step adds sources. It does not decide whether a new file replaces an old one, whether two claims conflict, or whether the material is ready to share. File naming, a version rule, and the weekly check belong in the same solution.

A real integration can stay practical: restrict the flow to the right folder, let a named owner approve intake, use separate permissions for published outputs, and review runs in Workspace Studio logs. Larger Workspace environments can also use admin controls and activity logs to see which flows and Gemini steps are running.

If the routine works manually for two weeks, make the next version shareable and measurable. Track how many files entered, how many old versions were caught, and which decisions became faster. This is a natural Tool Forge job: connect a working process to the right permissions, review point, and logging.

Start with a question that genuinely returns every week. The next time an approved report lands in Drive, the source bank should already know where it belongs.