n8n Community Node for Autodesk APS Data Management

An unofficial, community-maintained n8n node for Autodesk Platform Services (APS) Data Management and Autodesk Construction Cloud (ACC) Docs.

It provides all read operations exposed by Autodesk's current APS Data Management TypeScript SDK, searchable hub/project selectors, 2-legged authentication, and ACC Docs upload/download workflows.

Unofficial community project

[!IMPORTANT]
This package is independently developed and maintained by the community. It is not an official Autodesk product, is not affiliated with or endorsed by Autodesk, and is not an official n8n node. Autodesk, Autodesk Construction Cloud, ACC, and APS are trademarks of Autodesk, Inc.

Package: n8n-nodes-community-autodesk-aps-data-management
npm publisher: mohamed.elnahla

Features

• All 29 get* methods in @aps_sdk/data-management 1.1.4.
• ACC-focused hub/project browsing; non-ACC projects are filtered out.
• Searchable From List selectors that display Autodesk names instead of IDs.
• By ID selector modes compatible with n8n expressions and upstream node output.
• Ordered multi-selection for hubs, projects, folders, items, versions, download/job IDs, and transfer fields.
• Output controls for full responses, data-only items, or user-mapped data fields.
• Encrypted n8n credentials for APS client ID and client secret.
• Short-lived 2-legged OAuth tokens generated at execution time.
• Optional ACC x-user-id context.
• Upload a new ACC Docs item or a new version from n8n binary data.
• Download a native ACC Docs version into n8n binary data.
• Autodesk's required direct-to-S3 multipart transfer flow for larger files.
• No standalone OSS bucket creation, listing, deletion, or generic object management.

Requirements

• Self-hosted n8n with community nodes enabled.
• Node.js 24 or later for local development and CI. The current n8n node tooling depends on isolated-vm 7, which requires Node.js 24+.
• An Autodesk APS application with client ID and client secret.
• The APS application provisioned in the target ACC account.
• Appropriate Docs permissions for the service account or selected user context.

This package uses Autodesk's official npm SDK as a runtime dependency. For that reason, it is intended for self-hosted n8n and is not eligible for n8n Cloud's dependency-free verified-node program.

Install in n8n

n8n Community Nodes interface

1. Open your self-hosted n8n instance.

2. Go to Settings → Community Nodes.

3. Select Install a community node.

4. Enter:

   n8n-nodes-community-autodesk-aps-data-management
   

5. Accept the community-node risk notice and install.

6. Restart n8n if your deployment does not reload community packages automatically.

npm/manual installation

From the directory used for n8n custom/community packages:

npm install n8n-nodes-community-autodesk-aps-data-management

Restart n8n after installation.

For Docker, make sure the package is installed in the persistent n8n data volume or included in your custom image. See docs/INSTALLATION.md for examples and troubleshooting.

Configure Autodesk authentication

1. Create an APS application in the Autodesk developer portal.
2. Provision the application as a custom integration for the relevant ACC account.
3. In n8n, create an Autodesk APS 2-Legged OAuth Community API credential.
4. Enter the APS Client ID and Client Secret.
5. Optionally enter Act as User ID to send the ACC x-user-id header.
6. Use Test credential.

n8n stores the credential encrypted and does not place the secret in workflow JSON. The node requests an access token when execution starts; it never stores an APS access token as a workflow parameter.

See docs/AUTHENTICATION.md for scopes, ACC provisioning, permissions, and troubleshooting.

Resource selection

Hub, project, folder, item/file, and version fields provide two modes:

• From List: searchable, with human-readable account/project names.
• By ID: accepts a literal Data Management ID or an expression such as {{$json.projectId}}.

To browse projects, choose an ACC hub first. When a project ID comes from another node, switch Project to By ID; the hub can remain empty for operations whose APS endpoint only requires a project ID.

New nodes use a lazy path browser. Choose the hub and project first, select a top-level folder, and continue through the subfolder fields only as deeply as needed. Each dropdown requests only the direct children of the preceding folder and loads additional APS pages on demand.

• Folder operations and Upload File use the deepest selected folder as their target.
• Item/file fields list only files in the selected folder.
• Version fields load versions only after a file is selected, showing the version number and creation date while storing the version ID.
• Upload File's optional Existing Item ID lists files in the selected destination folder so an existing file can be selected when creating a new version.
• Twenty-five optional subfolder levels are available, matching the Autodesk Docs product limit. Only the next applicable level is shown. By ID remains available for literal IDs and expressions.

By ID accepts both literal IDs and expressions such as {{$json.folderId}}, {{$json.itemId}}, or {{$json.versionId}}.

Existing version 1 node instances retain the original full-project browser. Upgrade the node version to use lazy browsing; saved IDs and expressions continue to execute unchanged.

Node version 3 adds native multi-select controls. Every selected list is processed in its saved order. A one-value list is broadcast across longer lists; when two lists both contain multiple values, their lengths must match and values are paired by index. This prevents unintended Cartesian products. Versions 1 and 2 keep their original scalar UI and execution behavior.

Only the first applicable subfolder selector is initially visible. Selecting a folder reveals the next level, and selecting that level reveals one more; the remaining supported levels stay hidden. When a dependent selector combines more than one hub, project, folder, or item context, its labels are prefixed as Hub › Project › Resource so identical names remain distinguishable. Each loaded choice carries its originating hub/project context through later selectors and execution, while APS API calls still receive the original Autodesk resource ID. Literal ID expressions remain supported.

Output controls

Every operation has three output modes:

• Return Full Response preserves the complete APS response and is the backward-compatible default.
• Return Only Data emits each resource in data as an individual n8n item, preserving APS order. Tree scans emit their ordered root tree entries.
• Select and Map Data Fields applies the configured mappings to every data resource. The source dropdown shows the common fields for the selected response type. Choosing an object field such as attributes or relationships reveals nested source fields one level at a time; custom dotted paths can also be added with Custom Data Field Mappings (JSON).

For example, {"fileName":"attributes.displayName","storage":"relationships.storage.data.id"} maps two nested APS values to fileName and storage. Output items remain paired to the incoming n8n item.

Operations

Hubs, projects, and downloads

• Get Hub
• Get Hubs
• Get Hub Projects
• Get Project
• Get Project Hub
• Get Project Top Folders
• Get Project Full Tree
• Get Download Details
• Get Download Job

Folders

• Get Folder
• Get Folder Contents
• Get Folder Parent
• Get Folder References
• Get Folder Relationship Links
• Get Folder Relationship References
• Search Folder

Items

• Get Item
• Get Item Parent Folder
• Get Item References
• Get Item Relationship Links
• Get Item Relationship References
• Get Item Tip
• Get Item Versions

Versions

• Get Version
• Get Version Download Formats
• Get Version Downloads
• Get Version Item
• Get Version References
• Get Version Relationship Links
• Get Version Relationship References

Binary file operations

• Upload File
• Download File

The complete parameter and response guide is in docs/OPERATIONS.md.

Upload files

The Upload File operation expects an n8n binary property, an ACC project ID, and a destination folder ID. n8n custom nodes do not display a local file picker: connect a node that produces binary data (for example, Read/Write Files from Disk, Form Trigger, or HTTP Request) and set Input Binary Property Name to its output property (usually data).

• Leave Existing Item ID empty to create a new item and its first version.
• Set Existing Item ID to create a new version of that item.
• Choose Project File for Project Files folders.
• Choose Plan Document for Plans folders.

The node creates an ACC storage placeholder, transfers the binary through Autodesk's signed-S3 flow, finalizes the upload, and creates the item/version relationship.

Although Autodesk's signed transfer URLs use /oss/v2/ endpoints, this node does not expose general OSS operations. Autodesk requires this transfer mechanism for ACC Data Management files.

Download files

Provide an ACC project ID and version ID. The node resolves the version's storage relationship, downloads the native file using a short-lived signed URL, and writes it to the configured n8n binary output field.

Additional SDK options

Read operations include Additional Options (JSON). The object is forwarded as SDK optional arguments together with the generated access token and optional x-user-id.

Example:

{
  "pageNumber": 0,
  "pageLimit": 100,
  "includePathInProject": true,
  "excludeDeleted": true
}

Only include options supported by the selected SDK method. See Autodesk's Data Management API reference and the installed SDK declarations.

Pagination and full-tree scans

Enable Load All Pages on Get Hub Projects, Get Folder Contents, Search Folder, or Get Item Versions to fetch pages until APS no longer returns a next-page link. The combined response deduplicates resources by type and ID and reports pagination.pagesLoaded.

On Get Folder Contents, enable Scan Full Folder Tree to traverse the selected folder and every descendant. Get Project Full Tree performs the same traversal for all accessible top-level project folders. Both return:

• tree: nested folders and files;
• folders and files: flat lists that are convenient in later n8n nodes;
• included: deduplicated included version resources from APS;
• summary: folder, file, and total counts.

Every tree node promotes id, type, name, path, depth, and parentId, and retains the complete original APS object in resource. Recursive scans always load every page and intentionally ignore content filters that could hide folders and make a branch incomplete.

Example workflow pattern

1. Get Hubs to discover connected ACC accounts.
2. Get Hub Projects to retrieve ACC projects.
3. Get Project Top Folders or Get Project Full Tree to find Project Files or Plans.
4. Get Folder Contents to navigate items and subfolders, optionally with a full-tree scan.
5. Pass returned IDs into later node instances using By ID expressions.
6. Use Upload File or Download File for binary transfer.

Security notes

• Never place the APS client secret in a normal workflow field.
• Use an n8n credential and restrict credential sharing to the required projects/users.
• Keep N8N_ENCRYPTION_KEY stable and protected in self-hosted deployments.
• Grant the APS integration only the ACC permissions it needs.
• Signed transfer URLs are deliberately short-lived and are not returned in normal node output.
• Do not commit .env files, n8n data directories, credentials, or npm tokens.

See SECURITY.md for vulnerability reporting.

Development

git clone https://github.com/mohamedelnahla/n8n-aps-datamanagement.git
cd n8n-aps-datamanagement
npm ci --ignore-scripts
npm run lint
npm test
npm run dev

Production build:

npm run build

See docs/DEVELOPMENT.md for architecture and release checks.

Publishing

Publishing is performed by .github/workflows/publish.yml when a version tag such as v0.1.0 is pushed. The workflow validates the tag/package version, runs lint and tests, and uses the official n8n release tooling to publish with an npm provenance statement.

The repository owner must create a GitHub Actions secret named NPM_TOKEN using an npm granular access token belonging to mohamed.elnahla. Full setup and release commands are in docs/PUBLISHING.md.

Support and contribution

• Bugs and feature requests: GitHub Issues
• Contribution guide: CONTRIBUTING.md
• Change history: CHANGELOG.md

Community support does not replace Autodesk or n8n commercial support.

License

MIT