Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Workflow updated on 17/06/2024: Added 'Summarize' node to avoid creating a row for each Notion content block in the Supabase table. Store Notion's Pages as Vector Documents into Supabase This workf...
n8n-nodes-base.stickynote, @n8n/n8n-nodes-langchain.embeddingsopenai, @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
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Dataki.
Original n8n.io sourceWorkflow updated on 17/06/2024: Added 'Summarize' node to avoid creating a row for each Notion content block in the Supabase table.
This workflow assumes you have a Supabase project with a table that has a vector column. If you don't have it, follow the instructions here: Supabase Langchain Guide
This workflow automates the process of storing Notion pages as vector documents in a Supabase database with a vector column. The steps are as follows:
Notion Page Added Trigger:
Page Added in Notion DatabaseRetrieve Page Content:
Get Blocks ContentFilter Non-Text Content:
Filter - Exclude Media ContentSummarize Content:
Summarize - Concatenate Notion's blocks contentStore in Supabase:
Store Documents in SupabaseGenerate Embeddings:
Generate Text EmbeddingsCreate Metadata and Load Content:
Load Block Content & Create MetadataSplit Content into Chunks:
Token SplitterThis catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Store Notion's Pages as Vector Documents into Supabase with OpenAI |
|---|---|
| Complexity | intermediate |
| Nodes | 9 |
| Categories | Document Extraction, AI RAG |
| Author | Dataki |
| Published | 12 Jun 2024 |
Use the JSON export at /data/workflows/2290/2290.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
Workflow updated on 17/06/2024: Added 'Summarize' node to avoid creating a row for each Notion content block in the Supabase table. Store Notion's Pages as Vector Documents into Supabase This workf...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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.