Integrations live under Settings, then Integrations, which makes them look like one feature. They are three.
Data for apps
The largest group. You connect a service once, and apps that read from it stop asking anyone for credentials: the app’s setup form offers your dashboards, reports, bases, or calendars instead.
Salesforce, Airtable, Power BI, Grafana, Google Calendar, Outlook Calendar, Shopify. See Data integrations.
Alerts to your tools
Screenly tells you when a screen goes offline, and comes back. Rather than only emailing, it can raise a PagerDuty incident or post into a Slack channel.
See Notification events.
Network access for screens
Tailscale is not about data or alerts at all. It puts your screens on your own private network so they can display internal dashboards and intranet pages.
That is why it sits under Security rather than Integrations, which catches people out. See Reaching your private network.
The full list
| Provider | What it is for | How you connect |
|---|---|---|
| Salesforce | Data for apps | OAuth, after installing our managed package |
| Airtable | Data for apps | OAuth |
| Power BI | Data for apps | OAuth through Microsoft |
| Grafana | Data for apps | A service account token, not OAuth |
| Google Calendar | Data for apps | OAuth |
| Outlook Calendar | Data for apps | OAuth |
| Shopify | Data for apps | OAuth, with your store domain |
| Slack | Alerts, and an app | OAuth |
| PagerDuty | Alerts | OAuth |
| Tailscale | Network access for screens | OAuth client ID and secret, under Security |
Slack does both
Worth calling out because it is the one provider that spans two of the three jobs. One Slack connection serves both offline alerts and any app that reads from Slack. Connect it once. See Slack.
What is not an integration
Zapier is external: it talks to Screenly’s API rather than being connected here.
The browser extension authenticates with an API token.
TradingView and similar apps that use a public embed need no account and no connection at all.