Integrations – n8n Integration

VNTANA offers a verified node for n8n that lets you connect your 3D asset pipeline to over 1,000 other apps and services, without writing code. This integration eliminates the need to build custom API logic, manage authentication tokens, or maintain HTTP plumbing. Connect VNTANA in minutes and turn every asset publish into a trigger for the rest of your tech stack.

n8n is a workflow automation platform used by teams to build AI agents and automations that connect tools across the business. With the VNTANA verified node, you can listen for events on the VNTANA Platform (such as an asset moving to Live Public) and orchestrate downstream actions across systems like Slack, Salesforce, Salsify, Shopify, Google Sheets, and hundreds of others, including any vision or image generation model your team uses. The VNTANA node handles the entire authentication flow, multi-step uploads, and tag management for you, so you can focus on what your workflow does rather than how it talks to VNTANA.

Version Support and Downloads

The VNTANA verified node is published to n8n’s community registry and works with both n8n Cloud and self-hosted n8n instances on version 1.x and above.

To install or view the source, visit the n8n integrations page for VNTANA.

Installation

n8n Cloud (recommended)

Because VNTANA is a verified node, it appears directly in the n8n node search. No separate installation screen is needed.

1. Sign in to your n8n Cloud workspace and open any workflow.
2. Click the + button to open the node search panel and search for VNTANA.
3. Select the VNTANA node and click Install when prompted. Installation takes about a minute.
4. Once installation completes, the VNTANA node is available in every workflow in your instance.

Self-Hosted Installation

On a self-hosted instance you can install the node from the UI:

1. Open your n8n instance and navigate to Settings > Community Nodes.
2. Click Install a community node.
3. In the package name field, enter n8n-nodes-vntana and click Install.

If you’re running n8n in Docker or on your own infrastructure, you can also install the node via npm:

npm install n8n-nodes-vntana

Restart your n8n instance after installation to pick up the new node.

Using the Node

Authentication

The VNTANA node uses your VNTANA API key for authentication. The node handles the full token refresh flow internally, so you’ll never need to manage refresh tokens, organization scopes, or session cookies manually.

To generate an API key, log in to the VNTANA platform in your browser:

1. Within VNTANA, click your user icon in the upper right corner and select Profile.
2. Open the Authentication Key tab.
3. Click Generate or Regenerate and copy the key to your clipboard.

 

In n8n, create a new credential of type VNTANA API. You will need your Organization Slug, Default Workspace UUID, and API Base URL. Paste your key into the Authentication Key field, fill in the remaining fields, and click Save. The node validates the credential against your VNTANA organization on save.

Note: Regenerate will invalidate any previously generated key, so only do this if you are not using the key elsewhere. Otherwise, just use the key you already have.

After your credential is saved, you can use it across any number of VNTANA nodes in any workflow.

Triggering Workflows from VNTANA

A trigger is the event that starts an n8n workflow. The VNTANA node uses webhooks to fire workflows when events happen on the platform. Supported trigger events include asset publishing, asset approval, asset deactivation, and more.

To set up a webhook-based trigger:

1. Add an n8n Webhook node to your workflow and copy its production URL.
2. In VNTANA, navigate to Manage Organization > Webhooks and create a new webhook.
3. Paste the n8n webhook URL, select the workspace(s) you want to monitor, and choose the events you’d like to subscribe to (for example, asset.published).
4. Save. The next time a matching event fires in VNTANA, your n8n workflow will run.

Most Common VNTANA Node Operations

The VNTANA node exposes 16 operations across the platform, organized by resource. The five most commonly used in production workflows are:

• Render: Download. Pulls all renders attached to an asset (top, front, side, etc.) as binary files, ready for downstream nodes.
• Render: Upload. Uploads a new render to an asset’s Renders tab. Handles signed URL generation, file upload, and metadata in a single step.
• Product: Get / Update. Retrieves or updates asset metadata, tags, attributes, and review state.
• Tag: Create / Search. Creates or finds tags by name within a workspace, with built-in handling for the find-or-create pattern.
• Attachment: Upload / Download. Manages files attached to assets, including support files and supplementary media.

Each operation accepts standard n8n expressions for dynamic input. For example, the expression pulling the asset UUID from a triggering webhook is {{ $(‘Webhook’).first().json.body.product.uuid }}.

Full Operation Reference

Resource	Operation	Description
Product	Get	Retrieve a single asset by UUID
Product	Search	Search assets by name, tags, or metadata
Product	Create	Create a new asset
Product	Update	Update an asset’s metadata, tags, or review state
Product	Delete	Permanently delete an asset
Render	Download	Download one or all renders attached to an asset
Render	Upload	Upload a new render to an asset
Tag	Create	Create a new tag in a workspace
Tag	Search	Find tags by name
Tag	Get	Retrieve a single tag by UUID
Tag	Delete	Remove a tag from a workspace
Attachment	Upload	Upload a file attachment to an asset
Attachment	Download	Download a file attachment
Attachment	Search	List attachments on an asset
Webhook	Verify Signature	Validate the HMAC signature on an incoming webhook payload
Workspace	List	Retrieve all workspaces in your organization

Ready-Made Workflow Templates

You don’t have to start from a blank canvas. We publish ready-to-use templates to the n8n community gallery. Each one imports in a single click, includes step-by-step setup notes directly on the canvas, and only needs your credentials to run.

Browse all of them on our n8n creator profile.

Available now:

• Rules-based showroom automation. Encode your merchandising rules into the assets themselves: a Style attribute plus a STYLE_COLORNAME file naming convention. When assets are added to a showroom, the workflow groups them by style, sorts each group by color code, updates the showroom in place, and returns a CSV receipt. No spreadsheet, no manual curation.
• AI renders plus automatic tagging. The full pipeline: studio re-renders plus AI-generated product tags (material, color, style, use case) created and written back to the asset automatically. Search and merchandising metadata, populated the moment an asset publishes.
• Update VNTANA product attributes from scheduled Excel attachments. Drop a spreadsheet onto an asset and its metadata updates itself. The workflow polls for newly uploaded attachment files, parses them, and writes the attributes onto the product.

Other templates:

1. AI studio re-renders on publish. The moment an asset goes live, its platform renders are re-imagined by an image generation model using a brand-consistent style prompt, then uploaded back to the asset’s Renders tab. Geometry, proportions, and framing are preserved exactly.
2. Slack notifications with render previews. Post every newly published asset to a team channel with the studio render, AI tags, polygon count, and a one-click link to the asset in VNTANA. No more “is this ready?” pings.
3. Send tagged models to Figurement or  Blender for material editing. Tag an asset “Figurement” and publish. The workflow downloads the GLB and imports it into a Figurement scene for material editing and review. The tag is your routing switch: add it to send a model downstream, leave it off to skip.

 

These are starting points. Once VNTANA is wired into n8n, any tool n8n supports (from your CRM to your data warehouse to a custom Python script) becomes a downstream destination for your 3D content. Other patterns we’ve seen teams build include syndicating assets to Salsify, Shopify, Akeneo, and DAM systems in parallel, and running automated brand QA on renders before an asset ships.

Settings and Customization

The VNTANA node respects your workspace and organization scope automatically based on the credential you provide. Most operations expose the same fields you’d see in the VNTANA platform UI, including:

• Workspace UUID. Scopes the operation to a specific workspace within your organization.
• Product UUID. Identifies the asset to operate on. Can be hardcoded for testing or pulled from a webhook payload at runtime.