Novaza Flow#
Novaza Flow is the automation engine built into the Novaza platform. It lets you design, schedule, and run multi-step workflows — from simple data transformations to complex integrations across Office, Desk, Pulse, and external APIs — without writing infrastructure code.
Flow workflows run on Novaza’s managed compute layer. Enterprise plans support dedicated execution environments for isolation and compliance requirements.
What You Can Automate#
| Category | Examples |
|---|---|
| Data pipelines | Sync patient records from HIS, transform and load into Office modules |
| Notification workflows | Trigger Pulse campaigns when Office records meet criteria |
| Integrations | Push events to external APIs (ERP, CRM, billing) on record changes |
| Scheduled jobs | Generate reports, archive data, send digests on a cron schedule |
| AI tasks | Run classification, summarization, or extraction steps on incoming data |
Core Concepts#
Scripts#
A Flow script is a unit of logic — a function written in TypeScript or Python that receives inputs and returns outputs. Scripts are versioned, testable, and reusable across workflows.
Workflows#
A workflow chains scripts together into a directed graph. Each step receives the output of the previous step. Branching, parallel execution, and error handling are first-class constructs.
Triggers#
Workflows start from a trigger:
- Schedule — cron expression (e.g., every day at 06:00 UTC)
- Webhook — HTTP call from an external system or Office automation
- Office event — a record is created, updated, or deleted in an Office module
- Manual — run on demand from the Flow dashboard
Resources#
Resources are named credentials or configuration objects (database connections, API keys, SMTP settings) stored securely in Flow and injected into scripts at runtime. Credentials are never exposed in script code.
Accessing Flow#
Flow is available to Professional and Enterprise plan customers.
- Web UI: flow.novaza.ai
- Single Sign-On: log in with your Novaza account — no separate credentials required
- API: Flow exposes a REST API for triggering workflows and querying run history (see Middleware API for the
/med/flow/*endpoints)
Getting Started#
- Log in at flow.novaza.ai with your Novaza SSO account
- Navigate to Scripts → create your first script
- Navigate to Workflows → create a workflow and add your script as a step
- Add a trigger (schedule or webhook) and deploy
- Monitor runs in the Runs tab — view logs, inputs, and outputs per step
Limits by Plan#
| Feature | Professional | Enterprise |
|---|---|---|
| Concurrent workflow runs | 10 | Unlimited |
| Script execution timeout | 30 seconds | Configurable |
| Dedicated execution environment | — | ✅ |
| Private workspace isolation | — | ✅ |
| Audit log retention | 30 days | 1 year |
Related#
- Middleware API — Flow endpoints
- Office Workflows — for record-level automation within Office modules