iSSupported integration
iSAMS
Use agreed student or staff data to start admissions, contract or HR workflows, then return completed documents and status to the corresponding record.
- Typical exchange
- Student / staff data ↔ documents + status
Integrations
An integration is more than a logo.
For every connection, you should know what information moves, in which direction, what triggers it, who configures it and how exceptions are handled.
Explore connectionsConnection recordScoped before build
System of record
SIS · HRMS · CRM · ERP
Trusted source fieldsInto ZegalEvent + agreed fields→
Back to sourceStatus + record reference←
Governed workflow
Zegal
Rules · approvals · documents- Trigger
- Event or schedule
- Direction
- In, out or both
- Fields
- Defined in scope
- Exceptions
- Named owner
Integration catalogue
Connect the systems your teams already use.
These cards describe common connection patterns. The visible status labels distinguish a supported integration from a scoped build or an API or file exchange. Exact fields, direction and write-back are confirmed for each implementation.
01
School & admissions systems
Use agreed student, family, staff, enquiry and admissions data in governed school workflows.
PSCustomer-specific integration
PowerSchool
Use agreed student or enrolment fields to trigger school workflows, support bulk re-enrolment and return completed documents to the student record.
- Typical exchange
- Student events ↔ workflow records
VCustomer-specific integration
Veracross
Use agreed household, admissions and enrolment data in school workflows, with checklist or document write-back defined in scope.
- Typical exchange
- Admissions data ↔ checklist / files
OACustomer-specific integration
OpenApply
Connect agreed applicant and family data to admission, offer and re-enrolment workflows, with fields and write-back confirmed for the school.
- Typical exchange
- Applicant data ↔ documents + status
WAPI or file-based connection
Wonde
Use permissioned student, family or staff data through Wonde to populate school workflows, with available fields and school access scoped for implementation.
- Typical exchange
- Approved MIS data → workflow fields
02
CRM & ERP
Connect customer, deal and finance records to agreement and operational workflows.
FCustomer-specific integration
Funnel
Use agreed enquiry, family or admissions-stage data to start document workflows, with CRM write-back defined during implementation.
- Typical exchange
- Prospect / stage data ↔ workflow status
HCustomer-specific integration
HubSpot
Use agreed Deal fields or configurable stage changes to start agreement workflows and return completion status to the CRM.
- Typical exchange
- Deal data ↔ agreement status
D365Customer-specific integration
Dynamics 365
Map agreed Account, Contact or Opportunity fields into agreement workflows and return completion status or activity.
- Typical exchange
- CRM data ↔ workflow outcome
NSCustomer-specific integration
NetSuite
Use approved customer, vendor or transaction data to start agreement workflows and connect completed records to downstream ERP steps.
- Typical exchange
- ERP data ↔ completed record
03
Finance & payments
Turn completed agreements and trip decisions into controlled finance actions.
XeSupported integration
Xero
Link Xero to Zegal so values from a completed, Xero-enabled document can create an invoice record without re-entering the same data.
- Typical exchange
- Completed document values → invoice
SSupported integration
Stripe
In Zegal Guard trip workflows, collect and track a payment through Stripe Connect alongside the attendee’s parental and payment consent.
- Typical exchange
- Trip payment status → attendee record
04
Document storage
File completed records into the document structures your organisation already governs.
GDCustomer-specific integration
Google Drive
File completed documents to agreed folders using the naming and record references defined for the workflow.
- Typical exchange
- Completed documents → folders
SPCustomer-specific integration
SharePoint
Route completed files to agreed sites and libraries and map the metadata fields needed for governed archiving.
- Typical exchange
- Files + metadata → libraries
05
Spreadsheet workflows
Turn mapped rows and calculated values into controlled, repeatable document work.
GSAPI or file-based connection
Google Sheets
Use mapped rows to start bulk document workflows and return agreed document IDs or completion status to the sheet.
- Typical exchange
- Mapped rows ↔ document status
XAPI or file-based connection
Microsoft Excel
Use uploaded rows and calculated fields for fees, discounts or clause logic, then map approved values into document generation.
- Typical exchange
- Calculated rows → document suites
Clear availability
See the real status of every connection.
A connection built for one customer is not automatically a productised integration. Zegal distinguishes what is supported, customer-specific, and available through an API or file exchange.
Supported integration
Productised, currently available and supported.
Customer-specific integration
Deployed in a defined context; scope confirmed during discovery.
API or file-based connection
Feasibility and implementation scope agreed with the customer.
Bring us your current architecture and one target workflow.
We'll map the systems, data movement, responsibilities and implementation dependencies with you.