Skip to main content

Notion to Pinecone vector store integration

Workflow preview

Workflow preview
100%
Notion to Pinecone vector store integration preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This n8n automation is designed to extract, process, and store content from Notion pages into a Pinecone vector store. Here's a breakdown of the workflow: Notion Page Added Trigger: The automation ...

Best for

  • Document Extraction automation workflows
  • AI RAG automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

@n8n/n8n-nodes-langchain.textsplittertokensplitter, n8n-nodes-base.notiontrigger, n8n-nodes-base.notion, n8n-nodes-base.filter, n8n-nodes-base.summarize, @n8n/n8n-nodes-langchain.documentdefaultdataloader, @n8n/n8n-nodes-langchain.embeddingsgooglegemini, @n8n/n8n-nodes-langchain.vectorstorepinecone

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Udit Rawat.

Original n8n.io source

1.1 Workflow description

Title
Notion to Pinecone vector store integration
Workflow name
Notion to Pinecone vector store integration

This n8n automation is designed to extract, process, and store content from Notion pages into a Pinecone vector store. Here's a breakdown of the workflow:

Notion - Page Added Trigger: The automation starts by monitoring for newly added pages in a specific Notion database. It triggers whenever a new page is created, capturing the page's metadata.

Notion - Retrieve Page Content: Once triggered, the automation fetches the full content of the newly added Notion page, including blocks like text, images, and videos.

Filter Non-Text Content: The next step filters out non-text content (such as images and videos), ensuring only textual content is processed.

Summarize - Concatenate Notion's blocks content: The remaining text content is concatenated into a single block of text for easier processing.

Token Splitter: The concatenated text is then split into manageable tokens, which are chunks of text that can be used for embedding.

Create metadata and load content: Metadata such as the page ID, creation time, and title are added to the content, making it easy to reference and track.

Embeddings Google Gemini: The processed text is passed through a Google Gemini model to generate embeddings, which are numerical representations of the text that capture its semantic meaning.

Pinecone Vector Store: Finally, the embeddings, along with the content and metadata, are stored in a Pinecone vector store, making it searchable and ready for use in applications like document retrieval or natural language processing tasks.

This workflow ensures that every new page added to the Notion database is processed into a format that can be easily searched and used in machine learning applications. The automation runs every minute to capture new data in real-time, providing an up-to-date and searchable vector database of Notion content.

Use Case:

This automation converts Notion pages into vector embeddings and stores them in Pinecone for enhanced search and AI-driven insights. It’s ideal for teams using Notion for knowledge management, enabling semantic search and context-based content retrieval. For example, employees can easily find relevant information across documents, and data scientists can use AI models to analyze and summarize the content stored in Notion.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Token Splitter

Type / Role
@n8n/n8n-nodes-langchain.textSplitterTokenSplitter - textSplitterTokenSplitter
Config choices
Version 1

Block 2 - Notion - Page Added Trigger

Type / Role
n8n-nodes-base.notionTrigger - notionTrigger
Config choices
Version 1

Block 3 - Notion - Retrieve Page Content

Type / Role
n8n-nodes-base.notion - notion
Config choices
Version 2.2

Block 4 - Filter Non-Text Content

Type / Role
n8n-nodes-base.filter - filter
Config choices
Version 2

Block 5 - Summarize - Concatenate Notion's blocks content

Type / Role
n8n-nodes-base.summarize - summarize
Config choices
Version 1

Block 6 - Create metadata and load content

Type / Role
@n8n/n8n-nodes-langchain.documentDefaultDataLoader - documentDefaultDataLoader
Config choices
Version 1

Block 7 - Embeddings Google Gemini

Type / Role
@n8n/n8n-nodes-langchain.embeddingsGoogleGemini - embeddingsGoogleGemini
Config choices
Version 1

Block 8 - Pinecone Vector Store

Type / Role
@n8n/n8n-nodes-langchain.vectorStorePinecone - vectorStorePinecone
Config choices
Version 1

3. Summary Table

Workflow Notion to Pinecone vector store integration
Complexity intermediate
Nodes 8
Categories Document Extraction, AI RAG
Author Udit Rawat
Published 25 Jan 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/2797/2797.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Notion to Pinecone vector store integration do?

This n8n automation is designed to extract, process, and store content from Notion pages into a Pinecone vector store. Here's a breakdown of the workflow: Notion Page Added Trigger: The automation ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction, AI RAG use case.