Template Export & DRM

Introduction

The nLink ecosystem is designed not just for internal automation, but as a platform where creators can build, share, and monetize powerful automations. With the Template Export feature, you can package your entire workflow (including logic, custom nodes, and credentials structure) into a single .json file.

Exporting Workflows & Virtual Nodes

• Workflow Export
  From the Visual Debugger, click the Options menu (three dots) and select Download. This will generate a standalone .json file representing your workflow.
• Virtual Node Export
  If you have designed a complex sub-workflow, you can package it into a single Virtual Node. Right-click the selected nodes and choose Export Graph Node.

Soft DRM Protection

To protect template creators from piracy (unauthorized sharing and reselling of premium templates), nLink introduces Soft DRM (Digital Rights Management).

When a workflow is DRM-protected, end-users who import your workflow can fully utilize it—they can run it, edit it, and connect their own credentials. However, the system permanently blocks them from exporting, downloading, or duplicating the template.

How to Enable DRM for your Template

Currently, DRM is enabled by injecting a specific flag into your Workflow's JSON settings before distributing it.

{
  "name": "My Premium Chatbot Template",
  "nodes": [ ... ],
  "connections": { ... },
  "settings": {
    "save_execution_log": "all",
    "is_drm_protected": true
  }
}

By adding "is_drm_protected": true to the settings block of your exported JSON, the DRM lock will automatically and permanently activate when a customer imports the file into their nLink workspace.

Security Hardening

• Immutable Lock: Once a workflow is imported with DRM enabled, the lock is permanent. End-users cannot bypass the lock by updating the workflow settings via the UI or API.
• Export Prevention: All export APIs (GET /workflow/export, POST /workflow/export-node) will immediately reject requests for DRM-protected workflows with an ERR_PERMISSION_DENIED error.
• UI Restrictions: The Frontend Dashboard intelligently hides the "Download", "Duplicate", and "Export Node" buttons for DRM-protected workflows.

Best Practices for Creators

• Always use the Credential Builder to require users to input their own API Keys. Never hardcode your personal API keys inside the nodes before exporting.
• For maximum security, combine Workflow logic with custom WASM Nodes for proprietary algorithms. Since WASM code is compiled into binaries, your intellectual property remains fully secure.