LucidLinkInstall

Summary

Create an external file entry in a LucidLink filespace by linking an S3 object or a publicly accessible HTTP/HTTPS file. The node sends a POST request to the filespace external entries endpoint and returns the response data as output items.

Inputs

• Filespace ID (required) — ID of the filespace where the entry will be created.
• Path (required) — Full filesystem path for the new entry, such as /Documents/report.pdf.
• Kind (required) — Choose Single Object File (S3) or HTTP Link File.
• Data Store ID (required) — For an S3 entry, the ID of the data store containing the S3 credentials. For an HTTP entry, optionally provide an HTTP link data store ID; it is required for filespace format 3.7 and above and must be empty on 3.6 and below.
• S3 Object ID (required) — For an S3 entry, the object key or path within the bucket.
• S3 metadata — Optionally provide the object checksum and size together. Supplying both skips the S3 bucket access check (HEAD request); leave both empty to allow the check.
• HTTP File URL (required) — For an HTTP entry, the publicly accessible HTTP or HTTPS URL of the file.
• HTTP file size — For an HTTP entry, optionally provide the file size in bytes to skip the URL access check (HEAD request).

Output shape

A list of n8n items containing the response data.

For node version 2, a response object with a data field is unwrapped: an array in data becomes multiple items, and an object in data becomes one item. Empty strings and empty nested objects are pruned from the request body.

Links

• n8n community nodes installation guide