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 asks you to Select connection: pick an existing one, or choose New connection to sign in or enter credentials on the spot. Apps that need an external account work the same way.
There is no separate "Connections" page. The Data sources page lists your data sources grouped by the connection they use, and that is where you manage connections.
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.com | Data sources reading GitLab repository data |
| Linear | Data sources reading Linear issues |
| Sentry | Data sources reading Sentry errors and performance |
| Microsoft Power BI | Data sources running a DAX query against a semantic model |
| Microsoft Teams | Data sources reading channel messages |
| Microsoft SharePoint | Data sources reading news posts and list items |
| Data sources reading company page posts | |
| Data sources reading profile data and posts |
API key / token connections
These ask for credentials you copy from the external service (no browser login window):
| Service | What you provide |
|---|---|
| Zermelo | Portal URL and a one-time authorization code from your Zermelo Portal (see Connect Zermelo) |
| 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 (plus the base URL if you host Plausible yourself) |
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
Lumicast refreshes OAuth connections automatically where the service allows it, but access can still run out — for example after a long period of inactivity, or when it's revoked on the external service's side. On the Data sources page each connection shows its status: Connected, Expires in … days, or Expired.
When a connection is about to expire or has expired, click Reconnect next to it. Reconnecting restores every data source that uses the connection at once. The connection's actions menu also lets you Rename or Delete it — deleting a connection permanently deletes the data sources that use it too.