Connectors

Connect your app to third-party services using OAuth or managed provisioning

You’re viewing developer documentation

This documentation is for developers working with the Base44 developer platform. For information about connectors in the app editor, see Using Connectors.

Connectors let your app connect to third-party services like Google Workspace, Slack, Salesforce, and more. Most connectors use OAuth to authenticate with external APIs so you can make calls with your app’s credentials. Stripe uses a separate managed provisioning flow.

See supported services for the full list of available connector types.

To get started:

1. Configure a JSONC file for each service you need
2. Deploy and authorize via the CLI
3. Use in backend functions by calling getConnection() for OAuth connectors, or using the Stripe REST API directly for payments

Configure

Each connector is a JSONC file in your project’s connectors directory. The file defines the integration type and the scopes your app needs. By default the directory is base44/connectors/, but you can customize the path in your project configuration.

connectors

googlecalendar.jsonc

slack.jsonc

slackbot.jsonc

notion.jsonc

Example

This example configures a Google Calendar connector with read and event management scopes:

{
  "type": "googlecalendar",
  "scopes": [
    "https://www.googleapis.com/auth/calendar.readonly",
    "https://www.googleapis.com/auth/calendar.events",
  ],
}

Field reference

type · string · required

The integration type identifier. See the supported services table for the full list of accepted values.

Each connector type can only be defined once in your project.

scopes · array · required

Array of OAuth scopes required for your integration. The specific scopes depend on the external service and what operations your app needs to perform. See the connector permissions and scopes documentation for available scopes for each service.

Deploy and authorize

Deploy connectors with connectors push or deploy. To download existing connectors from Base44, use connectors pull.

When you push, the CLI handles each connector based on its type:

• OAuth connectors: The CLI prompts you to authorize each connector one by one. It suggests opening your browser automatically, and if you accept, it iterates through each integration’s authorization page sequentially. After authorization completes, your OAuth tokens are stored securely and you can retrieve them using the SDK.
• Stripe: The CLI provisions a Stripe sandbox for your app and returns a claim URL to complete onboarding. No OAuth flow is needed.

Use in backend functions

Once deployed and authorized, use the connector in your backend functions. The approach depends on the connector’s auth model:

OAuth connectors

Call connectors.getConnection() with the connector type to retrieve an accessToken for making authenticated API calls. Some connectors also return a connectionConfig with additional parameters (e.g. a subdomain or account ID).

This example retrieves a Google Calendar connection and fetches upcoming events:

const { accessToken } =
  await base44.asServiceRole.connectors.getConnection("googlecalendar");

const timeMin = new Date().toISOString();
const url = `https://www.googleapis.com/calendar/v3/calendars/primary/events?maxResults=10&orderBy=startTime&singleEvents=true&timeMin=${timeMin}`;

const calendarResponse = await fetch(url, {
  headers: { Authorization: `Bearer ${accessToken}` },
});

const events = await calendarResponse.json();

Stripe

Stripe does not use getConnection(). Instead, the platform stores your Stripe API keys as app secrets when you provision the connector. In your backend functions, read STRIPE_SECRET_KEY from the environment and call the Stripe REST API directly.

This example creates a Stripe Checkout session and returns the payment URL:

const STRIPE_SECRET_KEY = Deno.env.get("STRIPE_SECRET_KEY");

Deno.serve(async (req) => {
  const { priceId, successUrl, cancelUrl } = await req.json();

  const response = await fetch("https://api.stripe.com/v1/checkout/sessions", {
    method: "POST",
    headers: {
      Authorization: `Bearer ${STRIPE_SECRET_KEY}`,
      "Content-Type": "application/x-www-form-urlencoded",
    },
    body: new URLSearchParams({
      "payment_method_types[]": "card",
      "line_items[0][price]": priceId,
      "line_items[0][quantity]": "1",
      mode: "payment",
      success_url: successUrl || `${req.headers.get("origin")}?success=true`,
      cancel_url: cancelUrl || `${req.headers.get("origin")}?canceled=true`,
    }),
  });

  const session = await response.json();
  return Response.json({ url: session.url });
});

Supported services

Service	Type identifier	Auth model
Airtable	airtable	OAuth
Box	box	OAuth
ClickUp	clickup	OAuth
Discord	discord	OAuth
Dropbox	dropbox	OAuth
GitHub	github	OAuth
Gmail	gmail	OAuth
Google Analytics	google_analytics	OAuth
Google BigQuery	googlebigquery	OAuth
Google Calendar	googlecalendar	OAuth
Google Classroom	google_classroom	OAuth
Google Docs	googledocs	OAuth
Google Drive	googledrive	OAuth
Google Search Console	google_search_console	OAuth
Google Sheets	googlesheets	OAuth
Google Slides	googleslides	OAuth
HubSpot	hubspot	OAuth
Linear	linear	OAuth
LinkedIn	linkedin	OAuth
Microsoft Teams	microsoft_teams	OAuth
Microsoft OneDrive	one_drive	OAuth
Notion	notion	OAuth
Outlook	outlook	OAuth
Salesforce	salesforce	OAuth
SharePoint	share_point	OAuth
Slack User	slack	OAuth
Slack Bot	slackbot	OAuth
Splitwise	splitwise	OAuth
Stripe	stripe	Managed
TikTok	tiktok	OAuth
Typeform	typeform	OAuth
Wix	wix	OAuth
Wrike	wrike	OAuth

For OAuth connectors, pass the type identifier to getConnection() to retrieve an access token for that service.

Run connectors list-available to see the latest available integrations, including descriptions and any required connection config fields.

See connector permissions and scopes for the OAuth scopes each service may request.

See also

• connectors list-available
• connectors pull
• connectors push
• deploy
• Backend Functions