Appearance
Connections
Connections let Lumicast talk to external services on your behalf — authenticating with OAuth or an API key so your data sources can pull in live data.
You set up a connection once. After that, any data source that needs that service just references the connection — no re-entering credentials.
How connections are created
Connections are created inline during data source setup. When you choose a data source type that requires an external account (Google Sheets, Airtable, Jira, etc.), Lumicast prompts you to either pick an existing connection or authorise a new one on the spot.
There is no standalone "Connections" page — connections only exist in the context of the data sources that use them.
Connection types
OAuth connections
These open an authorisation window where you sign in to the external service and grant Lumicast access:
| Service | Used for |
|---|---|
| Google Sheets | Data sources reading spreadsheet data |
| Google Calendar | Google Calendar data sources |
| Airtable | Data sources reading Airtable bases |
| Jira | Data sources reading Jira issues |
| GitHub | Data sources reading repository data |
| GitLab Cloud | Data sources reading GitLab repository data |
| Linear | Data sources reading Linear issues |
| Sentry | Data sources reading Sentry errors and performance |
API key / token connections
These ask for credentials you copy from the external service (no browser login window):
| Service | What you provide |
|---|---|
| Zermelo | API token from your Zermelo school portal |
| GitLab (self-hosted) | Token and base URL of your GitLab instance |
| Stripe | API key from the Stripe dashboard |
| Plausible | API key from your Plausible account |
Re-using a connection
When you set up another data source against the same service, pick the existing connection from the dropdown instead of creating a new one. A single connection can back any number of data sources.
You can also create multiple connections to the same service (for example, two different Google accounts) and choose which one a given data source should use.
Expired or revoked connections
OAuth tokens can expire after long periods of inactivity, or be revoked from the external service's side. Expired and revoked connections are listed on the Data Sources home page — from there you can re-authorise them (which restores every data source that uses the connection at once) or delete them if they're no longer needed.