n8n-nodes-scriptureflow
v0.1.2
Published
Use ScriptureFlow in n8n workflows to discover translations and retrieve attributed Scripture from the public API.
Maintainers
Readme
n8n-nodes-scriptureflow
An n8n community node package for ScriptureFlow, a structured Scripture API for developers, ministries, educators, and automation builders.
Status: The package is published to npm. Version
0.1.1is the current npm release, and0.1.2is the prepared Creator Portal metadata release. This package has not been approved through the n8n Creator Portal and is not verified by n8n.
Public preview
- Base URL:
https://scriptureflow-api-preview.pages.dev - No API key is required during public preview.
- Future optional API-key support may be added when ScriptureFlow monetization and API-key support are ready.
- Discover exact, case-sensitive translation version keys from
translations.json. - Some translations may be partial; check available books before assuming coverage.
Scripture data rules
- Do not silently substitute translations.
- Do not invent or paraphrase Scripture text.
- Preserve the returned reference and version attribution.
- Keep generated commentary separate from Scripture text.
- Surface ScriptureFlow API errors instead of filling in missing text.
Installation
Install n8n-nodes-scriptureflow as a community node package in n8n.
In n8n, open Settings > Community nodes, choose Install, enter:
n8n-nodes-scriptureflowThen confirm the installation and search for ScriptureFlow in the node picker.
For self-hosted npm-based installations, install the package in the n8n custom nodes location supported by your deployment, then restart n8n:
npm install n8n-nodes-scriptureflowSupported operations
The current package contains these operations:
- Translation > Get Many retrieves translation keys and metadata from
/translations.jsonwithout hiding catalog statuses. - Book > Get Many retrieves the books available for a Version Key and helps expose partial translation coverage.
- Scripture > Get Verse retrieves one structured book/chapter/verse lookup directly from
/api/verse. - Scripture > Get Quick Verse retrieves a verse selected at request time from
/api/quick-verse; results may differ between executions. - Scripture > Get Generated Verse of the Day retrieves the generated static
/{version}/random.jsonresource and remains distinct from Quick Verse.
Raw ScriptureFlow JSON is returned by default. Catalog operations support conventional Return All/Limit controls. Scripture operations offer an optional Simplify boolean without inventing or paraphrasing Scripture text.
See the node roadmap for deferred operations and release gates.
Usage examples
List available translations
- Add the ScriptureFlow node to a workflow.
- Set Resource to Translation.
- Set Operation to Get Many.
- Leave Return All enabled to list the available translation keys and metadata.
Retrieve John 3:16 from en-lsv
- Add the ScriptureFlow node to a workflow.
- Set Resource to Scripture.
- Set Operation to Get Verse.
- Set Version Key to
en-lsv. - Set Book to
John, Chapter to3, and Verse to16. - Execute the node to retrieve the API-provided ScriptureFlow response with reference and version attribution.
Credentials
No credentials are required for public preview mode. A future optional API key credential may be introduced later; any API key or token field will be stored as a sensitive/password field.
Development
This repository uses the official n8n-node package structure and CLI commands.
npm install
npm run lint
npm run build
npm run devnpm run dev starts an interactive local n8n development session, normally at http://localhost:5678. It is intended for manual node discovery and workflow testing.
The package has no runtime dependencies. n8n-workflow is declared as a peer dependency, and build/lint tooling is kept in development dependencies.
Publishing status
Version 0.1.1 is published to npm with provenance, and the n8n community package scanner passed. Version 0.1.2 is prepared to add npm author email metadata for n8n Creator Portal submission. Future releases use npm trusted publishing/OIDC; normal pushes and pull requests do not publish the package. No Creator Portal approval has occurred.
Follow the release checklist and review publishing readiness before creating any release tag. Do not publish locally for the verified-submission path.
ScriptureFlow resources
- API preview
- OpenAPI 3.1 contract
- Swagger API Reference
- Postman collection
- n8n examples
- Public code examples
- AI usage guide
