LucidLinkInstall

Summary

Create a data store in the specified filespace by sending its name, kind, and, for an S3 data store, its storage credentials and configuration to the LucidAPI.

Inputs

• Filespace ID (required) — Filespace in which to create the data store.
• Kind (required) — Choose S3 Data Store or HTTP Link Data Store. HTTP Link Data Stores require filespace format 3.7 or later; no other kind-specific parameters are required for that choice.
• Name (required) — Name for the data store.
• S3 Access Key (required) — S3 credential; shown and required when Kind is S3 Data Store.
• S3 Secret Key (required) — S3 credential; shown and required when Kind is S3 Data Store.
• S3 Bucket Name (required) — Bucket to use; shown and required when Kind is S3 Data Store.
• Use Virtual Addressing (required) — Whether to use virtual-hosted-style S3 addressing; shown and required for S3, defaults to true.
• S3 Region — AWS region for S3. Either this or S3 Endpoint must be provided; empty values are omitted.
• S3 Endpoint — Custom S3 endpoint URL. Either this or S3 Region must be provided; empty values are omitted.
• URL Expiration (Minutes) — Expiration for presigned URLs on S3 data stores; defaults to 10080 minutes, with a declared range of 4320–10080.
• Request Options — Optional request settings: batching, accepting invalid SSL certificates, HTTP proxy, and timeout.

Output shape

A single API response item, typically containing the created data store record.

For node version 2, a response object with a data field is unwrapped to that payload; if data is an array, its elements are emitted as separate items. Empty strings, nulls, undefined values, and empty nested body objects are removed before the request.

Links

• n8n community nodes installation guide