Automation & utilitiesCodeExecute Workflow TriggerHTTP RequestEdit Fields

getBible Query v1.0

Configured with Execute Workflow Trigger, HTTP Request. Review the connections and setup before adapting this template.

Download workflow JSON View files on GitHub ↗4 nodes · MIT

Workflow preview

Node categories in this workflow

Trigger
Code
Web / API
Transform

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
Node	Category	Type	Operation
Entry	Trigger	Execute Workflow Trigger	See node parameters
ModelJson	Code	Code	See node parameters
API Query to GetBible	Web / API	HTTP Request	See node parameters
Map API Respons to Result	Transform	Edit Fields	See node parameters

Setup

Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

None declared. HTTP requests and Code nodes may still need configuration.

Workflow notes

GetBible Query Workflow Documentation

Overview

The GetBibleQuery workflow is a modular and self-standing workflow designed to retrieve scriptures based on provided references. It serves as an intermediary layer that takes in a structured JSON object, extracts the references, and returns the corresponding scriptures in the same format as if they were retrieved directly from the API.

This workflow is highly adaptable and can be integrated into various projects where scriptural references need to be dynamically fetched.

JSON Input Structure

The workflow expects a JSON object with the following parameters:

References should include the book name, chapter, and verse(s).
Multiple verses can be separated by commas (e.g., John 3:16,18).
Ranges can be specified using a dash (e.g., John 3:16-18).
The Bible translation to be used.
Specifies the API version (v2)

Example JSON Input:

{
  "references": [
      "1 John 3:16",
      "Jn 3:16",
      "James 3:16",
      "Rom 3:16"
  ],
  "translation": "kjv",
  "version": "v2"
}

API Response Format

The response returned by this workflow follows the same API format as if the request were made directly to the source API. This ensures compatibility with projects that rely on standard API responses.

Example JSON Response (in this workflow):

{
  "result": {
    "kjv_62_3": {
      "translation": "King James Version",
      "abbreviation": "kjv",
      "lang": "en",
      "language": "English",
      "direction": "LTR",
      "encoding": "UTF-8",
      "book_nr": 62,
      "book_name": "1 John",
      "chapter": 3,
      "name": "1 John 3",
      "ref": [
        "1 John 3:16"
      ],
      "verses": [
        {
          "chapter": 3,
          "verse": 16,
          "name": "1 John 3:16",
          "text": "Hereby perceive we the love of God, because he laid down his life for us: and we ought to lay down our lives for the brethren."
        }
      ]
    }
  }
}

Integration and Usage

The GetBible Query workflow is designed for easy integration into any project that requires scripture retrieval. Simply pass the appropriate JSON object as input, and it will return the requested scripture passages.

Support

For any questions or additional assistance, please visit our Support desk or API documentation

getBible Query v1.0

Purpose and structure

This folder contains the getBible Query v1.0 workflow. Its executable nodes use code, executeWorkflowTrigger, httpRequest, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Entry

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/1871_HTTP_Executeworkflow_Import_Webhook.json MIT; preserve source notices.

More in Automation & utilities

1/ Add Your credentials 2. Refresh Pipedrive tokens 6