Base44: OAuth Connectors for Google, Slack, Salesforce & More
Base44Base44 introduced OAuth Connectors, a native integration layer enabling apps to connect to third-party services including Google Workspace, Slack, Notion, Salesforce, HubSpot, LinkedIn, and TikTok without manual token management. Developers define connector configuration files and authorize each service through the CLI, after which access tokens are retrievable in backend functions via a single API call. The feature eliminates the need to build or maintain OAuth flows from scratch.
Sources & Mentions
2 external resources covering this update
Overview
Base44 released OAuth Connectors, a first-class integration layer that allows developers to connect Base44 apps to external services using OAuth — without writing or maintaining their own OAuth flows. The feature abstracts credential storage, token refresh, and authorization handshakes into a managed service, exposing a simple getAccessToken() method for use inside backend functions.
Supported Integrations
At launch, Base44 OAuth Connectors supports twelve major platforms:
- Google Workspace: Gmail, Calendar, Drive, Sheets, Docs, Slides
- Productivity: Slack, Notion
- CRM: Salesforce, HubSpot
- Social/Marketing: LinkedIn, TikTok
How It Works
Connectors are defined as JSONC configuration files placed in the project's base44/connectors/ directory. Each file specifies the integration type and the OAuth scopes the app requires. When a developer runs the CLI deploy command, the CLI prompts for authorization of each connector in sequence. Once authorized, credentials are stored and managed by Base44's backend. Inside any backend function, the token is retrieved with a single call.
Developer Impact
No More OAuth Boilerplate
Before this feature, integrating a service like Google Calendar required implementing the entire OAuth 2.0 authorization code flow: redirect handling, token exchange, refresh logic, and secure credential storage. Base44 OAuth Connectors removes all of that. Developers declare what they need; Base44 handles the rest.
Secure Credential Management
Tokens are stored securely by Base44 and retrieved at function execution time. Developers never handle raw credentials in application code, reducing the risk of accidental exposure.
Scope-Based Permissions
Each connector only requests the OAuth scopes declared in its configuration file. This enforces the principle of least privilege at the configuration layer, making it straightforward to audit exactly what permissions each integration holds.
Use Cases
OAuth Connectors unlock a wide range of automation scenarios directly from within Base44 apps: reading calendar availability before booking, writing data to Google Sheets on form submission, posting Slack notifications when entity records change, or syncing CRM contacts from Salesforce. These workflows previously required either external automation tools like Zapier or significant custom backend development.