lucidlink-bridge

n8n community node for the self-hosted LucidLink Bridge microservice (writes files into a LucidLink filespace via the LucidLink Python SDK)

Package Information

Released: 4 mo ago
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.4
Author: Charles Leighton

Available Nodes

Documentation generating…

LucidLink Bridge icon
LucidLink Bridge
Write files into a LucidLink filespace via the self-hosted LucidLink Bridge microservice

Documentation

n8n-nodes-lucidlink-bridge

This is a community add-on, not part of the official LucidLink product. It exposes operations against a self-hosted lucidlink-bridge microservice that wraps the LucidLink Python SDK. To use this node you must deploy and run the bridge service separately.

For the n8n integration with LucidLink, see n8n-nodes-lucidlink.

This n8n community node lets you write files into a LucidLink filespace from n8n workflows. The official LucidLink LucidAPI doesn't expose endpoints for direct file-byte writes; this bridge fills the gap by running the LucidLink Python SDK as a long-lived HTTP service.

Installation
Prerequisites
Operations
Credentials
Usage
Relationship to other LucidLink tools
Version history

Installation

Follow the n8n community-nodes installation guide.

The package name is n8n-nodes-lucidlink-bridge.

Prerequisites

You must deploy a lucidlink-bridge instance somewhere reachable from your n8n deployment. The bridge is a Python FastAPI service that runs the LucidLink Python SDK, authenticates with a service account, and links one filespace at startup. One container per filespace.

(Bridge source / deployment guide: TBD.)

Operations

Operation Description
Write File from URL Stream a file from an HTTPS source (e.g. a presigned URL) into the LucidLink filespace
Sync Force-flush any deferred writes so they become visible to other LucidLink clients

Credentials

LucidLink Bridge API

Field Description Example
Bridge URL Base URL of your bridge deployment https://sdk.your-domain.com
Bridge API Key Bearer token matching the bridge's BRIDGE_API_KEY env var (long random hex string)

The credential is tested via POST /v1/files/sync, which exercises the URL, the bearer token, and the daemon link end-to-end.

Because the bridge is pinned to one filespace at startup, each Bridge URL corresponds to a single filespace. To write to multiple filespaces from one n8n instance, deploy a bridge container per filespace and create a separate credential per bridge.

Usage

Typical workflow shape

[webhook trigger]  →  [LucidLink Bridge: Write File from URL]
                          Destination Path = /ingest/{{ $json.filename }}
                          Source URL       = {{ $json.presigned_url }}
                          Sync             = Now

The bridge fetches the Source URL directly, streaming bytes into the filespace without them passing through n8n. This is what lets the bridge handle multi-GB files without hitting n8n's N8N_PAYLOAD_SIZE_MAX limit or saturating n8n's binary-data storage.

Source Headers

If the Source URL requires authentication (e.g. an internal API with bearer auth), use the Source Headers field to attach those headers to the bridge's fetch request. The bridge forwards them as-is when calling the Source URL.

Sync semantics

  • Now (recommended) — bridge calls sync_all() before returning. The file is visible to other LucidLink clients by the time you see the HTTP response.
  • Deferred — bridge returns as soon as the local write completes. Use for bulk ingestion followed by a single Sync operation at the end of the workflow.

Path validation

The bridge rejects dest_path values that would silently misbehave at the SDK level:

  • empty paths
  • paths not starting with /
  • the root path /
  • paths ending with /
  • paths that resolve to an existing directory in the filespace

All return a 400 invalid_dest_path error so n8n surfaces a clear failure rather than a silent loss.

Relationship to other LucidLink tools

Tool What it wraps Use when
n8n-nodes-lucidlink Official LucidAPI REST surface Managing filespaces, entries, members, permissions, direct links, etc.
n8n-nodes-lucidlink-bridge (this) Self-hosted bridge microservice Writing file bytes into a filespace from a workflow

The two are complementary — most non-trivial workflows use both.

Version history

0.1.0

Initial release.

  • Operations: Write File from URL, Sync
  • Credential: LucidLink Bridge API (Bridge URL + Bridge API Key)

Discussion