First-run setup

Have four things ready.

ClassSync tests each connection as you go. For a normal hosted installation you need a Fireflies API key, a Gemini API key, a Notion connection token and the ClassSync device setup token.

Keep these values private. Never put API keys, recovery codes or webhook signing secrets in screenshots, GitHub issues or chat messages. ClassSync stores service credentials in your device's OS secure storage.

1. Fireflies API key

Open Developer settings

In Fireflies, go to Settings → Developer settings under your personal settings. Copy the API key shown there. Fireflies also exposes the same flow from its Integrations page by searching for the Fireflies API.

Official Fireflies guide ↗

Screenshot slot: fireflies-api-key.webpCapture Settings → Developer settings with the key itself blurred.

2. Gemini API key

Create a key in Google AI Studio

Open the API Keys page in Google AI Studio and create a new key for the project you want ClassSync to use. New keys are authorization keys by default. Copy the value into the Gemini step.

Open AI Studio API Keys ↗Official key docs ↗

Using an older key? Google is retiring legacy standard API keys for the Gemini API. Prefer a newly created authorization key rather than carrying forward an unrestricted legacy key.

Screenshot slot: gemini-api-key.webpCapture AI Studio → API Keys showing the Create API key action, with all real keys hidden.

3. Notion template + connection token

Duplicate the ClassSync template

Duplicate the ClassSync Notion template into your own workspace. It contains the subject and summary databases that the app expects.

Duplicate template ↗

Create an internal Notion connection

In Notion, open Settings → Connections, enable Developer Mode, then open the personal access token area and create a new internal connection. Copy its token.

Official Notion guide ↗

Give the connection access

Open your copied ClassSync Template page and add the new connection to that page. ClassSync can only discover databases the connection is allowed to access.

Screenshot slots: notion-token.webp + notion-page-connection.webpOne image for token creation and one for adding the connection to the copied template.

4. ClassSync relay token

Use the hosted setup token or your self-hosted token

The production relay URL is already built into the app. The Device API token field expects the ClassSync bootstrap setup token. This is not a Fireflies secret and it is not a value Cloudflare creates for you automatically.

If you run your own relay, you choose this secret yourself when setting DEVICE_API_TOKEN in Wrangler.

Self-host instructions →

5. Finish the nine-screen wizard

Welcome: review what you need, or choose Use recovery code if this is an additional device.
Fireflies: paste and test the API key.
Gemini: paste and test the API key; keep the recommended model unless you know why you need another.
Notion: paste the token, discover the shared databases and select Lista de Cadeiras plus Histórico de Resumos.
Academic: optionally connect ISEP Portal and Moodle, or skip this for later.
Relay: paste the device setup token. Only change the URL for self-hosting or staging.
Account: create your private ClassSync account. The app generates your personal Fireflies webhook URL and signing secret.
Automation: choose background processing and notification preferences.
Ready: review the tested connections and save.

6. Configure the Fireflies webhook

After the Account step, return to Fireflies Developer settings and configure Webhooks V2 using the exact URL and signing secret shown by ClassSync. Subscribe only to meeting.transcribed.

Screenshot slot: fireflies-webhook-v2.webpCapture the Webhooks V2 configuration with URL and secret replaced by fake values.

Notion database requirements

Lista de Cadeiras: Nome (or Name), Ano, Semestre, Status.
Histórico de Resumos: Nome, Data, Cadeira.
Only subjects whose Status is In progress are classification candidates.

Recommended metadata Let ClassSync add the optional Fireflies ID text property. It makes duplicate reconciliation safer across devices and interrupted publishes.

Moving to another device

Choose Use recovery code on the Welcome screen before entering any API keys. A recovery code can restore the shared Fireflies, Gemini and Notion configuration if the first device has already completed setup and synced a full account snapshot. Portal and Moodle credentials remain device-local.