App user connectors: let your users connect their own accounts - Lovable Documentation
Documentation Index Fetch the complete documentation index at: /llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. App user connectors let each end user of your published app connect their own third-party account. Your app then acts on their behalf , with their own permissions and only their data. Authentication runs through Lovable’s connector gateway , so user tokens are stored securely and never exposed in your project.
Use an app user connector when each signed-in user should see their inbox, their calendar, or their CRM records, not a single shared account. Standard connector vs. app user connector Both are app connectors and both route through the gateway. The difference is whose account the app uses. Standard app connector App user connector Whose account One account you connect once Each end user’s own account Who authorizes You (or a workspace admin) Every user, the first time they use it Data the app sees The single connected account’s data, shared by all visitors Only the signed-in user’s data, per their granted scopes Typical use Send from a company inbox, post to one Slack workspace, query one warehouse ”Connect your Gmail”, “Connect your Salesforce”, per-user dashboards Credentials Stored once, reused for every request Stored per user, isolated from other users Which one to use.
If every visitor should act as the same account (for example, notifications from one company Slack), use a standard connector. If every visitor should act as themselves (for example, viewing their own calendar events or their own CRM records), use an app user connector . How it works An app user connector has two parts: a client you configure once, and the individual sign-ins your end users complete when they use the app.
1. You configure the client once You set up a client for the connector once for your workspace. Depending on the provider, this means registering an OAuth application with that provider and adding its details to the client. Examples are a Salesforce External Client App, a Databricks OAuth app, or a Snowflake OAuth security integration. This configuration is stored securely and reused for every user who connects. It never contains any individual user’s data.
2. Each user connects their own account The first time one of your users needs the integration, your published app sends them through the provider’s standard OAuth consent screen . The user signs in with their own account and approves the requested permissions (scopes). Lovable exchanges the authorization for tokens and stores them encrypted in the connector gateway , linked to that individual user. 3. Your app calls the provider through the gateway When your app makes a request, it goes to the connector gateway rather than directly to the provider.
The gateway: Finds the connection for the request and checks that it belongs to this workspace, project, and user. Refreshes expired tokens automatically. When the provider rejects a request because the access token has expired, the gateway refreshes it with the refresh token and returns the response to your original request. If the refresh token is no longer valid, the gateway answers with a 401 error whose type is credential_refresh_token_expired , and the code Lovable generates asks the user to reconnect.
Injects the credentials and forwards the request to the provider. The third-party tokens never touch your app code. Stores each user’s credentials separately. How your app picks the right user depends on how users sign in: For apps published to your workspace that use workspace identity reuse (Business and Enterprise plans, newer apps), your app exchanges the signed-in member’s identity token for a short-lived access token and sends it to the gateway.
The gateway verifies the token and finds that member’s connection. When your app manages sign-in itself, for example with built-in authentication , the client needs Offline access enabled. Each user’s sign-in then gives your app an opaque connection key for that user. Your app sends that key together with its LOVABLE_API_KEY on every request for the user, including background operations. The gateway uses the pair to find the connection.
Because tokens live in the gateway and not in your project, they are not visible in project settings, to workspace admins, or to Lovable while it builds your app. See Integration security for how credentials are stored, rotated, and deleted. Available app user connectors The following providers are available as app user connectors . For Google and Microsoft, each product is its own connector but shares the same sign-in.
The OAuth app setup column links to each provider’s own documentation for creating the OAuth application you configure the client with. Provider App user connectors OAuth app setup Google Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, Google Slides Create OAuth credentials Microsoft Outlook, OneDrive, SharePoint, Teams, OneNote, Word, Excel, PowerPoint Register an application GitHub GitHub Create an OAuth app GitLab GitLab API (GitLab.com, Self-Managed, and Dedicated) Configure GitLab as an OAuth 2.0 provider .
Use a confidential application. Start with read_user , add read_api for reads, or use api for writes. Slack Slack Installing with OAuth Salesforce Salesforce External Client Apps HubSpot HubSpot Working with OAuth Linear Linear OAuth 2.0 authentication Notion Notion Authorization (public integration required) Databricks Databricks Authorize user access with OAuth Microsoft Fabric Microsoft Fabric Create a Microsoft Entra app (delegated GraphQLApi.Execute.All permission required) Power BI Power BI Register an app (delegated Dataset.Read.All and Workspace.Read.All permissions required) Snowflake Snowflake OAuth for custom clients Amazon Redshift Amazon Redshift Data API with trusted identity propagation , plus connector-specific AWS setup Workday Workday OAuth 2.0 API clients (Workday sign-in required) The list of app user connectors grows over time.
Open Connectors to see what is currently available. Set up an app user connector Setup happens in two steps: configure the client in your workspace, then add the connect experience to your app. Register and approve your OAuth app with the provider Before you can configure the client, you (or your organization’s admin) register an OAuth application on the provider’s side and get it approved for use. This process differs from provider to provider , and each has its own requirements.
For example, you might create a Salesforce External Client App, a Databricks OAuth app, a Snowflake security integration, a Google OAuth consent screen, or a Microsoft app registration. Approval can also involve extra steps, such as admin consent for a tenant, app verification for sensitive scopes, or installation approval in a workspace. Because the exact steps and any review process are owned by the provider, the authoritative instructions are in that provider’s own documentation .
The OAuth app setup links in Available app user connectors point you to each provider’s guide. When you register the OAuth app, add Lovable’s connector gateway callback URL to the app’s allowed redirect URIs so authorization can complete: https://connector-gateway.lovable.dev/api/v1/app-users/oauth2/callback Lovable also shows this value in the connector setup screen so you can copy it directly. If the provider requires verification of lovable.dev , see I can’t verify the callback domain .
Configure the client 1 Open the connector Open Connectors and select the provider you want (for example Salesforce or Gmail ). 2 Add a client Add a client and enter the OAuth application details from the provider (for example the client ID and secret, and any account or workspace URL the provider requires). 3 Choose who can use the client Under Sharing , a new client is pri
The rest of this page is on the live site.