one-hub

n8n community node for One-Hub responses, file handling, folder management, and sync jobs

Package Information

Released: 5 mo ago
Downloads: 17 weekly / 81 monthly
Latest Version: 0.1.6
Author: Forstner Software Solutions

Documentation

n8n-nodes-one-hub

This is an n8n community node for One-Hub, a trusted enterprise knowledge interface that connects systems like Jira, SharePoint, Confluence, and files to deliver precise, source-backed answers in seconds.

One-Hub is designed for secure company use with GDPR-compliant operation, Austrian hosting, and on-premise readiness.

n8n is a fair-code licensed workflow automation platform.

Installation
Operations
Credentials
Compatibility
Usage
Resources
Version history

Installation

Follow the installation guide in the n8n community nodes documentation.

Operations

The node supports the following operations:

  • Response
  • Send Question: Sends a question to One-Hub and returns a non-streaming response including sources.
  • File
  • Upload: Uploads (and optionally creates intermediate folders if the API key also has role FolderCreate) and stores a file for a chat.
  • Delete: Deletes a file from the chat's file storage.
  • Sync
  • Trigger Sync: Starts embedding synchronization for all files and connectors in a chat and creates a summary.
  • Get Job Status: Retrieves the status of a previously started sync job.
  • Folder
  • Create: Creates a new folder in the chat's file storage.
  • Delete: Deletes a folder from the chat's file storage.

Credentials

To use this node, an API key must be created in One-Hub.

  • Cloud: Create an API key at app.one-hub.at/developer.
  • On-Premise: Create an API key in your own One-Hub instance.
  • Store the API key in the node credentials in n8n.

Optional for On-Premise:

  • Set Deployment Type to On-Premise.
  • Enter your own Chat API Base URL and File API Base URL.

Compatibility

The node should work with every n8n version.

Usage

Example: Send Question

Use this operation to ask One-Hub a question and receive a grounded answer with sources.

Expected Chat ID format:

  • UUID/GUID string, for example: 123e4567-e89b-12d3-a456-426614174000

Sample node configuration:

  • Resource: Response
  • Operation: Send Question
  • Chat ID: 123e4567-e89b-12d3-a456-426614174000
  • Input: Which Jira issues have the status "In Progress"?

What the response includes:

  • The generated answer text from One-Hub

Resources

Version history

Discussion