Visual Flows
A planned node-based editor built around typed inputs, outputs, and validated connections.
CampusLayer Sync · Planned
Build workflows between the applications your school uses.
Sync is the planned automation engine for cross-system work. Its Flows editor will let authorized teams define triggers, conditions, transformations, approvals, and actions without scripting every provider API.
Who it is for
Educators and IT teams who need repeatable, policy-controlled processes across applications.
Durable execution
Backend runs with logging, retries, conflict detection, and preflight checks. The editor will not be the execution engine.
Selective synchronization
Start with one-way and bounded workflows. Two-way sync requires explicit source authority and conflict policies.
How it fits into CampusLayer
- STEP 1Connect providers and register the operations they actually support.
- STEP 2Design and review a versioned Flow, including approval steps where needed.
- STEP 3Execute on the server with authorization rechecked, audit history, and clear failures.
Current scope and safeguards
Sync, the React Flow editor, and general cross-provider automation are roadmap capabilities, not live public services. Two-way synchronization will require additional provider support, institutional approval, and loop/conflict controls.
All access is subject to provider permissions and institutional approval. Review our student privacy disclosure.