Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.base44.com/llms.txt

Use this file to discover all available pages before exploring further.

Add app user connectors to let each person using your app connect their own account to a third party service, such as Google, Slack, or Notion. App user connectors are added at the workspace level and can be used across apps in that workspace. You can add them from your workspace settings or directly from the AI chat in a specific app.
Available connectors for app users

Scheduling app

Let each person connect their own Google Calendar to view availability or create events.

Sales app

Let each salesperson connect their own HubSpot account to manage contacts and deals.

Content planning app

Let each team member connect their own Notion account to sync pages or tasks.

Before you begin

Create an OAuth app in the developer platform for the service you want to connect before adding the connector in Base44. See Preparing connector details.
You need a Builder plan or higher to add app user connectors.

​
Preparing connector details

Before adding the connector in Base44, prepare the details required by the service you want to connect. This usually means creating an OAuth app or project in that service’s developer platform, adding your Base44 redirect URI, and copying the details you need into Base44. The exact setup depends on the service. For example, Google uses Google Cloud, Slack uses Slack API Applications, and LinkedIn uses the LinkedIn developer portal.

Setup overview

  1. Prepare your Base44 redirect URI: Use the callback URL for your live app, custom domain, or preview. See the formats below.
  2. Create an OAuth app: Do this in the third party service’s developer platform.
  3. Add the redirect URI: Paste the Base44 redirect URI into the OAuth app settings.
  4. Prepare the connector details: Copy the Client ID and Client Secret, then choose the scopes your app needs.
  5. Add the connector in Base44: Paste the details into the connector setup form.

Redirect URI formats

  • Live app URL: https://your-live-app-domain.base44.app/api/external-auth/callback
  • Custom domain: https://your-custom-domain.com/api/external-auth/callback
  • Preview URL: https://preview--your-live-app-domain.base44.app/api/external-auth/callback
  • Some services call the redirect URI a callback URL or authorized redirect URI.
  • Enter the redirect URI exactly as shown.
  • Add the preview redirect URI if you want to test the connector in preview.
  • Some services only show the Client Secret once. Copy it before closing the page.
Treat Client Secrets like passwords. Do not share them with others. Only copy them into the AI chat when it specifically asks for them as part of the secure connector setup flow.

​
Adding a connector in Base44

Once you have your OAuth app details, add the connector from your workspace settings or from the AI chat in a specific app.

​
Adding the connector from your workspace

Add the connector from your workspace settings and enter the required details. To add a connector from your workspace:
  1. Click your profile icon.
  2. Click Account settings.
  3. Click Connectors.
  4. Under Connectors For App Users, click Add Connector.
  5. Click the connector you want to add.
  6. Enter the following:
    • Connector name: Enter a short name to identify this connector, for example Google Calendar scheduling.
    • Client ID: Enter the Client ID from the OAuth app you created in the connected service.
    • Client Secret: Enter the Client Secret from the same OAuth app.
    • Scopes: Enter the scopes your app needs, with each scope on a separate line.
  7. Click Add Connector.
Add LinkedIn Connection window showing fields for connector name, Client ID, Client Secret, and scopes.

​
Adding the connector using the AI chat

You can also start from the AI chat in the app where you want to use the connector. To add a connector from the AI chat:
  1. Open the app where you want to use the connector.
  2. Ask the AI chat to add a feature where each person connects their own account.
  3. If the connector is already set up in your workspace, the AI chat can use it directly in the app.
  4. If the connector is not set up yet, enter the connector details, including the Connector name, Client ID, Client Secret, and Scopes.
  5. Click Connect.
AI chat prompting for connector details, including connector name, Client ID, Client Secret, and scopes.

​
Using a connector in your app

Once the connector is set up, prompt the AI chat in the app you want to use it in to build a feature with that connector.
Settings page in an app showing a LinkedIn Connection section with a Connect LinkedIn button.

​
Managing connectors for app users

You can update or remove connectors at any time from the Connectors tab. Changes you make apply across all apps in your workspace.
If you change the scopes, people who already connected their account need to reconnect and approve the updated permissions.
To edit a connector:
  1. Click your profile icon.
  2. Click Account settings.
  3. Click Connectors.
  4. Under Connectors For App Users, hover over the connector and click View.
  5. Hover over the connection name and click Edit.
  6. Update the fields.
  7. Click Save Changes.
To delete a connector:
  1. Click your profile icon.
  2. Click Account settings.
  3. Click Connectors.
  4. Under Connectors For App Users, hover over the connector and click View.
  5. Hover over the connection name and click Edit.
  6. Click Delete Connector.
  7. Click Delete Connector again to confirm.
Deleting a connector removes it from your apps for everyone who used it. This cannot be undone.
Edit connector window showing the connector name, Client ID, Client Secret, scopes, and options to save changes or delete the connector.

​
Troubleshooting

Click a topic below to troubleshoot app user connector setup.
This usually means the redirect URI in the connected service does not match your Base44 callback URL exactly.To fix a redirect URI mismatch:
  1. Open the OAuth app in the connected service.
  2. Go to the redirect URI, callback URL, or authorized redirect URI settings.
  3. Check that the URL matches your Base44 callback URL exactly.
  4. Check whether your app uses a custom domain.
  5. Check whether you are testing in preview.
  6. Add the correct live, preview, or custom domain callback URL.
  7. Save the OAuth app settings.
  8. Try connecting again from your app.
This usually means the preview redirect URI is missing from the connected service.To fix preview connection issues:
  1. Open the OAuth app in the connected service.
  2. Go to the redirect URI, callback URL, or authorized redirect URI settings.
  3. Add the preview redirect URI for your app.
  4. Save the OAuth app settings.
  5. Open your app preview.
  6. Sign in as someone using the app.
  7. Try connecting again.
This usually means the Client ID or Client Secret is missing, incorrect, or copied from the wrong OAuth app.To fix an invalid Client ID or Client Secret:
  1. Open the OAuth app in the connected service.
  2. Copy the Client ID again.
  3. Copy the Client Secret again.
  4. Go back to Base44.
  5. Edit the connector.
  6. Paste the updated values.
  7. Click Save Changes.
This usually means your app requested a permission that is missing, unavailable, or written in the wrong format.To fix a scope error:
  1. Check the connected service’s OAuth documentation.
  2. Confirm which scopes your app needs.
  3. Copy the scopes exactly as shown in the service’s documentation.
  4. Add each scope on a separate line in Base44.
  5. Save the connector.
  6. Ask people who already connected to reconnect and approve the updated permissions.
Some services keep new OAuth apps in testing mode until you publish or verify them. People may not be able to connect unless they are added as test users.To fix testing mode issues:
  1. Open the OAuth app in the connected service.
  2. Check whether the app is in testing, development, or unpublished mode.
  3. Add test users if the service requires it.
  4. Publish or verify the OAuth app if needed.
  5. Try connecting again from your app.

​
FAQs

User connectors let each person connect their own account. Shared connectors use one account for everyone in the app.
The connected service needs to know which app is requesting access. The OAuth app gives you the Client ID, Client Secret, scopes, and redirect URI settings needed for the connection.
You find them in the OAuth app or developer app you create in the connected service. The exact location depends on the service.
Scopes are permissions. They tell the connected service what your app can access after someone connects their account.
Use the redirect URI for the environment you want to connect. For live apps, use your live app callback URL. For preview testing, add the preview callback URL. For custom domains, add the custom domain callback URL.
Yes, if you want to test the connector in preview. Preview and live apps use different redirect URIs.
If the connector is already set up in your workspace, the AI chat can use it directly in the app without asking you to enter the connector details again.
Some tools can be connected in 2 ways, so the AI chat may confirm the type you want to add.
  • Shared: Choose this if you want one account to power the feature for everyone in the app.
  • Per-user: Choose this if each person should connect their own account.
Yes. You can add multiple connectors with different scopes for different use cases.
People who already connected their account need to reconnect and approve the updated permissions.
Yes. People can disconnect at any time from within the app.
Yes. Base44 encrypts sensitive credentials and access tokens and handles automatic token refresh.