Skip to main content
Edurie’s integrations let you connect your school to the tools your staff and students already use. Once connected, Edurie automatically keeps rosters, calendars, grades, and communication spaces in sync with your external provider — reducing manual data entry and keeping every platform consistent. You manage all integrations from the Apps & Integrations section of your admin panel.

Supported integrations

Google Workspace

Sync classes, rosters, and grades to Google Classroom; create Calendar events, Meet links, Chat spaces, and school-issued Gmail accounts.

Microsoft 365

Connect your Azure AD tenant to sync class data to Microsoft Teams, Outlook calendars, and OneDrive folders.

Finding and installing integrations

All integrations are managed at the school level. Each school in your Edurie tenant has its own independent set of connected apps.
  1. Sign in to the Edurie admin panel and select your school.
  2. Navigate to Apps & Integrations in the left sidebar.
  3. Select the integration you want to install and click Connect.
  4. Follow the OAuth authorization flow or enter credentials as prompted.
Once connected, the integration tile shows a Connected status badge. You can return to this page at any time to update settings, pause syncing, or disconnect the integration entirely.

Core concepts

Understanding these concepts will help you get the most out of Edurie’s integrations and troubleshoot problems quickly.

Sync

A sync is the process of pushing Edurie data to an external provider, or pulling external changes back into Edurie. Syncs can be triggered in two ways:
  • Automatic — Edurie triggers a sync whenever relevant data changes. For example, enrolling a student in a class automatically adds them to the corresponding Google Classroom course or Microsoft Teams channel.
  • Manual — You can trigger a sync at any time by clicking the Sync button on an individual class page or from the integration settings.
Sync operations are queued and processed asynchronously. Most syncs complete within a few seconds, but larger rosters may take a moment longer.

Sync logs

Every sync operation is recorded in the integration’s sync log. Use sync logs to verify that data has been pushed successfully or to diagnose failures.
If a sync fails, you can retry it directly from the sync log without re-triggering the full sync flow. Navigate to Apps & Integrations → [Provider] → Sync Logs and click Retry on the failed entry.
Each log entry includes:
FieldDescription
ActionThe operation that was attempted (e.g., google_classroom.roster.student.add)
Statuspending, success, failed, or skipped
TimestampWhen the operation ran
DetailsProvider response or error message

Sync conflicts

A conflict occurs when data in Edurie and the external provider diverge in a way that Edurie cannot automatically resolve. For example, if a teacher’s name is changed directly in Google Workspace after it was synced from Edurie, a conflict is created so you can decide which version should be the source of truth. When a conflict is created, it appears in Apps & Integrations → [Provider] → Conflicts. Each conflict offers three resolution options:
  • Accept external — Keep the provider’s version and update Edurie to match.
  • Push local — Overwrite the provider’s version with Edurie’s data.
  • Ignore — Dismiss the conflict without making any changes.
Unresolved conflicts do not block syncing, but they do indicate a data mismatch. Review conflicts regularly to keep your systems consistent.

Webhooks

Edurie can receive real-time event notifications from providers via webhooks. When a provider sends a webhook, Edurie processes it and applies any relevant changes automatically. Webhook signatures are validated on every incoming request, and Edurie rejects requests with invalid or missing signatures.

Integration status

An integration can be in one of four states:
StatusMeaning
ConnectedThe integration is active and syncing normally.
DegradedSyncs are partially failing — some operations succeed, others do not.
ErrorAll recent syncs have failed. Credentials may have expired or been revoked.
DisconnectedThe integration has been disconnected. No syncs will run.
If your integration enters an Error state, reconnect it from Apps & Integrations to restore access.