Skip to content
ClickRuntime

Connect Google Drive to Pinecone

Google Drive holds what your company knows: policies, help articles, reports and contracts. Pinecone makes that content searchable by meaning, so a question finds the right passage even when the words differ. Connecting them keeps the index in step with your folders and lets people get answers from your documents, with the source file named.
Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Ideas

What you can do with Google Drive and Pinecone

Answers, summaries and reply drafts built from the documents in your Drive folders. These are ready-made starting points. Anything else you can describe works too.
The moment it happensAI

Answer questions from your Drive documents, with the source named

Send a question and get an answer drawn from your company documents in Drive, quoting the file and passage it came from.

See how it works
Every 15 minutes

Keep a Pinecone index in step with a Drive folder

New and edited files in your Drive folder are added to Pinecone within minutes, and files you remove are taken out of the index.

See how it works
Every hourAI

Get an analysis of each new earnings report compared with past quarters

When a new earnings report lands in your Drive folder, it is indexed and you get an email comparing it with earlier quarters.

See how it works
Every 5 minutesAI

Draft replies to support emails from your Drive help docs

Each new support email gets a draft reply in Gmail, written from the help documents you keep in Drive.

See how it works
Every hourAI

Get an accounting summary for each new EDI or export file in Drive

When a new EDI or accounting export lands in your Drive folder, it is indexed and you get an email summarising its bookings.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Google Drive and Pinecone, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Google Drive and Pinecone automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what should happen between Google Drive and Pinecone in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Only index Google Docs and PDFs in the "Approved" folder, and remove vectors when a file is deleted.

Each week, email me a list of files that failed to index and why.

Use cases

Why people connect Google Drive and Pinecone

How the two apps work together

  • A check every few minutes looks for new or changed files in the Drive folders you choose.
  • The script reads text, splits it into chunks, creates embeddings and upserts them to Pinecone.
  • Questions from another source query Pinecone and return answers with the Drive file link.

  • Teams searching internal documents

    Drive documents are indexed in Pinecone so questions return answers with the source file. Knowledge is easier to find.

  • Support teams using help docs

    Help articles in Drive feed answers to support questions. Answers match the docs.

  • Analysts working with reports

    Reports in Drive are searchable by meaning. Insights are found faster.

  • Consultants reusing past work

    Past proposals are indexed for reuse. New work starts from good examples.

More apps

Google Drive, Pinecone and other apps in one automation

An automation isn't limited to two apps. Add the next step in another app and it runs as part of the same automation.

Ask in Slack

When someone asks a question in #ask-docs, search my Pinecone index of Drive files and reply with the answer and file link.

Embeddings with OpenAI

Index my Drive folder into Pinecone using OpenAI embeddings and update changed files every hour.

Answer support emails

Draft replies to support emails using my Pinecone index of Drive help docs.

Setup

Connect Google Drive and Pinecone once

Every idea on this page uses the same two connections, so you set them up once. If one is missing, your assistant tells you and links to the right place.

Google Drive

File storage

  1. At console.cloud.google.com, create a project and enable the Google Drive API.
  2. Set up the OAuth consent screen and add the scope https://www.googleapis.com/auth/drive.
  3. Create an OAuth client of type Web application with the redirect URI https://clickruntime.com/oauth/callback.
  4. In the ClickRuntime dashboard, open Connections, choose Google Drive and enter the client ID and secret, then connect.
  5. Prefer a service account? Under IAM & Admin → Service Accounts, create one and add a JSON key, share your folders or a Shared Drive with its email, and save the key as a secret on Connections & secrets.

Pinecone

AI / Vector database

  1. In the Pinecone console, open the project that holds your index.
  2. Go to API Keys and create a new API key, then copy it.
  3. In the ClickRuntime dashboard, open Connections & secrets and save the key as a secret for Pinecone. It is sent in the Api-Key header.

FAQ

Questions about connecting Google Drive and Pinecone

Do I need a Pinecone account?
Yes. Create an index with built-in embedding in Pinecone, then save your Pinecone API key in your ClickRuntime dashboard. Pinecone's free starter plan is enough for many small document sets.
Which Drive files can be indexed?
Google Docs and plain text files directly. PDFs can be converted to text through Google Drive first; scanned images of text work less reliably.
Does it change my Drive files?
No. Files are read, never edited. Converting a PDF makes a temporary copy that is removed straight after.
Who can see the indexed content?
Anyone who can query your Pinecone index, which by default is only your automations. Keep confidential folders out of shared indexes.
Which file types can it read?
Google Docs, Sheets, Slides and PDFs are common. Other formats depend on text extraction.
Does it re-index changed files?
Yes. It compares modified times and updates only changed files.
Which embedding model does it use?
The one you choose, such as Pinecone's hosted models or another provider.

Related pages

Keep exploring

Tell your assistant what Google Drive and Pinecone should do together

Free plan. No credit card.

Add to ChatGPTAdd to Claude