Setting up connectors for app users

Add user connectors so each person using your app can connect their own third-party account.

Add user connectors to let each person using your app connect their own account to a third-party service.

Connectors for app users are added at the workspace level and can be used across apps in that workspace.

Example use cases

• A scheduling app where each person connects their own Google Calendar.
• A sales app where each person connects their own HubSpot account.
• A content planning app where each person connects their own Notion account.

Before you begin:

• Create an app in the relevant provider and prepare your Client ID, Client Secret, and required scopes.
• People must be signed in to your app to connect their accounts.

You need a Builder plan or higher to add user connectors.

---

Adding connectors for app users

You can add connectors for app users from your workspace settings or from the AI chat in a specific app.

The connector is added at the workspace level and becomes available across apps in that workspace. People using your app then see a Connect button for each connector you add.

Adding a connector from your workspace

Add the connector from your workspace settings and enter the required details so people can connect their account.

Use a clear, purpose-based name so you can identify the connector later, for example, LinkedIn content publishing or HubSpot contacts sync.

To add connectors for app users from your workspace:

1. Click your profile icon.
2. Click Account settings.
3. Under Integrations, 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: A short name to identify this connector, for example LinkedIn content publishing.
   • Client ID: Enter your OAuth client ID.
   • Client Secret: Enter your OAuth client secret.
   • Scopes: Enter the scopes your app needs, with each scope on a separate line.
7. Click Add Connector.

Adding a connector using the AI chat in an app

You can also start from the AI chat in a specific app and enter the connector details there. The connector is added at the workspace level and can then be used in other apps in that workspace.

To add connectors for app users 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.

---

Using a connector in an app

After adding the connector, ask the AI chat in the app where you want to use it to build a feature with that connector.

---

Managing connectors for app users

You can update or remove connectors at any time from the Connectors page. 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. Under Integrations, 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. Under Integrations, 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.

---

Building a custom per-user OAuth flow

Not every tool is available as a user connector yet. If the tool you need is not available, you can build a custom per-user OAuth flow using backend functions and the provider’s API.

This is an advanced setup. Endpoints, scopes, and required parameters depend on the provider, so follow the provider’s OAuth documentation alongside the steps below.

To build a custom per-user OAuth flow:

1. Open the AI chat in your app editor.
2. Switch to Discuss mode.
3. Describe what you want, for example:

Each person should connect their own LinkedIn account. Help me design the OAuth flow with backend functions.

4. Work with the AI to outline the authorization URL, callback flow, token storage, and token refresh logic based on the provider’s documentation.
5. Use backend functions to implement the flow:
   • Send people to the provider’s authorization page.
   • Receive the authorization callback.
   • Store user-specific tokens securely in your app’s data.
   • Add token refresh logic if the provider uses expiring tokens.

---

FAQs

What is the difference between user connectors and shared connectors?

User connectors let each person connect their own account. Shared connectors use one account for everyone in the app.

What happens if the connector is already set up in my workspace?

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.

Why does the AI chat ask me to choose between Shared and Per-user?

Some tools can be connected in 2 ways, so the AI chat may ask which type you want to use.

• Choose Shared if you want one account to power the feature for everyone in the app.
• Choose Per-user if each person should connect their own account.

Can I add more than one connector of the same type?

Yes. You can add multiple connectors with different scopes for different use cases.

What happens if I change the scopes for a connector?

People who already connected their account need to reconnect and approve the updated permissions.

Can people disconnect their account?

Yes. People can disconnect at any time from within the app.

Are user tokens stored securely?

Yes. Base44 encrypts sensitive credentials and access tokens and handles automatic token refresh.