How do I import "Prod: Notion to Vector Store - Dimension 768" into n8n?

Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.

Which integrations does "Prod: Notion to Vector Store - Dimension 768" use?

It uses: textSplitterTokenSplitter, notion, filter, summarize, documentDefaultDataLoader, embeddingsGoogleGemini, vectorStorePinecone. The flow diagram above shows how each service connects across the 8 nodes. Filter OpenRuna by integration to find related workflows and tools.

Can I import a sanitized export without credentials?

Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own textSplitterTokenSplitter and notion credentials in n8n after import.

What trigger type does "Prod: Notion to Vector Store - Dimension 768" use?

Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.

Is "Prod: Notion to Vector Store - Dimension 768" free to use?

OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for textSplitterTokenSplitter, notion, filter, summarize, documentDefaultDataLoader, embeddingsGoogleGemini, vectorStorePinecone.

← Workflows

Prod: Notion to Vector Store - Dimension 768

8 nodes · textSplitterTokenSplitter, notion, filter, summarize, documentDefaultDataLoader, embeddingsGoogleGemini

Engine: n8n
Nodes: 8
Trigger: scheduled/triggered
Source file: 1570_Filter_Summarize_Automation_Triggered.json

Workflow flow

IntegrationsTextSplitterTokenSplitter

NotionFilterSummarizeDocumentDefaultDataLoaderEmbeddingsGoogleGeminiVectorStorePinecone@n8n/n8n-nodes-langchain.textSplitterTokenSplitter@n8n/n8n-nodes-langchain.documentDefaultDataLoader@n8n/n8n-nodes-langchain.embeddingsGoogleGemini@n8n/n8n-nodes-langchain.vectorStorePinecone

100%

Token Splitter

@n8n/n8n-nodes-langchain.textSplitterTokenSplitter

TRIGGER

Notion - Page Added Trigger

Notion

Create metadata and load content

@n8n/n8n-nodes-langchain.documentDefaultDataLoader

Embeddings Google Gemini

@n8n/n8n-nodes-langchain.embeddingsGoogleGemini

Notion - Retrieve Page Content

Notion

Filter Non-Text Content

Filter

Summarize - Concatenate Notion's blocks content

Summarize

Pinecone Vector Store

@n8n/n8n-nodes-langchain.vectorStorePinecone

8 steps · flows top to bottom, branches left to right

Browse by integration

textSplitterTokenSplitter notion filter summarize documentDefaultDataLoader embeddingsGoogleGemini vectorStorePinecone

Browse all integrations →

Download n8n JSON Download sanitized JSON Download flow graph

Import into n8n

Download the n8n JSON file (full or sanitized).
In n8n: Workflows → Import from file.
Open each node and reconnect credentials to your accounts.
Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Prod: Notion to Vector Store - Dimension 768 (8-node n8n automation, textSplitterTokenSplitter, notion, filter, summarize, documentDefaultDataLoader, embeddingsGoogleGemini, vectorStorePinecone) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

This n8n workflow, "Prod: Notion to Vector Store - Dimension 768", wires together textSplitterTokenSplitter, notion, filter, summarize, documentDefaultDataLoader, embeddingsGoogleGemini, vectorStorePinecone in 8 nodes. 8 nodes · textSplitterTokenSplitter, notion, filter, summarize, documentDefaultDataLoader, embeddingsGoogleGemini It starts from a scheduled/triggered trigger and routes data through every node in order. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

Import "Prod: Notion to Vector Store - Dimension 768" into n8n, reconnect credentials for textSplitterTokenSplitter, notion, filter, summarize, documentDefaultDataLoader, embeddingsGoogleGemini, vectorStorePinecone, and run the same automation in your own workspace.
Use it as a starting template when wiring textSplitterTokenSplitter, notion, filter, summarize, documentDefaultDataLoader, embeddingsGoogleGemini, vectorStorePinecone — adjust node parameters to your accounts and record IDs.
Study how data moves from textSplitterTokenSplitter to notion before building your own variant.
Share it with your team as a documented reference for scheduled/triggered automations in the textSplitterTokenSplitter stack.

Example output

Imported into n8n, "Prod: Notion to Vector Store - Dimension 768" exposes 8 configured nodes. Trigger type: scheduled/triggered. Integrations: textSplitterTokenSplitter, notion, filter, summarize, documentDefaultDataLoader, embeddingsGoogleGemini, vectorStorePinecone. Set your credentials on the textSplitterTokenSplitter node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "Prod: Notion to Vector Store - Dimension 768" JSON into a plain-English runbook, node by node. It can flag where textSplitterTokenSplitter rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for textSplitterTokenSplitter, notion, filter, summarize, documentDefaultDataLoader, embeddingsGoogleGemini, vectorStorePinecone. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Prod: Notion to Vector Store - Dimension 768" — extract textSplitterTokenSplitter IDs and secrets into environment variables without changing the 8-node structure.

Frequently asked questions

How do I import "Prod: Notion to Vector Store - Dimension 768" into n8n?: Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Prod: Notion to Vector Store - Dimension 768" use?: It uses: textSplitterTokenSplitter, notion, filter, summarize, documentDefaultDataLoader, embeddingsGoogleGemini, vectorStorePinecone. The flow diagram above shows how each service connects across the 8 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?: Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own textSplitterTokenSplitter and notion credentials in n8n after import.
What trigger type does "Prod: Notion to Vector Store - Dimension 768" use?: Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Prod: Notion to Vector Store - Dimension 768" free to use?: OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for textSplitterTokenSplitter, notion, filter, summarize, documentDefaultDataLoader, embeddingsGoogleGemini, vectorStorePinecone.