NotebookLM integrations and automation

This connection is for NotebookLM Enterprise, the Google Cloud edition of NotebookLM, not the free consumer app. The consumer product at notebooklm.google has no public API. The Enterprise API lives in a Google Cloud project with NotebookLM Enterprise set up, uses Google Cloud authentication and IAM, and addresses notebooks by project number and location. Google marks parts of it as pre-GA, so endpoints and behaviour can change and support is limited; plan for that before depending on it.

What the documented API covers is notebook housekeeping rather than chat. You can create a notebook, get it, list recently viewed notebooks, delete notebooks, and share a notebook with users at a chosen role. Sources can be added in batches from Google Docs and Slides in Drive, from web or YouTube URLs, from raw text, or by uploading a file, and each source can be retrieved or removed. An audio overview can be generated for a notebook, checked for completion, and deleted.

The useful automation, then, is keeping a notebook’s sources current. A research team may want this week’s set of reports added to the right notebook every Monday; a course team may want a notebook per module, shared with the right people, built from a folder list. The workflow does the bookkeeping, and people do the asking inside NotebookLM. Treat source processing as asynchronous: an added source is not immediately ready to ground answers, so check its status before telling anyone the notebook is up to date.

Sharing goes through Google identities in your organisation, and per-notebook source limits still apply. Record the notebook ID and the source IDs you added, so a rerun adds only what is new instead of stacking duplicates.