Skip to content

Add Narrative Intelligence to Google Docs

A shared Story Bible tracked inside Google Docs

Start free

How it works

1

Connect your Google Doc

Authorize PlotLens to read your Google Doc and it begins indexing your manuscript.

2

PlotLens monitors your document for changes

As you and your co-writers edit, PlotLens detects new content and runs validation.

3

Validation results appear in the sidebar

Findings show up in the PlotLens sidebar. You can turn on background-colour highlights on the text they reference.

What Marcus needed

Your co-writers see results without learning a new tool

Validation results appear in the PlotLens sidebar. Optional background-colour highlights mark the referenced text in the Doc. The add-on does not add Docs comments.

How setup will work once Google Docs opens

  1. Authorize Google Docs access

    Sign in with your Google account and select the documents you want PlotLens to monitor.

  2. PlotLens indexes your manuscript

    Characters, locations, and events are extracted from your existing document content.

  3. Review findings in the sidebar

    Findings are listed in the sidebar. With background colour on, the referenced text is highlighted, and collaborators with access to the Doc can see the highlight.

Limitations

The Google Docs add-on is built and in review for the Google Workspace Marketplace. There is no public listing yet, which means there is nothing to install today — the steps above describe how installation will work once the listing publishes, not something you can do now. In the meantime, download your Doc as .docx and upload it to PlotLens directly; the same Story Bible, the same Manuscript Check, one export step in between.

Two limits are worth knowing before the listing lands. The add-on does not create Google Docs comments: findings appear in the sidebar, and the only in-document mark is an optional background-colour highlight, off by default. Authorizations are also per Google account: the account you authorize has to be the one that actually holds access to the document, which is the most common way a working setup silently stops working.

Everything downstream of getting the text into PlotLens is unaffected by the wait. Extraction returns characters, locations, events, items, organizations and concepts with source attestations; auto-derived facts arrive pending with the snippet they came from, so you accept or reject each one; batch validation sweeps whole documents and returns findings with a severity, a conflict type, a citation and a suggested fix. Spot Check will take a pasted excerpt of up to roughly two thousand words with no project documents required, free on every tier and outside the monthly quota — which makes it the cheapest way to check one revised passage while an integration is still closed.

As with every PlotLens integration, sessions live 24 hours with automatic heartbeats, enforce a per-plan maximum content length, and apply a per-session requests-per-minute limit that the client backs off from on its own.

Google Docs is where collaborative writing happens. The PlotLens add-on is built and in review for the Google Workspace Marketplace — there’s no public listing to install from yet. Once it publishes it will monitor your shared manuscript, validate continuity as your team writes, and list findings in the sidebar, with optional background-colour highlights in the Doc. It does not add Google Docs comments. Until then, download your Doc as .docx and upload it to PlotLens directly.

The add-on reads the paragraphs of the document body. How it handles text in suggesting mode (unaccepted suggestions) has not been verified against a real Google Docs host. If you download as .docx and upload, check that the file does what you expect: in an uploaded .docx, pending tracked changes and hidden text are left out, and headers, footers, and footnotes are not read.

Ready to add PlotLens to Google Docs?

Start free — no credit card required.