Skip to content
ClickRuntime

Connect Pinecone to Slack

Pinecone stores what your team knows, such as help articles, past tickets or customer feedback, in a form that can be searched by meaning. Slack is where the team works. Connecting them brings relevant knowledge into the conversation: draft answers to new tickets, and summaries of what customers keep saying.
Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Ideas

What you can do with Pinecone and Slack

Support drafts and feedback summaries from your Pinecone index, shared in Slack. These are ready-made starting points. Anything else you can describe works too.
DailyAI

Summarise new App Store reviews for your product team in Slack

Each day new App Store reviews are stored in Pinecone and a summary of the main complaints and praise is posted to Slack.

See how it works
The moment it happensAI

Draft answers to new support tickets and share them in Slack

When a support ticket arrives, a draft answer based on your knowledge base is posted in Slack for the team to review.

See how it works Your own logic

Any other automation you can describe in words

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

See how to build your own

Build your own

Build any Pinecone and Slack automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what should happen between Pinecone and Slack 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 answer when the match score is over 0.8; otherwise reply that I do not know and tag the docs owner.

Each Friday, post the questions asked this week that had no good match.

Use cases

Why people connect Pinecone and Slack

How the two apps work together

  • A check every few minutes reads new messages in the channels you choose.
  • The script searches Pinecone and writes an answer with AI.
  • It replies in Slack with the answer and source.

  • Teams answering questions in Slack

    A question in a channel is answered from documents in Pinecone. Fewer repeat questions.

  • Support leads reviewing drafts

    Draft answers are posted to Slack before sending. Quality stays high.

  • Product teams analysing feedback

    Feedback indexed in Pinecone is searched for themes. Patterns are posted.

  • Engineers searching runbooks

    Runbooks are indexed and searchable from Slack. Incidents resolve faster.

More apps

Pinecone, Slack 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.

Index Drive docs

Index my Google Drive docs in Pinecone and answer questions in #ask with the file link.

Index Notion pages

Index my Notion wiki in Pinecone and answer questions in #help.

Draft ticket replies

Draft replies to Zendesk tickets from Pinecone and post them to #support for review.

Setup

Connect Pinecone and Slack 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.

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.

Slack

Team chat

  1. At api.slack.com/apps, create a new app from scratch in your workspace.
  2. Under OAuth & Permissions, add the bot scopes the automation needs, such as chat:write, channels:read and channels:history.
  3. In the ClickRuntime dashboard, open Connections, choose Slack and enter your app's details, then install it to your workspace.
  4. In each channel the automation should use, type /invite @your-app-name.

FAQ

Questions about connecting Pinecone and Slack

Do I need a Pinecone account?
Yes. Use an index with built-in embedding and save your Pinecone API key in your ClickRuntime dashboard.
What goes into the index?
Whatever the automation is for: help articles and past answers for support drafts, or customer reviews for feedback summaries.
Does anything get sent to customers?
No. These automations post drafts and summaries to Slack. A person decides what is sent.
Which channel do posts go to?
The channel you choose, such as #support or #product.
Can it answer in threads?
Yes. Answers are posted in the thread of the question.
Can it cite the source?
Yes. The source title and link are included.
Can it be limited to one channel?
Yes. List the channels it should read.

Related pages

Keep exploring

Tell your assistant what Pinecone and Slack should do together

Free plan. No credit card.

Add to ChatGPTAdd to Claude