Draw workflows with vertices.
Polygon Designer lets you add vertices to a canvas, connect them into a workflow, and configure how signals move from one point to the next.
Every workflow starts with a vertex.
Stop wiring services together by hand.
Draw the workflow. Let vertices carry the signal. Node Vertex is not asking your team to think in terms of callback URLs, queue workers, backend controllers, retry plumbing, or brittle glue code.
Webhooks are what platforms invented because the web did not have programmable signal points. Node Vertex gives every signal a place to live.
Think in vertices: Listen to this vertex. When it changes, send the new value there.
What is a Polygon?
A polygon is a connected workflow of vertices. Vertices can represent forms, storage, transformations, emails, integrations, payments, listeners, static pages, files, AI actions, and live streams.
Vertex
An addressable signal, data, content, action, or state point.
Polygon
A workflow made from connected vertices.
Constellation
A group of polygons that powers a larger business process.
Canvas-based workflow design
Drag vertices onto a canvas.
Connect them visually with directed edges.
Configure each vertex from a side panel.
Save and activate the polygon.
Test a payload through the workflow.
View execution history and audit details.
Sales Intake Polygon
A business can create a sales intake automation without traditional glue code.
[Sales Page]
↓
[Sales Intake Form]
↓
[Sales Responses JSON Store]
↓
[Listener: On New Response]
↓
[Transform: JSON to HTML]
↓
[Email: Send Notification]sales -> form -> salesresponses -> listener -> transform -> email
A form submission can be stored, detected, transformed into HTML, and sent as an email.
Multiple connections
A vertex can fan out to multiple downstream steps. The first designer supports simple linear workflows, while the graph model supports multiple edges.
salesresponses ├── transform-to-email -> email-sales-team ├── transform-to-teams -> teams-sales-channel └── create-jira-ticket
Execution visibility
Every run is inspectable. See what completed, failed, or skipped.
Lead received ✅ Transformed to HTML ✅ Email sent ✅
The simplest way to connect anything to anything — static, dynamic, or live.
Every step is still a vertex. Every signal is addressable. Every workflow is inspectable.
Start with a Vertex