Skip to main content

​
About integrations

Integrations connect Base44 to the rest of your stack so you can automate workflows, pull in data, and call external services without wiring every API call by hand. You can integrate at 3 levels:
  • App level: Integrations inside a single app:
    • Built-in integrations such as Invoke LLM and SendEmail.
    • Connectors for OAuth-based connections to tools like Notion, Slack, or Google Workspace.
    • External API calls with backend functions that use per-app Secrets and functions.
  • Workspace level: Shared APIs managed once for the whole workspace:
    • Custom OpenAPI integrations based on OpenAPI specs that any app in the shared workspace can call securely.
  • Account level: Connections that live on your Base44 account:
    • MCP connections that you configure once so the Base44 AI chat can use external tools while you build, without changing your app’s deployed code.

​
App level integrations

App-level integrations live inside a single app. They include built-in integrations, connectors, and backend-powered external APIs that you wire to that app only.

​
Built-in integrations

Some integrations come preinstalled in Base44 and are available to use immediately. They do not require a paid plan, extra setup, or separate API keys. With these core integrations, you can add AI, messaging, file handling, and advanced logic to any app with no additional configuration. Base44 built-in integrations include:
  • Invoke LLM: Generate AI responses from the built-in language model using detailed prompts. Supports JSON schema outputs, file attachments for added context, image analysis, and web search for up-to-date information.
  • SendEmail: Send emails to people in your Base44 app with customizable sender names and rich HTML content.
    SendEmail does not support sending to external mailing lists or adding file attachments.
  • UploadFile: Let people upload files to your app. Use the returned file URL in other integrations or workflows.
  • GenerateImage: Create images from detailed text prompts. Returns a URL to the generated image.
  • ExtractDataFromUploadedFile: Pull structured data from uploaded files (CSV, PNG, JPG, JPEG, PDF) using JSON schemas. Useful for importing data in bulk.

​
Connectors

Connectors are OAuth-enabled integrations that let a specific app connect to supported tools. You ask the AI chat to connect a service, sign in, and approve the requested permissions. Your app can then read or write data in that tool based on what you allow.
You need a Builder plan or higher to use connectors in your app.
Examples of what you can build with connectors:
  • Sync a Notion database to power a knowledge view in your app.
  • Post updates to a Slack channel.
  • Sync Salesforce or HubSpot records into an internal dashboard.
  • Save files from your app to Google Drive.
  • Block off time in Google Calendar when a new booking is made.
  • Publish a LinkedIn post when a new blog post is published.
  • Show TikTok profile stats and follower counts in a dashboard.
Learn more about connectors.

​
External API calls with backend functions

External integrations using backend functions let a specific app talk directly to third-party services like Stripe, Twilio, or Google APIs with per-app credentials. These calls are wired through your own backend functions and Secrets. Use backend functions when:
  • You want a one-off integration for a single app.
  • You need custom logic that is tightly coupled to that app.
  • The service is not yet set up as a custom OpenAPI integration in your workspace.
Examples of external integrations with backend functions:
  • Sending welcome emails to new people using your app via your email provider.
  • Syncing your existing CRM with your app database.
  • Alerting your team in Slack when someone submits a form.
  • Generating content with AI tools using your own provider keys.
  • Calling vendor-specific APIs that do not have a connector or custom OpenAPI integration yet.
Important:
  • You need a Builder plan or higher to use backend functions.
  • You must activate backend functions in each app that needs to call external APIs (see below).
You store credentials as Secrets in the app dashboard and use them in TypeScript functions under Dashboard → Code → Functions.

​
Workspace level integrations

Workspace-level integrations live in a shared workspace and can be reused across many apps without repeating setup or credentials.

​
Custom OpenAPI integrations

Custom OpenAPI integrations let you register shared external APIs at the workspace level from an OpenAPI specification. You import a spec once, select the operations you want to expose, and any app in that shared workspace can call those operations through the SDK. The AI builder and your frontend code can call custom OpenAPI integrations directly through base44.integrations.custom without exposing credentials. Calls are proxied through the Base44 backend, so secrets never reach the browser, and you do not need to activate backend functions to use them. This is ideal for internal APIs and partner APIs that your team uses across many apps.
Important:
  • Custom OpenAPI integrations are only available in shared workspaces.
  • Only workspace owners and admins on a Builder plan or higher can create or edit custom OpenAPI integrations.
  • Anyone in the shared workspace can use an existing custom OpenAPI integration in their apps, even on a free plan, and without activating backend functions.
Learn how to configure these APIs in detail in Managing custom OpenAPI integrations.

​
Account level connections

Account-level connections are configured once for your Base44 account and are available wherever you use the Base44 AI chat.

​
MCP connections

MCP connections let you connect custom MCP servers to your Base44 account so the AI chat can use external tools and data as context while you build. This gives you a context-aware builder chat without changing your app’s deployed runtime.
Important:
  • MCP connections are available on the Builder plan or higher.
  • MCP servers are configured once per account under Account Settings → MCP Connections.
  • The AI chat only calls an MCP server when your prompt requires it (for example, when you mention that server or ask for data it provides). It does not contact every MCP server for every message.
Examples of what you can do with MCP connections:
  • Ask the AI chat to search an internal docs MCP and summarize the most relevant pages for a feature.
  • Connect a GitHub MCP server and ask for a summary of open issues in a specific repo.
  • Connect an analytics MCP, such as Amplitude or a custom metrics service, and ask the chat to pull recent product metrics into the conversation while you plan changes.
Learn how to add and manage MCP servers in Using MCP connections.

​
Setup and management

This section covers shared setup tasks that apply across multiple integration types.

​
Activating backend functions

To use external integrations that rely on backend functions, you need to activate backend functions in each app.
To activate backend functions:
  1. Go to your app’s editor.
  2. Click Dashboard.
  3. Click Settings.
  4. Click App Settings.
  5. Click Activate next to Backend Functions.
Activating backend functions in your Base44 app
Each backend function has a code file you can edit, view, and test. You can also check logs for each function. To manage your functions, go to Dashboard → Code → Functions.

​
Adding an integration

You can add integrations or connections at any time while building:
  • Use built-in integrations directly from the chat.
  • Ask the AI chat to add connectors for supported OAuth services.
  • Work with your admin to expose shared APIs as custom OpenAPI integrations in your workspace.
  • Use backend functions and Secrets for per-app external APIs.
  • Configure MCP connections in your account settings for the AI chat.
Before adding per-app external integrations, activate backend functions in your app’s dashboard. Custom OpenAPI integrations and MCP connections are managed at the workspace or account level and do not require backend functions.
Looking for quick app connections? Use Connectors for OAuth setup, no API keys required. For APIs your whole team should share, use custom OpenAPI integrations. To enrich the AI chat with external tools, use MCP connections.

Examples of prompts for the AI chat to set up integrations

  • Add an OpenAI integration that summarizes new inputs
  • Connect to Resend to send a welcome email when a person signs up
  • Pull in company data from Airtable
When you request an integration in the AI chat, Base44 guides you step by step and asks for credentials or authorization when needed. It then connects the backend and frontend logic automatically so you can get up and running fast.
Connecting an integration to your app using the AI chat

​
Getting your API keys

Some integrations require an API key, which acts like a private password between Base44 and the external service. Your API key proves ownership and keeps your connection secure. Base44 stores your key safely so your app can use it without exposing it.
Never share your API key publicly. Treat it like a password.
To get your API key:
  1. Log into the external service (for example, OpenAI, Resend, Notion).
  2. Find the Developer, API, or Integrations section.
  3. Click Create API Key or Generate Token and copy it.
  4. Paste your API key in Base44:
    • Using the AI chat: Enter your API key in the AI chat when prompted.
      Adding your API key in the AI chat in Base44
    • Setting up manually: Save your API key in Secrets.
      a. Click Dashboard in your app’s editor.
      b. Click Secrets.
      c. Click Add Secret.
    Adding secrets in the app dashboard of Base44
Custom OpenAPI integrations also use secrets, but these are configured once by a workspace admin when creating or editing the integration and are stored as encrypted workspace secrets, not per-app Secrets.

​
FAQs

Click a question below to learn more about using integrations.
Custom OpenAPI integrations are configured once in a shared workspace from an OpenAPI spec and are available to every app in that workspace through base44.integrations.custom.call(). Credentials are stored as encrypted workspace secrets and never exposed to app code, and you do not need to enable backend functions to use them.Per-app external APIs use backend functions and Secrets in a specific app. They are ideal for app-specific logic or when you do not want to share an API across all apps in a workspace.
Before publishing your app, test your integration so you can catch issues early:
  1. Use sandbox or test mode (for example, Stripe test keys), if the provider offers it.
  2. Try real flows and edge cases, not just a single happy path.
  3. Check that inputs and outputs match your expectations in your UI and in the provider’s dashboard.
  4. Monitor integration credit usage in both Base44 and the external service.
  5. Preview your app to catch slow loading, failed API calls, or missing data before going live.
If you run into issues, check the following:
  • Backend functions are activated (for per-app external APIs).
  • Your API key is correct and saved in Secrets or in the custom OpenAPI integration, if relevant.
  • You have enough active credits in the external service.
  • You are using live credentials, not test ones, when testing production flows.
  • Your API request includes the correct endpoint, payload, and parameters.
  • You have not hit the service’s rate limits.
To check your balance:
  1. Click your profile icon at the top right of your workspace.
  2. Select Settings.
  3. Click Workspace to view used and remaining credits for the current billing cycle.
You can also view your remaining credits while working on an app by clicking the Base44 logo at the top-left. Learn more about credits in Base44.
No. You cannot update the Users entity directly from a backend function. The Users entity is managed by Base44 to maintain secure and consistent authentication. You can only update custom fields that you add to the Users entity, for example profile metadata, but you cannot update core fields like email or password.
You can enable backend functions for all new apps by default.To enable backend functions for future apps:
  1. Click your profile icon at the top right of your workspace.
  2. Click Settings.
  3. Click the Account tab.
  4. Click the Enable backend functions for new apps by default toggle.
If you see a 403 error when using backend functions, it may mean backend functions are not available for your app or workspace, or the request is missing permissions.Common causes and fixes:
  • Plan requirement: Backend functions are only available on the Builder plan or higher. The app owner must have a Builder plan or higher and must enable backend functions in App Settings.
  • Feature not enabled: Even if your plan is eligible, you must enable backend functions in your app’s dashboard.
  • Still having trouble: After checking both, see the Troubleshooting Issues article or contact Base44 support.
There are 2 types of API keys you may need to regenerate or update:
  • Third-party service keys: Regenerate your key in that service’s developer portal, for example OpenAI, Resend, Notion, then update it in Dashboard → Secrets or in your custom OpenAPI integration settings.
  • Your Base44 account API key:
    1. Click your profile icon at the top right of your workspace.
    2. Select Settings.
    3. Click Account.
    4. Click Regenerate next to API Key.
Once regenerated, your Base44 API key updates across all of your Base44 apps automatically. If you have added your Base44 key in another service, update it there as well.
  • Built-in integrations remain available.
  • Connectors, custom OpenAPI integrations, MCP connections, and per-app external APIs that rely on backend functions may stop working until you upgrade to a Builder plan or higher.
Yes. You can mix built-in integrations, connectors, custom OpenAPI integrations, and per-app external APIs in the same app, as long as your plan and settings support them.
For security reasons, external services like Stripe, OpenAI, or Notion do not let third parties, including Base44, access your credentials automatically. Instead, you need to:
  1. Log in to the service.
  2. Go to the API or developer section.
  3. Generate your key.
  4. Paste it into Base44 as a Secret or workspace header.
Once added, your app or custom OpenAPI integration can use that key behind the scenes safely and without code.
Why this matters: API keys act like passwords for services. Keeping them private and under your control keeps your data safe and ensures only you authorize access.
No. MCP connections are only for the Base44 AI chat while you build. They are configured at the account level under Settings → MCP Connections and are used only when your prompt requires that MCP server. Your deployed app does not call MCP servers through this settings page.
Still need help? Join our Discord and get real-time support from the Base44 team and community.