Skip to content
Docs

Visual Builder & SDK

Interplay’s builder is a single visual canvas where a workflow is assembled from nodes, wired together, and deployed live. The same workflow can be authored visually, edited as code, or worked on both ways by different people on the same team — there is no separate “export to production” step, because the canvas is the runtime.

How do you build a flow in Interplay?

Section titled “How do you build a flow in Interplay?”

Drag nodes from the palette onto the canvas, connect their inputs and outputs, configure each node in a side panel, and deploy. The flow becomes live immediately. Node categories cover triggers and I/O, logic and control flow, parsers and transforms, storage and databases, GenAI and agents, enterprise services, messaging, commerce, analytics, blockchain, and hardware/IoT.

Can developers work in code instead of on the canvas?

Section titled “Can developers work in code instead of on the canvas?”

Yes. Interplay is a hybrid environment rather than a no-code silo:

  • Function nodes run JavaScript or Python inline inside a flow, with dedicated Python virtual-environment management and package installation from the editor.
  • New nodes can be authored directly, including from a plain-English description — see Custom Nodes & Extensibility.
  • Flows are JSON artifacts that can be imported, exported, diffed, reviewed, and committed to source control like any other code.
  • AgentOne, the built-in AI coding agent, edits that code alongside you.

Does Interplay have version control for flows?

Section titled “Does Interplay have version control for flows?”

Yes. Interplay provides flow-aware versioning: projects can be initialized as Git repositories, version history is browsable from the editor, and teams can switch between versions of a flow. Because flows are stored as structured JSON rather than opaque binaries, changes are reviewable and rollbacks are exact.

How are workflows organized?

Section titled “How are workflows organized?”

Projects group related flows, credentials, and assets into an isolated workspace, so one initiative can proceed without touching another. Pipelines chain flows into larger multi-stage processes with their own routes. Flows can be searched, grouped, tagged, commented, and documented in place — including generated architecture summaries and flow descriptions.

How does a flow become an API or an application?

Section titled “How does a flow become an API or an application?”

Any flow can expose an HTTP trigger and respond over HTTP, which turns it into a live API endpoint the moment it is deployed. Flows can also be triggered on a schedule, by inbound messages and webhooks, by file or mail streams, or from another flow. Interplay additionally ships chatbot widget nodes and dashboard/app templates so a workflow can be surfaced to end users directly. See API and automation.

Are there starting templates?

Section titled “Are there starting templates?”

Yes. Interplay ships a starter library of demo applications and flow templates — research agents, chat and dashboard apps, inventory and commerce examples, document-processing pipelines — that can be installed into a workspace and then modified. Teams can also save their own flows as reusable templates.

Sources and references

Section titled “Sources and references”