Schedule Gemini Notebook (formerly NotebookLM) Daily Briefs

Gemini Notebook (formerly NotebookLM) is great at answering questions. It just never asks one. Nothing happens until you open a notebook, type, and wait. So when we analyzed what the 776 people on the Kortex MCP waitlist asked for, timing came out on top. In fact, 128 of them wanted their notebooks to work on a schedule, without being asked (Kortex MCP waitlist survey, 776 respondents, Sep-Oct 2026).

That job already works. This guide sets up a Gemini Notebook daily briefing (a NotebookLM daily briefing, in the old name) with one message to your AI assistant. Kortex then asks a notebook your question, saves the answer and turns it into an Audio Overview. You’ll get the prompts, three schedules to copy, and the one caveat: Chrome has to be open.

Key Takeaways

• 128 of 776 Kortex MCP waitlist respondents asked for scheduled or triggered work, the most-requested job on the list (Kortex MCP waitlist survey, 2026).
• One sentence to your assistant creates the schedule with create_automation: hourly, daily or weekly.
• Schedules fire from Chrome, so a closed laptop runs nothing.

What is a Gemini Notebook daily briefing?

A Gemini Notebook daily briefing is a standing question your notebook answers on a clock. Kortex checks your schedules about every 15 minutes. When one is due, it runs a three-part loop, and you sit down to a brief you never had to request (Kortex MCP docs, 2026):

1. Ask. At the hour you picked, Kortex asks your notebook a question you wrote once, such as “What changed this week?” In other words, the answer comes from your sources, the same as if you’d typed it.
2. Save. The answer goes back into the notebook as a new source, titled with the date. Prefer a clean source list? Save it as a Kortex note instead.
3. Listen. Gemini Notebook then generates an Audio Overview, so the brief is something you can play while the kettle boils.

The ask step is what makes this a briefing instead of a timer. Every other scheduled action does the same fixed thing each run, for example adding a tag. In contrast, asking is the one action whose output depends on what the notebook holds that morning. Add three articles on Tuesday, and Wednesday’s answer knows about them.

How is this different from Kortex automation rules?

Same family, different front door. Our guide to Kortex automation workflows covers rules you build in the automation panel, mostly fired by events such as a tag. This guide, on the other hand, covers schedules you set up by talking to your AI assistant.

	Automation rules guide	This guide
How you set it up	Click it together in the Kortex automation panel.	Describe it to your AI assistant in one message.
What usually fires it	Events: a tag added, a notebook filed in a collection.	The clock: hourly, daily or weekly.
Signature move	Fixed actions: make a Briefing Doc, add a tag, send audio to a podcast.	Ask a question now, save the answer, make audio.
What you need	Kortex Pro.	Kortex MCP (Pro, private beta).

You can use both. A rule can watch for a tag, while a schedule asks what changed.

Why can’t Gemini Notebook schedule Audio Overviews on its own?

Because Gemini Notebook only works when you ask. Its help page lists four Audio Overview formats and warns that generation “may take a couple of minutes,” but it says nothing about recurring runs (Gemini Notebook Help, 2026). The closest native feature is Generate later, which defers a generation when you’ve run out of allowance (Gemini Notebook Help, 2026). That’s a one-off, not a routine. Google’s Gemini app does have scheduled actions, capped at 10 active at a time, for jobs such as a daily news digest (Gemini Apps Help, 2026). However, that help page doesn’t mention notebooks or Audio Overviews, and there’s no public consumer API to build your own. A digest of the news isn’t a digest of your sources.

So today, a briefing is a chore you repeat by hand every morning, which is why scheduling tops the wish list. Specifically, in the Kortex MCP waitlist survey, 128 of 776 respondents (16%) wanted their assistant to run work on a schedule or trigger, more than any other job. Similarly, 244 of the 776 (31%) described a manual copy-paste workaround they rely on today (Kortex MCP waitlist survey, 776 respondents, Sep-Oct 2026). One respondent described the job exactly: “Each morning, my assistant should prepare a short source-backed briefing from selected notebooks.” That’s what this guide sets up.

Kortex fills that gap from your side of the browser. Kortex is a Chrome extension for Gemini Notebook, and Kortex MCP is its Model Context Protocol server, which lets AI assistants work inside your notebooks. We built the scheduler into the extension, which already talks to Gemini Notebook with your own Google sign-in. In addition, Kortex never stores your Google password or cookies (Kortex MCP docs, 2026).

Our Gemini Notebook MCP guide explains the connection. Meanwhile, you can start with the free extension today and get in line for the part that runs on a clock.

What do you need before you set up a schedule?

You need four things: Kortex in Chrome, an invite to Kortex MCP, a connection that’s allowed to write, and a notebook worth asking. Kortex MCP is a Kortex Pro feature, at $9.99 a month or $4.92 a month billed yearly, and it’s in private beta: only invited members can connect. Invites go out from the waitlist above. Once you’re in, the checklist is short:

• Kortex in Chrome, signed in to the Google account that owns your notebooks.
• Kortex MCP connected to your assistant. In Claude Code it’s one command, shown below. For Claude Desktop or the web app, see using Gemini Notebook in Claude.
• Write access. Creating a schedule is a write. New API keys default to Read-only, so pick Standard, or allow writes on the OAuth consent page.
• A notebook worth asking. Importantly, a briefing is only as good as the sources behind it.

claude mcp add --transport http kortex https://mcp.kortex-notebooklm.com/mcp

How do you schedule a daily briefing in Gemini Notebook?

In three steps and about five minutes: describe the schedule to your assistant in one message, run it once as a test with run_automation, then check the run log. Your assistant makes every tool call. As a result, you never write the rule by hand.

Step 1: Tell your assistant once

When we ran tools/list against the production server on October 1, 2026, it returned 150 tools. Notably, eight of them manage automations (Kortex MCP tools, 2026). Here’s the request from the Kortex homepage, word for word:

Every Monday at 8, ask my Competitors notebook what changed this week. Save the answer and make it an Audio Overview I can listen to.

Behind that sentence, your assistant:

1. Calls list_notebooks to find the real id of “Competitors,” because create_automation rejects a rule that names something that doesn’t exist.
2. Calls create_automation with a schedule trigger and two actions: ask and save, then generate audio.
3. Tells you what it created, since the rule keeps acting after the chat ends.

Here’s what gets saved:

{
  "name": "Competitors brief",
  "trigger": { "type": "schedule", "every": "weekly", "weekday": 1, "hour": 8, "notebookIds": ["<Competitors notebook id>"] },
  "actions": [
    { "type": "ask_and_save", "question": "What changed this week?", "saveAs": "source", "title": "Competitor brief {date}" },
    { "type": "generate_audio", "prompt": "Focus on the newest Competitor brief source." }
  ]
}

weekday: 1 is Monday, hour: 8 is 8 a.m. on your computer’s clock, and {date} stamps each brief with the date. Always name the notebook. Left blank, a schedule applies to every notebook in the account. In other words, that’s a lot of Audio Overviews.

Why steer the audio? It’s made from the whole notebook, not just the new answer. As a result, telling the hosts to focus on the newest brief keeps the episode about this week.

Step 2: Test it now with run_automation

Don’t wait until Monday to find out it works. run_automation runs a rule’s actions immediately across the notebooks it targets. An identical run inside the previous minute is suppressed. Consequently, asking twice won’t make two briefs.

Run my Competitors brief now as a test. Tell me when the Audio Overview has finished, and show me the answer it saved.

Your assistant calls run_automation, then polls list_artifacts until the Audio Overview shows as completed.

Step 3: Check the log, pause or change it

Every run is recorded. list_automation_runs shows which rule ran, on which notebook, whether each action succeeded and why one failed. Actions run in order and stop at the first failure. For instance, if the question step fails, no audio gets made.

Show me my Kortex automations and the last five runs of the Competitors brief. If a step failed, tell me why in one line.

Your assistant answers with list_automations and list_automation_runs. Everything else is plain language too:

• Pause it: “Pause my Competitors brief for now.” That calls set_automation_enabled and keeps the rule for later.
• Change it: “Move my Competitors brief to 7 a.m.” That calls update_automation, which leaves anything you didn’t mention alone.
• Delete it: delete_automation is permanent, so your assistant should confirm first. Sources and audio it already made stay put.

Three schedules worth copying

These cover the common jobs: a competitor brief, a research digest and a study review. Each takes one message, so swap in your own notebook names.

The Monday competitor brief (weekly)

Every Monday at 7, ask my Competitors notebook: "What changed this week in pricing, product and hiring? Name the company and cite the source for each change. If nothing changed, say so in one line." Save the answer as a source titled "Competitor brief {date}", then make an Audio Overview that focuses on that brief.

Why 7 and not 8? The run lands within 15 minutes of the hour, and the audio takes a few minutes more. Set it an hour early and it’s waiting when you sit down. Likewise, the “say so in one line” clause matters, because quiet weeks get a short note instead of five paragraphs of filler.

Here’s your Monday. At 8 you open the notebook to a source called “Competitor brief” with today’s date, every change cited, and an Audio Overview waiting in the Studio panel. Why insist on the citations? Even tools that answer from your sources slip. In a 2025 study on a 300-document corpus, 13% of NotebookLM’s outputs contained a hallucination, against about 40% for ChatGPT and Gemini (Hagar, Agustianto & Diakopoulos, 2025). Notably, the usual error was an overconfident reading of a source, not an invented fact. A cited brief lets you check the one line you’re about to act on.

The daily research digest (up to three notebooks)

A schedule can ask up to three notebooks at once and merge the answers, one heading per notebook. Point it at a separate briefing notebook, so digests don’t pile up inside your research.

Create a notebook called Morning Briefing. Then, every day at 7, ask my Papers, Policy and Market notebooks: "What are the three findings I most need to know today, and which source should I read first? Cite each one." Save the combined answer as a source in Morning Briefing titled "Digest {date}", then make an Audio Overview of Morning Briefing that covers only the newest digest.

As a result, the digest lands in Morning Briefing and your research notebooks stay untouched.

The weekly study review (Sunday)

Every Sunday at 6 p.m., ask my Biology 201 notebook: "Summarize the newest lecture notes and list the three ideas I'm most likely to be tested on." Save the answer as a source, then make an Audio Overview of that summary and a quiz from the notebook.

Alternatively, swap the quiz for flashcards or a mind map if that’s how you revise.

What about hourly?

Hourly exists, but save it for cheap text work, in particular asking and saving into a Kortex note or running a saved workflow. Our guide to multi-step AI workflows shows how to build one.

Don’t make an Audio Overview every hour. Each run draws on your Gemini Notebook allowance, which now refreshes every five hours until you hit a weekly cap (Gemini Notebook Help, 2026). Twenty-four audio runs a day would, therefore, burn through it fast. Our usage limits guide explains what costs the most.

What has to be running for a schedule to fire?

Chrome does. Schedules run inside the Kortex extension, which checks for due ones about every 15 minutes on your computer’s local time (Kortex MCP docs, 2026). Chrome can be minimised, and no notebook tab needs to be open, but a closed laptop runs nothing. We analyzed the extension’s scheduler code to pin down the rest:

• Missed hours don’t catch up. A daily or weekly schedule only fires during its hour. If Chrome is closed from 7 to 8, the 7 a.m. brief waits for tomorrow. Hourly schedules, however, pick up at the first check after Chrome opens.
• Pick an hour you’re usually online. If your laptop stays shut until 9, set the brief for 9 and listen at 9:30.
• Your clock decides. Times follow your computer’s local time, so travel changes when the brief arrives.
• Stay signed in. Kortex works through your existing Google session.

What can’t a scheduled briefing do?

A schedule only reaches your notebooks. It can’t read Gmail, Notion or Google Drive on its own; only your AI client can, during a conversation (Kortex MCP docs, 2026). That’s the bridge model: whatever your AI client can reach, Kortex can put into a notebook while you talk to it.

Most people already have the other half. In the waitlist survey, 81% said their assistant can reach Google Drive, and 81% said Gmail (Kortex MCP waitlist survey, 776 respondents, Sep-Oct 2026). Therefore, split the job: bring outside material in during a chat, as in sending email into Gemini Notebook, and let the schedule brief you on it.

A few more limits worth knowing:

• It reads, it doesn’t fetch. The ask step works from sources already in the notebook. A saved workflow, however, can add sources, since it’s any sequence of Kortex tool calls. The docs’ example: “Every day, re-read the Google Docs linked in my Team notebook.”
• Digests pile up. Saving as a source adds one per run, so a daily brief adds about 30 a month. Free Gemini Notebook accounts cap a notebook at 50 sources (Gemini Notebook Help, 2026). Use a separate briefing notebook, save to a Kortex note, or prune old digests.
• Scheduled workflows skip your key’s profile. A run you start by hand is checked against your key’s profile first. A scheduled run isn’t made by a key; consequently, it runs whatever was saved. Keep irreversible jobs manual (Kortex MCP docs, 2026).

Want audio, slides or a quiz right now instead of on a timer? That’s a different job: making Studio outputs from chat.

Is a scheduled briefing worth setting up?

Yes, if two things are true: a notebook of yours changes during the week, and Chrome is open at a predictable hour. Then a briefing that waits for you beats a notebook that waits for you. The setup is three moves: tell your assistant once, test it with run_automation, and pick an hour when your laptop is awake. In particular, point daily digests at a separate briefing notebook, and keep Audio Overviews off the hourly schedule so your Gemini Notebook allowance lasts the week. On the other hand, if your notebooks rarely change, or your laptop stays shut most mornings, a schedule will mostly report “nothing changed” or never fire. Ask by hand instead. For everyone else, it’s one sentence of setup.

Frequently asked questions

Can NotebookLM schedule an Audio Overview on its own?

No. As of October 2026, Gemini Notebook (formerly NotebookLM) makes Audio Overviews when you ask, and its closest feature, Generate later, is a one-off. Google’s Gemini app allows up to 10 scheduled actions; however, its help page doesn’t mention notebooks. Kortex MCP adds hourly, daily or weekly schedules that run from your browser.

Is this the same as Gemini’s Daily Brief?

No. Google’s Daily Brief, in the Gemini app, draws on Gmail, Google Calendar and your Gemini chats, and it’s US-only and English-only. Its page doesn’t mention notebooks. The briefing in this guide, by comparison, asks one of your notebooks a standing question.

Does my computer need to be on for a scheduled briefing?

Yes. Schedules run inside the Kortex extension, so Chrome must be open with the extension signed in, though it can sit minimised. A daily or weekly run whose hour passes while Chrome is closed waits for its next slot instead of running late.

How often can a Kortex schedule run?

Every hour, every day at an hour you choose, or once a week on a weekday you choose, all on your computer’s local time. There is no every-15-minutes option. Because Kortex checks for due schedules about every 15 minutes, a run lands within that window of its hour.

Can a schedule read my Gmail, Notion or Google Drive?

No. A schedule only reaches your notebooks. Your AI client can fetch from Gmail, Drive or Notion with its own connectors during a conversation, and Kortex MCP can carry that into a notebook. The next briefing then works with whatever landed there.

How do I pause or delete a scheduled briefing?

Ask your assistant. “Pause my Competitors brief” calls set_automation_enabled and keeps the rule for later. “Move it to 7 a.m.” calls update_automation. Deleting is permanent, so your assistant should confirm before it calls delete_automation.

What does a scheduled Gemini Notebook briefing cost?

Kortex has a free plan, but Kortex MCP is a Pro feature at $9.99 a month, or $4.92 a month billed yearly. It’s in private beta, so you also need an invite from the waitlist. In addition, Google’s own Gemini Notebook usage limits still apply to every scheduled question and Audio Overview.

---

Editorial note: fact-checked against the official help pages and docs linked above on October 1, 2026. Spotted something out of date? Contact us and we will fix it, or read more about Kortex.