Use Sourcey-generated documentation inside n8n workflows.
This community node reads the public artefacts emitted by a Sourcey static docs site:
documents.jsonfor search candidates: every page, operation and schema, each with its own Markdown, which the node reads for its contentllms-full.txtfor whole pages, and for a document whose Markdown cannot be readsitemap.xmlfor ingestion
A site built before Sourcey 3.7.1 publishes search-index.json in place of
documents.json, and the node reads that instead.
It does not need credentials for public docs and does not run sourcey build
inside n8n.
Install n8n-nodes-sourcey from the n8n community nodes panel, or install it
manually in a self-hosted n8n instance.
The package is published on npm as n8n-nodes-sourcey, from GitHub Actions
with npm provenance, which its npm page shows for each release:
- npm: https://www.npmjs.com/package/n8n-nodes-sourcey
- source: https://github.com/sourcey/n8n-nodes-sourcey
Creator Portal verification is pending. Until n8n grants verified status, the package is available as a community node for self-hosted n8n installs and any n8n environment that allows community packages.
Returns one item with:
context: packed documentation context ready for an AI Agent promptcitations: source URLs and titlesdocuments: hydrated source documentsconfidence:none,low,medium, orhighstatus:ok,weak_results, orno_results
Use this for Chat Trigger -> Sourcey -> AI Agent -> Respond workflows.
Returns one item per ranked result from documents.json, each page, operation
and schema a result of its own. Each item includes title, URL, excerpt, tab,
category, score, and metadata, with the method and path of an operation.
Use this for branching, result selection, and support routing.
Fetches one page by path or URL. It prefers llms-full.txt and falls back to
HTML text extraction when the LLM artefact is missing.
Returns one item per page or chunk for ingestion workflows. Use this with embeddings and vector-store nodes.
Build docs in CI, then use this node against the deployed site.
The recommended workflow is:
- n8n receives a GitHub webhook, schedule, release event, or manual trigger.
- n8n dispatches a GitHub Actions workflow using
sourcey/build-docs. - GitHub Actions builds and deploys the static Sourcey site.
- n8n waits for the deployment URL.
- n8n runs Sourcey Retrieve Context, Search, Fetch Page, or Load All.
This keeps build work in CI and keeps the n8n node fast, dependency-free, and verification-friendly.
Import the JSON files in workflows/:
ask-docs-chatbot.jsonvector-store-ingestion.jsonsupport-question-router.jsonbuild-and-index-sourcey-docs.json
The workflows avoid Code and Function nodes. If an example needs custom JavaScript glue, the Sourcey node API should be improved instead.
None in Phase 1. The node consumes public Sourcey docs sites.
This package is generated from the official n8n-node scaffold and uses the
programmatic node style. It keeps runtime dependencies empty for verified
community-node eligibility. Releases are published from GitHub Actions so npm
can attach provenance, which n8n requires for Creator Portal verification.
npm install
npm run typecheck
npm test
npm run buildRun a local n8n instance with the node loaded:
npm run dev