Platform
What ScreenQube connects to today — and, because it matters more during procurement, what it does not.
Each of these is a real app in the console with its own page on this site. You schedule it once; it fetches and refreshes on its own. Nothing here needs a designer to touch it again on Monday.
Most "do you integrate with X?" questions have the same answer: if X can render a web page, ScreenQube can display it. A dashboard, a rota, a queue board, an internal tool behind your own auth — point the Web URL app at it and it becomes a screen. It is not a connector, and it will not pull structured data back out. But it is honest, it works today, and it covers more ground than a list of named logos would.
The console accepts Google and Microsoft sign-in alongside email and password. Both are redirects to the provider, not background requests, so the handshake happens where you can see it.
Whether SAML, Azure AD group mapping or SCIM provisioning are offered has not been established. If your security review requires one of those, ask before you plan around it.
Automation
Set side by side deliberately. An integrations page that lists only the working half is the easiest kind of page to write and the most expensive one to believe.
Working today
The nine apps above fetch their own content on a schedule. This is the automation most sites are actually asking for when they ask about integrations.
Not established
No customer-facing REST API, webhook or automation connector has been evidenced on the platform. We would rather say that than publish a roadmap item as though it shipped.
Tell us what the other system is and what has to move between them. If the answer is the Web URL app, we will say so, and you will have it running this week. If the answer is that it does not exist yet, you will get that answer too — before it becomes a line item in your project plan rather than after.