Meet the new Scripe, live on October 7.Register

Integration

Drive files, read once, cited every time.

Pick the documents that matter and Scripe keeps them in the knowledge base, refreshed when they change.

Google DriveScripe

The files that matter, read once.

Decks, docs and PDFs your team already maintains in Drive become the knowledge behind every idea and draft.

Knowledge base

  • Positioning 2026Synced
  • Messaging frameworkSynced
  • Customer case study.pdfSynced

Pick the files, one by one.

Choose the positioning deck, the messaging doc, the case-study PDF. Scripe reads each into the knowledge base and refreshes it when the file changes.

Evidence
Outlier · Lea Brandt, 6.4× her average
Knowledge base · the 14 Sep call, Granola
Positioning · marketing leads, 11-50-person B2B

Every draft names the file.

An idea that draws on a Drive document carries its name; the hover card quotes the passage and opens the file.

Company documentsWorkspace

  • Positioning 2026
  • Product handbook
  • Pricing decision

Lea Brandt

Onboarding call

Priya Desai

Customer interview

Shared in the workspace, or one profile's own.

Company documents belong to the workspace and every profile draws on them; a profile's own files stay with that profile.

What comes out of Drive.

Which files are read, how you choose them, and what happens when they change.

All integrations
  • Docs, Slides, PDFs

    Google Docs and Slides, and PDFs stored in Drive.

  • Files, not folders

    You choose the files; folders are not synced as a whole.

  • Refreshed on change

    A changed file updates its document; a removed one removes it.

Questions about Google Drive

Build pipeline one post at a time