Package Information
Documentation
n8n-nodes-space-atlas
An n8n community node for Space Atlas —
drives, folders and assets from inside a workflow.
Install
In n8n: Settings → Community nodes → Install, then enter:
n8n-nodes-space-atlas
Self-hosted n8n only; n8n Cloud does not allow community nodes that make arbitrary
HTTP calls.
Credential
Space Atlas API takes two fields:
| Field | Value |
|---|---|
| API Key | A workspace key beginning wk_. Space Atlas → Settings → API keys. |
| Base URL | https://api.space-atlas.com (change it only for a self-hosted install). |
Press Test — it calls GET /v1/me, which needs no scope, so a read-only key still
tests green.
The key is scoped on the server: to its workspace, to the drives it was granted, and to
its write scopes. The node cannot widen any of that.
Operations
| Resource | Operation | Endpoint |
|---|---|---|
| Drive | List | GET /v1/drives |
| Folder | List | GET /v1/drives/:id/folders |
| Folder | Create | POST /v1/folders |
| Asset | List | GET /v1/folders/:id/assets or /v1/drives/:id/assets |
| Asset | Get | GET /v1/assets/:id |
| Asset | Get Download URL | GET /v1/assets/:id/download-url |
| Asset | Upload | three calls, below |
| Custom API Call | Request | any /v1 path |
Upload
Space Atlas takes no file bytes through its API — they go straight to storage. The node
does all three steps for you:
POST /v1/assets/upload-url— asks where to put itPUTto the returned presigned URL — sent with no Space Atlas credential, because
that URL is already signedPOST /v1/assets/register— the asset row only exists after this, and the server
checks the object is really there first
Feed it an item with binary data (for example from HTTP Request or Read Binary
File) and name the binary field. Renditions — thumbnails, proxies, HLS — are built
server-side afterwards; the node returns as soon as the asset exists.
Custom API Call
The API has ~103 /v1 routes and this node wraps eight of them. Everything else —
share links, saved views, snapshots, pages, analysis jobs, templates — is reachable with
Custom API Call: pick a method, give a path such as /v1/share-links, and the
credential is applied for you.
Notes
- List operations return one page. The response carries
next_cursor_page; feed it
back into Page to walk them. - The node returns the API's
datapayload as items, except for Custom API Call, which
returns the whole envelope — a custom route may not have adatakey.
Development
npm install
npm run build # tsc only; there is no asset step
npm run verify # dependency-free self-check
This package is deliberately not a workspace of the monorepo root, likeapps/media-services: it has its own node_modules and is published on its own.
Licence
MIT