Integrations

What Cerium connects to, and what it does not

The connections that work today, each inside the module that uses it. Next to them, what is missing: Zoom, calendars, SMS and WhatsApp. Better to know before you buy than after you roll it out.

How it is wired

Connections run one way: the outside service reports an event, Cerium checks its signature and records the result. Cerium does not send its own webhooks to the school's systems.

What comes into Cerium

  • Stripe reports a payment with a signed webhook; a repeated event is never booked twice.
  • The video server reports who joined and left the room; that becomes an attendance hint in the Journal.
  • The accounting software replies with the invoice number; a failure goes back to the queue and retries on its own.
  • The enquiry form also works without a key: a public address with a QR code, straight into the pipeline.

Not available today

  • Zoom, Google Meet and Microsoft Teams.
  • Google Calendar, Apple Calendar and iCal subscriptions.
  • SMS and WhatsApp.
  • Outgoing webhooks and an API for reading school data.
  • An App Store and Google Play app with push notifications: in preparation.

Questions about integrations

Short answers, no overpromising. What is missing is listed alongside.

What Cerium does not connect
  • Google or Apple calendars, or iCal subscriptions.
  • An SMS gateway or WhatsApp.
  • Outgoing webhooks or a data-reading API.

No. Webhooks in Cerium are incoming only: from Stripe (school payments and the subscription) and from the video server. Every event has its signature checked, and a repeat is not recorded twice. The only way in from outside that the school sets up itself is the enquiry form API key.

No. The API key does one thing: it adds an enquiry to the CRM pipeline from a form on the school's website. A key with a list of addresses works only from a browser on those sites; a key without one works only server to server. School data comes out through CSV export from the tables.

Yes, for online payments. The school opens a connected account (Stripe Connect), so money goes from the guardian to the school's balance and on to its bank account. Cerium keeps only the customer and card identifiers and a label such as "Visa •••• 4242", never the card number. The platform fee on online payments is set in the agreement. Without Stripe, cash and bank transfers are entered by hand.

The one the school already uses: Fakturownia, wFirma, iFirma or inFakt. The software keys go into Settings and are stored encrypted. The software numbers the invoice, issues it and sends it to KSeF; Cerium builds the document from the payment, runs the queue and records the outcome.

No. The room opens on lessons set to online mode, on the platform's video server, with the group whiteboard alongside. The school connects nothing and creates no accounts, and students join from the browser. Lessons are not recorded; only a trace of who was in the room and when is kept.

Yes. Students, guardians and groups have a downloadable CSV template and an import of up to 500 rows per file, in one transaction. A student's groups, guardians and companies are matched by name. More about moving over on the Migration page.

See Cerium from the inside.

14 days on your groups and instalments. No card, no strings.