Base44 Adds Shared OAuth Connections for Workspace Data Connectors
Base44Base44 introduced getWorkspaceConnection(), a new SDK method that retrieves a shared OAuth token for workspace-registered connectors — OAuth apps that a builder configures once in Workspace Settings, such as Databricks or Snowflake. It serves as the shared-token counterpart to the existing getCurrentAppUserConnection(), letting all users of an app share a single, workspace-level connection instead of each authenticating individually. Connectors of this kind are identified by connector ID rather than an integration type string, giving builders a cleaner way to wire backend functions into enterprise data platforms.
Key Takeaways
getWorkspaceConnection()introduces a shared-token model, letting one builder-authorized OAuth connection serve every user of an app instead of requiring per-user logins.- Base44 explicitly calls out Databricks and Snowflake as target use cases, signaling a push toward supporting backend data-warehouse integrations more directly.
- The method is the shared-token counterpart to
getCurrentAppUserConnection(), giving developers a clear choice between per-user and workspace-wide OAuth connections depending on the use case. - Workspace connectors are referenced by connector ID rather than an integration type string, distinguishing them structurally from Base44's built-in per-user integrations.
- The returned
connectionConfigobject (e.g., account subdomain) means developers no longer have to hardcode platform-specific configuration, since it travels with the token response. - This is a developer/backend-facing SDK change rather than a UI feature, so it will primarily be noticed by builders wiring custom backend functions into enterprise data platforms.
A New Way to Share Data Connections Across a Workspace
Base44 added getWorkspaceConnection() to its backend SDK, giving app builders a dedicated method for pulling a shared OAuth token out of connectors that are registered at the workspace level. Previously, developers reaching for OAuth-backed data platforms in backend functions relied on getCurrentAppUserConnection(), which is scoped to whichever individual user is making the request. The new method fills a gap for services where a single, builder-consented connection should be reused by every user of an app, rather than requiring each person to complete their own OAuth flow.
How Workspace Connectors Differ from App User Connectors
The distinction Base44 is drawing is between two connector models. App user connectors hand each signed-in user their own OAuth token — useful when an action needs to happen "as" a specific person, like posting to their personal account. Workspace connectors, by contrast, follow a shared-account model: the app builder authorizes the connection once inside Workspace Settings, and the resulting token is reused across every user of the app. This second model is a natural fit for connecting to backend data infrastructure — Base44 calls out Databricks and Snowflake by name as example use cases, platforms where a single service-level credential typically makes more sense than per-user authentication.
What Changed for Developers
Calling getWorkspaceConnection() from base44.asServiceRole.connectors returns an access token and an optional connectionConfig object (for example, a Snowflake account subdomain), which developers can plug directly into calls against the target platform's API. Connectors accessed this way are referenced by their connector ID — the identifier assigned when the connector is registered in Workspace Settings — rather than by a generic integration type string used elsewhere in the connectors API. This keeps workspace-specific OAuth apps cleanly separated from Base44's catalog of pre-built, per-user integrations.
The change is aimed squarely at developers building apps that need to query or write to external data warehouses and similar backend services, extending Base44's connector system further into data-platform territory rather than just consumer-facing SaaS tools.