Skip to content
Docs

Custom Nodes & Extensibility

Interplay’s node palette is not a fixed list. Anything the platform does not already integrate with can be added — generated from a description, installed from a registry, or written by hand — and once installed a custom node behaves exactly like a built-in one.

Yes. Describe the node you need in plain English and Interplay drafts, generates, and deploys it directly into your palette, ready to drag onto a canvas. This is the fastest route to a connector for an internal or niche API: instead of scaffolding a node package by hand, you describe the endpoint and the shape of the data you want out.

Three routes, all from the editor:

  • Node registry — browse and install from a curated registry of published nodes; missing dependencies for an imported flow can be resolved in one action.
  • npm — search npm for community node packages and install a chosen version.
  • Upload — install a node package directly into the workspace.

Installed nodes can be pinned to specific versions and uninstalled cleanly.

Yes. Nodes are standard packages with a runtime file and an editor definition, so a developer can author one in JavaScript, or wrap Python logic through the Python function node. In-flow function nodes cover the common case where a few lines of custom logic are needed without publishing a reusable node at all — with Python virtual-environment creation and package installation available from the editor’s library tab.

  • Databases — MySQL, PostgreSQL, and MongoDB can be provisioned and connected from the platform, with a built-in database browser for inspecting data.
  • Templates and starter apps — bundled demo applications can be installed, modified, and re-saved as your own templates.
  • Workflow import — flows and mappings can be converted in from other automation tools, so existing automations can be brought onto the platform rather than rebuilt from zero.
  • Chat and dashboard surfaces — chatbot widgets and dashboard apps let a flow be published to end users without a separate front-end project.