Integrations

Sparks provides all backend components – or you connect what you already run: from full sovereignty and your Matrix backend to hybrid with Microsoft 365 or your own Exchange and SharePoint. Word, Excel and Outlook can stay on the desktop – Sparks brings chat, video, calendar and AI together in one interface, usually without migrating data.

Or connect your existing backends:

Sparks Cloud calendar

Available

Native EU calendar in Postgres – recurring events, attendees, public web RSVP for guests, ICS export, and migration wizard. Optional instead of or alongside Exchange/Nextcloud.

Postgres calendar (EU)Public web RSVPICS exportRecurring events (RRULE)Calendar migration
Setup time: Included (SMB+)

Exchange SE & SharePoint Server

Available

Exchange Server/SE via EWS and SharePoint Server on-prem – calendar, files, identity (Entra ID, AD FS). Parallel with M365 supported.

EWS calendar (Exchange SE)SharePoint Server (REST)Entra ID / AD FS / IdP
Setup time: Individual

Microsoft 365

Available

Calendar from Exchange, tasks from Planner, files from SharePoint & OneDrive, MS Teams chat connection.

Exchange calendarSharePoint filesMS Teams chatPlanner tasksOneDrive
Setup time: ~ 5 minutes

Google Workspace

Available

Google Calendar, Google Drive files and Google Contacts – connected via OAuth, no data migration.

Google CalendarGoogle DriveGoogle ContactsGmail calendar invites
Setup time: ~ 2 minutes

Nextcloud / openDesk

Available

Nextcloud calendar (CalDAV), files (WebDAV), Nextcloud Talk bridge. Full openDesk compatibility.

CalDAV calendarWebDAV filesNextcloud Talk bridgeopenDesk compatible
Setup time: ~ 3 minutes

Open-Xchange

Available

OX App Suite calendar (CalDAV) and contacts (CardDAV) – ideal for hosted Exchange alternatives.

CalDAV calendarCardDAV contactsOX Drive (coming soon)
Setup time: ~ 3 minutes

Matrix server

Available

An existing Matrix server can be reused. Any compatible Matrix server works – e.g. Synapse, Tuwunel, Dendrite, Conduit. Optional: connect your own LiveKit for video.

Your own homeserverSynapse, Tuwunel, Dendrite, ConduitOptional: your own LiveKit
Setup time: Individual

Cisco Jabber

Enterprise

Click-to-IM and click-to-call into the installed Jabber client – org-controlled deep links, no chat bridge.

Click-to-IMClick-to-CallOrg controlDesktop & web
Setup time: Org flag
Office Add-in

Sparks inside Outlook

If Outlook remains your mail and calendar client, you can schedule Sparks online meetings without switching apps: the Sparks Outlook add-in (Office.js) extends Outlook desktop, Outlook on the web, and New Outlook for Windows – similar to the “Teams meeting” button.

Available as an Office add-in (React + Office.js). The meeting button and calendar task pane are implemented; create appointment from email, dual-write to the Sparks Cloud calendar, and RSVP sync are in progress.

What the add-in does today

  • Sparks meeting in appointments

    When composing an Outlook appointment, the “Sparks meeting” button inserts a join link, meeting ID, and invitation block – including meeting options (lobby, E2EE, etc., depending on plan).

  • Sparks calendar task pane

    The ribbon opens a compact Sparks calendar panel: view events and manage Sparks appointments without leaving Outlook.

  • Connected to Sparks backends

    Authentication via Entra SSO or Keycloak; appointments and online meetings use the Sparks account API and appointment manager – compatible with Exchange/M365 hybrid setups.

  • Central rollout

    Deploy as an integrated app in the Microsoft 365 admin center or sideload for pilots. Production hosting: outlook-addin.sparks.team.

In development

  • Create an appointment directly from an email (carry over recipients as attendees)
  • Dual-write: appointment also in the Sparks Cloud calendar (Postgres)
  • Sync RSVP status between Sparks and Outlook
Enterprise interop

Cisco Jabber: click-to-IM and click-to-call

Organisations running Cisco Jabber (CUCM + IM and Presence) can start chat or a call in the installed Jabber client from Sparks – without embedding Jabber chat in the app and without an XMPP bridge.

Enabled per organisation. From the contact card, people page and avatar menu, Sparks opens the Jabber protocol handler (IM or call). History and media stay in Jabber.

What the integration does today

  • Click-to-IM

    Opens the Jabber chat window for the contact’s JID or user ID via deep link (e.g. im: / xmpp:).

  • Click-to-Call

    Starts an audio or video call via Jabber protocol handlers (ciscotel: / tel: / sip:) using the contact’s number or SIP URI.

  • Org control

    Admins enable the feature per organisation and configure preferred schemes and an optional default IM domain.

  • Desktop and web

    Tauri desktop and the browser open the OS protocol handler. Requires Jabber installed and registered.

Intentionally not included

  • No Matrix↔XMPP chat bridge and no shared history
  • No Cisco presence sync into Sparks
  • Not a PSTN/contact-centre replacement and no deskphone CTI in the web app

The principle: connect, don't migrate

Sparks is not a new silo. It connects to your existing backends and leaves your data where it is – or you use the native Sparks Cloud calendar (EU Postgres) without an external calendar source. Exchange data stays in Exchange. Google data stays in Google. Nextcloud data stays in Nextcloud. Sparks is the frontend that brings everything together.

Data stays in your backends – Sparks is the frontend.

No other provider can do this

AI assistant with real context from all backends

The Sparks assistant accesses calendars, chats, tasks and files from all connected backends – simultaneously. Questions like "What are my tasks for today?" or "Summarise the Nextcloud document we discussed in the last meeting" are answered with real context – not hallucinations.

Discover the AI assistant

Which backend do you use?

Sparks Free is free to use and supports one backend.

Start for free