Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
What this does Receives a URL via webhook, uses Firecrawl to scrape the page into clean markdown, and stores it as vector embeddings in Pinecone. A visual, self hosted ingestion pipeline for RAG kn...
n8n-nodes-base.stickynote, n8n-nodes-base.webhook, n8n-nodes-base.code, @mendable/n8n-nodes-firecrawl.firecrawl, n8n-nodes-base.respondtowebhook, @n8n/n8n-nodes-langchain.vectorstorepinecone, @n8n/n8n-nodes-langchain.embeddingsopenai, @n8n/n8n-nodes-langchain.documentdefaultdataloader
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Firecrawl.
Original n8n.io sourceWhat this does
Receives a URL via webhook, uses Firecrawl to scrape the page into clean markdown, and stores it as vector embeddings in Pinecone. A visual, self-hosted ingestion pipeline for RAG knowledge bases. Adding a new source is as simple as sending a URL.
The second part of the workflow exposes a chat interface where an AI Agent queries the stored knowledge base to answer questions, with Cohere reranking for better retrieval quality.
How it works
Part 1: Ingestion Pipeline
url field/scrape fetches the page and converts it to clean markdownPart 2: RAG Chat Agent
🔥 Firecrawl 🌲 Pinecone 🧠 OpenAI Embeddings 🤖 OpenRouter (Claude Sonnet) 🎯 Cohere Reranker
Webhook usage
Send a POST request to the webhook URL:
curl -X POST https://your-n8n-instance/webhook/your-id \
-H "Content-Type: application/json" \
-d '{"url": "firecrawl.dev"}'
Pinecone setup
Your Pinecone index must be configured with 1536 dimensions to match the OpenAI text-embedding-3-small model output. See the sticky note inside the workflow for the exact index settings.
Requirements
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.
| Workflow | Scrape and ingest web pages into a Pinecone RAG stack with Firecrawl and OpenAI |
|---|---|
| Complexity | advanced |
| Nodes | 17 |
| Categories | Document Extraction, AI RAG |
| Author | Firecrawl |
| Published | 09 Mar 2026 |
Use the JSON export at /data/workflows/13964/13964.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.
What this does Receives a URL via webhook, uses Firecrawl to scrape the page into clean markdown, and stores it as vector embeddings in Pinecone. A visual, self hosted ingestion pipeline for RAG kn...
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.