Core concepts
A few ideas underpin everything in OrchaSync. Once these click, the rest of the product is straightforward.
How things are organized
OrchaSync is structured as a simple hierarchy:
| Concept | What it is |
|---|---|
| Company | Your organization. Everything belongs to a company, and your team members share it. |
| Workspace | A container for related work inside a company. You can have several — for example, one per brand or environment. |
| Workflow | A single automation: the thing you build on the canvas. A workspace holds many workflows. |
| Version | A saved snapshot of a workflow. Each time you save, you create a new version, so you always have history. |
| Run | One execution of a workflow. Every run records what happened, step by step. |
In short: a company has workspaces, a workspace has workflows, each workflow is saved as versions and executed as runs.
Workflows and nodes
A workflow is built from nodes connected on a canvas. Each node is one step — start, transform, decide, call an external system, finish. Data flows along the connections from one node to the next.
See the Nodes overview for how nodes work and what each one does.
Connections
A connection stores the credentials for an external platform (like NetSuite or WooCommerce) so your workflows can act on it without ever embedding secrets in the workflow itself. You set a connection up once and reuse it across workflows.
See Connections.
Runs and the audit trail
When a workflow runs, OrchaSync records a run with a step-by-step log. You can watch this live while testing, or review it afterward. This is how you answer "what ran, when, and why did it fail?" — covered in Running & monitoring.
Workflows run asynchronously — a trigger starts a run, and OrchaSync works through it in the background. You don't have to keep a browser tab open for a workflow to finish.