One set of trustworthy data
The same record across systems, with less administrative work
Home / Solutions / Integration Hub
The connectors we have built and run for colleges: Moodle, Salesforce, Zoho, Celcat, finance, Microsoft 365, Google Workspace, payments and AI. Pick the ones you need, and if one is missing, we build it.
Not tied to a vendorDocumented and monitoredInnealla or your SIS
Purpose-built for education
Admissions, enrolment, learning, attendance, finance and communications kept in sync automatically, replacing manual data entry, spreadsheets and fragile point-to-point links. Each connector is switched on per college from inside Innealla.
The same record across systems, with less administrative work
Least-privilege access, and every call logged
Because the connector usually already exists
Why it works
The student record sits at the centre, whether that is Innealla or the SIS you already have.

01
A connector built for one college becomes available to every other college on the hub. Innealla, Moodle, Salesforce and Zoho all plug into the same place, so a new institution gets the catalogue on day one rather than a fresh integration project.
02
Legacy databases, proprietary systems, undocumented APIs and hybrid on-premise and cloud environments. If a system holds data, we can connect it securely and reliably, extending the life of what you have while enabling automated workflows.
03
The hub exposes Moodle, Salesforce, student records and this website to AI assistants through connectors we wrote, with a key per person, named tools instead of database logins, and every call logged.
See how we use it ourselves →The catalogue
Each connector is documented, monitored and supportable by someone other than the person who built it, with least-privilege access and every call logged.
Courses, cohorts and enrolments provisioned from the curriculum; grades and announcements kept in step
Multi-tenant Moodle estates for several schools or brands
Student information systems connected to Moodle and other VLEs
Leads, applications and cases into the student record without re-keying
Enquiries, applications and cases into the student record
Leads and applications flowing into the student record
Applications import
SUSI grants and HEA SRS returns
Exports prepared by the system
The monthly reporting international students need
To Navision, Microsoft Dynamics and other accounts systems
Online payments, payment links and instalment plans
Invoices to sponsors against the student account
Identity, email and calendars; student accounts created in Microsoft 365
Identity, email and calendars; staff sign-in
Staff sign-in with your existing identity provider
Timetable and attendance synchronised with student records, or a one-off import into Innealla for cutover
Attendance tied to timetables and student records
Email and SMS connected to the student record
Website enquiry and application forms feeding the CRM and the student record
Service desks connected to student data
An assistant that can use Moodle within each user’s permissions
Exposed to AI assistants with a key per person and every call logged
Missing a system? We build connectors for a living. If one is missing, we add it to the hub, and it is then available to every college.
Book an Integration Review →What we connect
A typical college runs systems from different suppliers and different decades. Staff re-key data between them, and students have to know which system holds what. These are the links we build most often.
How we build integrations
Ours are built so that is never the case.
We love API environments and the challenge of integration
If a system holds data, we can connect it securely and reliably, extending the life of what you have.
“Inneall are very solutions driven. They find better ways of doing things. I can throw an idea at them and they’ll find a way to do it.”
Case study
Moodle, attendance, payments and Salesforce working across one estate.
Start here
Two weeks, fixed price. You get a map of what you have and a plan you can act on, with us or without us.
FAQ
Two weeks, a fixed price, and a map of every integration you need, ranked by value and effort.

One hub, with a connector for each system a college runs. Each one is documented, monitored and supportable by someone other than the person who built it, with least-privilege access and every call logged.
A connector built for one college becomes available to every other college on the hub. Innealla, Moodle, Salesforce and Zoho all plug into the same place, so a new institution gets the catalogue on day one rather than a fresh integration project.
Designed for colleges and training providers: admissions, enrolment, learning, attendance, finance and communications kept in sync automatically, replacing manual data entry, spreadsheets and fragile point-to-point links.
The hub exposes Moodle, Salesforce, student records and this website to AI assistants through connectors we wrote, with a key per person, named tools instead of database logins, and every call logged. See how we use it ourselves.
Legacy databases, proprietary systems, undocumented APIs and hybrid on-premise and cloud environments. If a system holds data, we can connect it securely and reliably, extending the life of what you have while enabling automated workflows. We have integrated systems others refused to touch.
One set of trustworthy data across systems, less administrative work, stronger compliance and reporting, and faster delivery because the connector already exists. Start with a two-week Integration Review: every system and interface mapped, with the fixes ranked by value and effort.