Skip to content

Release 0.2.0

Choose a tag to compare

@chleighton1 chleighton1 released this 05 Sep 15:55
· 2 commits to main since this release

Aligned with LucidLink LucidAPI v1.5.0

⚠️ Upgrading: node version 2

The node now ships two versions and defaults to version 2 for newly added nodes.

  • Version 2 strips the LucidAPI data envelope and splits lists into one item per
    record — reference fields as {{ $json.id }}
  • Version 1 returns the raw response — {{ $json.data.id }}

Existing workflows are unaffected. Nodes already on a canvas keep the version they
were created with, so their expressions keep resolving. To adopt version 2, replace the
node and drop data from any downstream expressions.

Paginated operations (Entry → List Children, External Entry → List IDs, Permission →
List) unwrap to a single item holding both the records and nextCursor, so cursor-based
loops keep working. Data Store operations are unchanged, because the API doesn't wrap them.

New resources

  • Service Account — Create (optionally with an initial key), Get Many, Get, Delete
  • Service Account Key — Create, Get Many, Delete

These let you automate credential rotation. Keys can be single-use or given an expiry.
The token is returned only once, in the response that creates it.

Fixes

  • Data Store → Create now has a Kind selector for S3DataStore and
    HttpLinkDataStore. Previously kind was hard-coded to S3DataStore, so HTTP link
    data stores could not be created at all. The S3 credential fields are now only shown,
    and only sent, for S3DataStore.
  • Data Store → Create no longer sends blank optional fields as empty strings.
    Leaving S3 Endpoint or S3 Region empty omits the key instead of sending "",
    which the API rejects.
  • External Entry → Create can now set HTTP Link Data Store ID for HttpLinkFile
    entries, which the API requires on filespace format 3.7 and above. Previously the field
    was only available for SingleObjectFile, so HttpLinkFile creates failed on those
    filespaces with no way to fix it from the node.
  • External Entry → Create/Update gained the optional metadata fields that skip the
    server-side HEAD access check (object checksum + size, HTTP file size) — useful for
    bulk imports and for objects the API can't reach directly.
  • Filespace → Create omits blank Customer Storage: Endpoint and Bucket Name.
    The API requires endpoint to be absent when the region is a known provider region.
  • Member → Update Role no longer sends [""] when Filespace IDs is left blank.

Documentation

Documented the response envelope and node versions, service account key handling,
HttpLinkDataStore, Update Credentials being S3-only, service accounts as permission
principals, the entry name character restrictions, and the 1–100 range on bulk
membership. Added the previously undocumented Health resource and corrected the
operation count (12 resources, 48 operations).

Full changelog: v0.1.6...v0.2.0
npm: https://www.npmjs.com/package/n8n-nodes-lucidlink/v/0.2.0