osFoundry / Platform
Integrations
OAuth-connected services — Slack, GitHub, Stripe, Google. Auth state in one view.
What it is
Integrations is the settings surface in osFoundry where you connect outside services over OAuth and see the authorization state of all of them in a single view. Instead of hunting through separate screens to remember which accounts are linked, whether a token is still valid, or which workspace a connection belongs to, you get one list: Slack, GitHub, Stripe, Google, each showing whether it is connected and authorized. Connecting runs the standard OAuth consent flow for that provider, so you grant access in the provider's own login screen and osFoundry stores the resulting authorization rather than asking for a password.
Because osFoundry is a bring-your-own-key desktop workspace, these OAuth connections sit alongside your own model API keys rather than routing through a reseller. The point is a single place to wire the workspace to the services your agents and chats actually touch — a GitHub account for code, Slack for messaging, Stripe for billing data, Google for calendar and related services — and then to reason about that access from one screen. When a connection expires or a provider revokes consent, the auth state in this view is where you notice it and reconnect.
Living under Settings & Security, this page is also the honest inventory of what is connected: every OAuth grant in one list, so revoking or re-authorizing is a deliberate act you can see, not something buried per feature. On a local-first desktop app, that consolidated view matters — you can tell at a glance exactly which external accounts the workspace is authorized to reach.
Key capabilities
- Connect Slack, GitHub, Stripe, and Google to osFoundry over standard OAuth consent flows
- See every connection's authorization state — connected, expired, or revoked — in one settings view
- Grant access in each provider's own login screen; osFoundry stores the OAuth authorization, not your password
- Manage integrations alongside your own model API keys, with no reseller in the middle (BYOK)
- Revoke or re-authorize any connection deliberately from a single Settings & Security inventory
Use cases
- Developer: links a GitHub account over OAuth so agents and chats can work against repositories, and checks the connection is still authorized after a token rotation
- Operator: connects Slack and Stripe, then uses the single auth-state view to confirm both grants are live before relying on them in a workflow
- Security-minded lead: audits which external accounts the workspace can reach from one Settings & Security list and revokes a Google connection that is no longer needed
Frequently asked questions
Which services can I connect?
The Integrations page supports OAuth-connected services including Slack, GitHub, Stripe, and Google. Each appears in one list with its current connection and authorization state.
Does connecting an integration mean giving osFoundry my password?
No. Integrations use OAuth, so you authorize access in the provider's own login and consent screen. osFoundry stores the resulting authorization, not your account password.
How do I know if a connection has stopped working?
The Integrations view shows the auth state of every connected service in one place. If a token expires or a provider revokes consent, you see it there and can re-authorize the connection.