Dynamic Scripture Retrieval via GetBible API - n8n Workflow

• Technical content creators who need to integrate specific religious texts into applications.


• Developers building custom knowledge bases or RAG systems that require specialized data sources.


• Users looking for modular n8n templates that demonstrate reusable workflow patterns.


• Anyone needing a reliable, self-contained n8n workflow component for external API querying.

This n8n workflow, titled 'GetBible Query,' is designed to operate as a self-standing, modular component. It solves the problem of needing to query the GetBible API with multiple references formatted in a specific way. While the API requires references to be semicolon-separated within the URL path, the standard input to the n8n workflow is usually an array. This n8n workflow handles the crucial data preparation automatically, ensuring seamless communication with the external API.

By leveraging the Execute Workflow n8n trigger, this n8n workflow can be easily integrated into larger business process n8n templates, acting as a backend service for retrieving specific scripture passages based on parameters like translation and book references. The final step ensures the output conforms precisely to the expected API response structure, making it highly compatible for downstream consumption.

The execution of this n8n workflow begins immediately upon being called by an external process via the Entry n8n trigger (an Execute Workflow Trigger n8n node). This n8n trigger expects a structured JSON payload containing an array of references, the desired translation, and the version.

1. Data Modeling (ModelJson n8n node): The crucial step is data transformation. A Code n8n node is used to process the incoming JSON. It takes the array of references (e.g., ["1 John 3:16", "Rom 3:16"]) and joins them into a single, semicolon-separated string (1 John 3:16; Rom 3:16). This prepares the data format required by the GetBible API endpoint.


2. API Call (API Query to GetBible n8n node): An HTTP Request n8n node then constructs the API call. It dynamically injects the prepared reference string, translation (defaulting to 'kjv'), and version (defaulting to 'v2') directly into the URL path, executing the query to fetch the scripture.


3. Result Mapping (Map API Respons to Result n8n node): Finally, a Set n8n node maps the raw API response data into a standardized structure under the key result. This ensures the output of this n8n workflow matches the expected API format, providing consistency for projects utilizing this component. This completes the core logic flow of the n8n templates solution.

To utilize this dynamic scripture retrieval n8n workflow:

1. Import the JSON: Copy the provided n8n workflow JSON code and paste it into your n8n instance using the 'New' -> 'Import from JSON' option.


2. No Credentials Required: This specific n8n workflow does not require credentials for the GetBible API itself, as it relies on public endpoints.


3. Test the n8n Trigger: Use the example JSON provided in the 'Entry' n8n node to test the execution. The example data includes references, translation (kjv), and version (v2).


4. Integration: To use this as a sub-workflow, set up an Execute Workflow n8n node in your primary n8n workflow and point it to this template, ensuring you pass the required JSON input payload (references array, translation string).

• Entry (Execute Workflow Trigger): Acts as the entry point and n8n trigger for the sub-workflow. It is configured to receive structured JSON input, defining the scripture references and translation required for the query.


• ModelJson (Code n8n node): This critical custom code n8n node iterates through the input data. Its primary function is to transform the array of scripture references into a single, semicolon-separated string, which is necessary for the GetBible API URL structure. This is essential for the reliability of the overall n8n workflow.


• API Query to GetBible (HTTP Request n8n node): This n8n node handles the data retrieval. It uses dynamic expressions to construct the full URL: https://query.getbible.net/{{ $json.version }}/{{ $json.translation }}/{{ $json.references }}. It fetches the raw scripture text.


• Map API Respons to Result (Set n8n node): This final manipulation n8n node takes the raw JSON output from the API and wraps it under a new key called result. This ensures the output of this n8n workflow adheres to a consistent API standard, making the n8n templates solution robust for various integrations.