Connect everything you run: govern it as one
100+ ready connectors, plus an HTTP connector and webhooks for everything else. Your systems stay exactly where they are: what changes is that every connection passes through explicit permissions, and every action lands in the audit trail.
One hub, an orbit of systems
No rip-and-replace, no migration: NOVA sits in the middle and your systems stay on their orbit: the order meets the inventory, the invoice meets the ledger, the customer meets the reply.
A sample of 100+ ready connectors: the live catalogue sits inside the dashboard.
Every connection by explicit permission
An ungoverned integration is a back door. In NOVA, a connector sees only what you allowed: source by source, role by role.
Access limited to the fields actually needed: no open access "just in case."
Payouts, deletions and bulk sends pause at an authorized human before executing.
Who acted, what they did, when, and under which permission: recorded and reviewable anytime.
| Support agent | Sales agent | Reports analyst | |
|---|---|---|---|
| WhatsApp Business | Allowed | With approval | Denied |
| ERP system | With approval | Denied | Allowed |
| CRM system | Allowed | Allowed | With approval |
| Operations database | Denied | Denied | With approval |
No connector? Open it with the API
Call any endpoint, receive any event: the HTTP connector and webhooks bring your internal systems: even the legacy ones: into the same flow, under the same governance.
# Receive any event: register a webhook as a flow trigger $ curl -X POST https://api.novasyc.com/v1/hooks \ -H "Authorization: Bearer $NOVA_API_KEY" \ -d '{ "flow": "order-sync", "event": "invoice.created" }' ✓ hook registered · id: whk_8f3k2 ✓ scope: flows:order-sync · audit log: enabled
# Run a flow with one call: scoped to this key's permissions only POST /v1/flows/leave-approval/runs Host: api.novasyc.com Authorization: Bearer $NOVA_API_KEY Content-Type: application/json { "input": { "employee_ref": "EMP-4821", "days": 3 } }
// Every run emits an audit event: who, what, when, under which permission { "run_id": "run_01J9K4QH", "flow": "leave-approval", "actor": "api_key:integrations-team", "scopes": ["flows:run", "hr:read"], "status": "completed", "approved_by": "[email protected]", "region": "ksa-central" }
Illustrative examples of the API pattern: full documentation lives inside the dashboard.
The connectors, by category
Representative categories of what NOVA connects today: each with a governance rule that matches its sensitivity.
| Category | Examples | Governance note |
|---|---|---|
| Communication channels | WhatsApp Business · Telegram · Slack · Teams · Gmail | Every outbound message passes the channel's permissions and lands in the audit trail. |
| Business & resource systems (ERP) | SAP · Oracle · Odoo | Access limited to required fields; sensitive financial actions require human approval. |
| Sales & customer systems (CRM) | Salesforce · HubSpot · Zoho | Separate read and write permissions per flow: never one key for everyone. |
| Productivity & documents | Microsoft 365 · Google Sheets | Access scope is pinned to the specific files and folders involved. |
| Databases | PostgreSQL and more | Queries run under restricted read roles by default; writes are an explicit decision. |
| Internal & custom systems | HTTP connector & webhooks: custom ERP connectivity on the Enterprise plan | Same governance: explicit permissions and an audit trail for every action. |
Integration questions
The HTTP connector and webhooks open any system with an API: including your legacy internal ones: call any endpoint, receive any event, and drop it into a flow like any ready connector. If you need deeper connectivity: such as custom ERP landscapes: custom ERP and internal-system connectivity is part of the Enterprise plan under a custom agreement.
Every connection gets explicit permissions at the action and data level: a flow reaches only the fields it actually needs, sensitive actions pause for human approval before executing, and every action lands in a complete audit trail: who acted, what they did, when, and under which permission. No open access, no keys that roam without limits.
Wherever you decide. On NOVA Cloud, data is processed in Saudi data centers by default. If it must never leave your infrastructure, NOVA runs inside your own private cloud (VPC) or fully on-premises in your data center: including completely air-gapped environments. Full details on the deployment & sovereignty page.
From connector to operation
Workflows
A connector alone is worth nothing: here it becomes a complete, observable operation.
Explore workflowsDeployment & sovereignty
In-Kingdom cloud, your own VPC, or air-gapped on-prem: your data lives where you decide.
Deployment optionsAI workflow automation
What do these integrations actually do in your working day? The full solution, from the team's point of view.
Explore the solutionTrust Center
The security model, personal data protection, and how we handle security reviews.
Enter the Trust CenterConnect your first system today.
Book a live demo where we put your own systems on the canvas: or start free and activate your first connector in minutes.