Integrations

QuantaDuck Integrations

Connect timetables, messaging, admissions, CRM, HR, and learning platforms into one governed integration layer.

Solutions

Integration patterns and platform connectors—placeholder detail you can refine with live scope and APIs.

Moodle & Canvas (VLE)

Synchronise courses, enrolments, and assessment signals with your central data estate.

Details ▼

Problem: Learner activity is split across the VLE and MIS, slowing reporting and support.
Solution: Event-driven sync for cohorts, modules, and grades with conflict-safe reconciliation.
Outcome: One timeline of learner engagement for tutors and compliance teams.
Tech stack: LTI 1.3, REST APIs, webhooks, Azure/AWS queues

Microsoft Dynamics

Align recruitment, cases, and contracts with student and employer records.

Details ▼

Problem: CRM data does not match core student IDs, creating duplicate contacts and missed SLAs.
Solution: Golden-record mapping with scheduled delta loads and exception dashboards.
Outcome: Reliable handoffs between outreach, admissions, and delivery teams.
Tech stack: Dataverse, Power Automate, OAuth2, change data capture

Google Classroom

Bring Classroom rosters and coursework signals into institutional reporting.

Details ▼

Problem: Operational teams cannot see Classroom activity next to MIS or finance views.
Solution: Secure roster sync plus optional coursework metadata for analytics sandboxes.
Outcome: Faster intervention and clearer accountability for hybrid cohorts.
Tech stack: Google Workspace APIs, service accounts, least-privilege scopes

Microsoft Graph & Microsoft 365

Directory, mail, and Teams context wired to the right operational workflows.

Details ▼

Problem: Identity and collaboration signals sit outside line-of-business systems.
Solution: Graph-backed provisioning hooks and Teams deep links for case workflows.
Outcome: Fewer context switches and auditable actions tied to the right user.
Tech stack: Graph API, O365 connectors, conditional access aware clients

Active Directory

Authoritative identity and group membership for apps, VPN, and campus systems.

Details ▼

Problem: Stale groups and manual account lifecycle create security and support load.
Solution: HR-driven joiner–mover–leaver automation with rollback and attestations.
Outcome: Consistent access on day one and clean exits without drift.
Tech stack: Azure AD / Entra ID, LDAP, SCIM, privileged access reviews

Bespoke APIs, reporting & third parties

Custom connectors, governed exports, and partner platforms brought under one roof.

Details ▼

Problem: One-off spreadsheets and ad hoc APIs hide risk and duplicate effort.
Solution: Versioned integration contracts, observability, and reusable reporting packs.
Outcome: Repeatable delivery with measurable uptime and fewer fire drills.
Tech stack: OpenAPI, SQL/semantic layers, ELT, partner SFTP / webhooks

Timetable Web View and ICS Link

Publish authoritative timetables to the web and calendar apps staff and students already use.

Details ▼

Problem: Room and session changes are emailed as PDFs; personal calendars drift from the source of truth.
Solution: Web view with deep links plus signed ICS feeds scoped by role, cohort, and campus.
Outcome: Fewer clashes, fewer “which room?” tickets, and a single timetable narrative across devices.
Tech stack: HTTPS feeds, tokenised ICS URLs, cache headers, optional SAML-gated web view

Azure Service Bus

Reliable messaging between campus systems with retries, dead-lettering, and observability.

Details ▼

Problem: Point-to-point scripts break under load and lose messages when a downstream system is down.
Solution: Topics and queues with idempotent consumers, correlation IDs, and replay-safe handlers.
Outcome: Resilient integration fabric that scales with peak enrolment and clearing events.
Tech stack: Azure Service Bus, Managed Identity, Application Insights, .NET / Node workers

Azure File Storage

Secure, shared file drops and pick-up folders for batch integrations and evidence packs.

Details ▼

Problem: Partners email attachments or use ad hoc shares with no versioning, virus scan, or retention policy.
Solution: Managed file shares with SAS or Entra ID access, lifecycle tiers, and monitored landing zones.
Outcome: Predictable handoffs for ILR extracts, supplier files, and audit artefacts with full traceability.
Tech stack: Azure Files (SMB), private endpoints, Defender for Storage, automation triggers

Enroly

Connect admissions workflows, offers, and confirmations to your student record spine.

Details ▼

Problem: Offer data is re-keyed into the MIS, delaying enrolment and risking mismatched cohorts.
Solution: API-led sync for applicants, decisions, and deposit status with exception queues.
Outcome: Faster conversion tracking and accurate readiness lists for curriculum and finance.
Tech stack: Enroly APIs, webhooks, student ID mapping, secure vault for credentials

Student CRM

Unify recruitment, conversion, and retention touchpoints with canonical learner identity.

Details ▼

Problem: Teams run parallel spreadsheets; campaign responses do not tie back to the MIS.
Solution: Bidirectional sync for contacts, pipelines, and outcomes with governance on PII.
Outcome: One funnel view from first enquiry through to enrolled learner.
Tech stack: CRM REST/SOAP, bulk APIs, incremental sync, field-level audit

PS16

Align finance, employer, and learner data with your reporting and compliance layers.

Details ▼

Problem: ILR and funding outputs need consistent snapshots; manual exports miss last-minute changes.
Solution: Scheduled extracts and validated staging models aligned to your PS16 processes.
Outcome: Fewer return cycles and clearer sign-off between curriculum, finance, and data teams.
Tech stack: SQL views, file drops, validation rulesets, change tracking

Active Campaign

Automate journeys while keeping marketing consent and learner context accurate.

Details ▼

Problem: Campaign lists go stale the day after export; unsubscribes are not reflected centrally.
Solution: Segment sync from MIS/VLE signals with consent flags and suppression lists.
Outcome: Compliant outreach that respects programme, campus, and communication preferences.
Tech stack: Active Campaign API, tags, custom fields, webhook callbacks

Echo 360

Link lecture capture and analytics to modules, rooms, and attendance where policy allows.

Details ▼

Problem: Engagement data sits outside the LMS/MIS, so intervention is reactive and manual.
Solution: Course and roster alignment plus optional analytics exports to your warehouse.
Outcome: Tutors see participation signals next to progression data they already trust.
Tech stack: Echo 360 APIs/LTI, SSO, scheduled CSV/API extracts, role-based access

Zellis

Bridge payroll and people data with finance and HR reporting without duplicate entry.

Details ▼

Problem: Cost centres and contract changes are reconciled in spreadsheets at month end.
Solution: Controlled feeds for posts, cost allocation, and leaver events with reconciliation checks.
Outcome: Cleaner management accounts and faster answers to workforce questions.
Tech stack: Zellis exports/APIs where available, secure SFTP, validation dashboards

Bio Time

Bring time and attendance into workforce planning alongside teaching timetables.

Details ▼

Problem: Clocking data never meets room bookings or HR rosters in one place.
Solution: Normalised shift and attendance events with rules for sites, roles, and exceptions.
Outcome: Better cover decisions and auditable records for payroll handoff.
Tech stack: Bio Time interfaces, CSV/API ingestion, time-zone safe pipelines

Learning Curve

Keep skills pathways, completions, and compliance training visible to managers and HR.

Details ▼

Problem: Mandatory training completion is chased by email; evidence is scattered across systems.
Solution: Completion sync, deadline alerts, and dashboards tied to job roles and sites.
Outcome: Fewer overdue modules and a single evidence trail for audits.
Tech stack: LMS APIs, SCORM/xAPI where used, HR master data keys

HR

Connect core HR master data—roles, sites, contracts—to access and downstream apps.

Details ▼

Problem: Joiners and movers update HR first, but IT and teaching systems lag by days or weeks.
Solution: Event-driven HR feed with staged approvals and rollback for high-risk changes.
Outcome: Right access on day one and cleaner exits across Active Directory, CRM, and VLE.
Tech stack: HR system APIs/flat files, Entra ID / SCIM, workflow engine, audit logs

HubSpot

Bring your marketing automation and student recruitment data together.

Details ▼

Problem: Applications and student enquiries are tracked in HubSpot but do not sync seamlessly with the core MIS system.
Solution: Automated bidirectional sync between HubSpot and your MIS via API to ensure a single source of truth.
Outcome: Streamlined admissions processes and accurate tracking of learner journeys from enquiry to enrollment.
Tech stack: HubSpot API, OAuth, Webhooks, REST APIs