Base44 Integrations: Connectors, APIs, GitHub and Payments

Base44 connects your apps to outside services in three ways, and the plan decides which ones you get. Built-in integrations for email, AI calls, image generation and file uploads work on every plan, Free included, with no API keys. Connectors that sign in to tools such as Gmail, Slack, Notion or HubSpot, and backend functions that call any API you choose, start on the Builder plan. Builder is $40 per month billed annually or $50 per month billed monthly. GitHub sync, the Base44 MCP server and in-app payments sit behind the same gate. Every built-in call spends integration credits, so size the volume before launch.

Built-in services: what every plan can call without a key

Every new app ships with six preinstalled actions: Invoke LLM, SendEmail, SendPushNotification, UploadFile, GenerateImage and ExtractDataFromUploadedFile. You open no account with an AI or email provider, because Base44 runs these services and bills your workspace in integration credits ^[1]. Invoke LLM can return JSON that follows a schema, read attached files and images, and search the web. The extraction action turns CSV, PNG, JPG and PDF files into structured records. That covers a fair share of small apps: a form that emails a confirmation, a tool that summarizes uploads, a page that draws images on request.

The limits hide in the details. SendEmail reaches anyone who signed up to the app on any plan, but writing to an address that has not signed up needs a paid plan and a verified custom domain. It cannot send to an external mailing list and attaches at most 5 files of 5 MB each, 10 MB in total. Push notifications need the Builder plan or higher and reach only a native store app with push set up. Apps have no built-in action for sending your own text messages; the only texts are MFA sign-in codes for app users, billed in integration credits. For reminders or alerts you add a third-party SMS service through a backend function, which puts you on Builder anyway.

Connectors: one-click sign-ins from the Builder plan

Connectors are OAuth links to outside tools where Base44 stores and refreshes the credentials for you, and they need the Builder plan or higher. The catalog on Base44's integrations page covers Gmail, Google Calendar, Drive, Docs, Sheets and Slides, plus Slack, Notion, HubSpot, Salesforce, LinkedIn, TikTok and Discord. Its developer changelog adds Airtable, Dropbox, Microsoft Teams, Outlook, SharePoint, Google Search Console, Calendly, GitLab, Supabase, Instagram, ClickUp, Wrike, Google Analytics, Snowflake, Databricks, QuickBooks, Google Ads and Square. Mailchimp, Gorgias, Intercom, Zoho CRM, Meta Ads, Klaviyo and Asana followed in July 2026. Each connector flow comes with a backend function you can open and edit.

The real decision is the credential type. A shared connector uses one connected account for everyone in the app, such as a company Slack bot posting alerts. An app user connector lets each person connect their own account, and only workspace owners and admins can set one up. Most app user connectors need your own OAuth client, which puts your brand on the consent screen. Google Calendar alone can let Base44 manage that OAuth, and only on the Pro plan or higher. Reading Gmail content through your own client is a Google restricted scope. Verification can take several weeks.

Triggers make connectors more than outbound calls. Workflows, also a Builder feature, can start from connector events in Gmail, Google Calendar, Google Drive, Outlook, OneDrive and Slack, and connector automations fire backend functions from webhook events in those tools plus Teams and SharePoint. Expect a few quirks per service. LinkedIn does not renew access in the background, so its connections need a manual reconnect now and then. Instagram replies to a direct message must come within 24 hours of the person's last message. The GitHub connector reads pull requests and issues for your app; it does not sync your code.

Your own APIs: backend functions, OpenAPI imports and manual keys

Anything outside the catalog runs through backend functions: serverless TypeScript on Deno, each with its own HTTP endpoint, written for you by the AI chat. They need the Builder plan or higher, and on Free or Starter such calls fail with a 403 error. Paste an API key into the chat and Base44 stores it as an encrypted secret before the AI reads the message. Secrets never reach the browser. One trap catches teams later: a published app keeps the secret values it had at its last publish, so republish after you rotate a key. Functions can call each other in a chain of at most seven.

For services outside the catalog, Base44 does not store or refresh OAuth tokens; your functions do that work. The integrations page lists manual setups for monday.com, OpenAI, ElevenLabs, Twilio, Resend and Zapier, each running on your own account and keys. Zapier also needs a premium Zapier account for webhooks and must be called from the backend, never the browser. A team with an internal API can import its OpenAPI specification as a workspace integration: owners and admins on Builder or higher create it, and anyone in the workspace can use it. The catch is identity. It sends the same sign-in details on every call, so it cannot act as each user.

Integration credits: who spends them and what a call costs

Integration credits are the meter behind everything above. Free includes 100 a month, Starter 2,000, Builder 10,000, Pro 20,000 and Elite 50,000. Base44's own estimates run about 1 credit per email (about 2 from a custom email domain), 1 per upload or generated image, about 1 per LLM call on Automatic and from about 3 on a chosen model ^[2]. An in-app agent message starts at about 3. Workflow steps cost about 1 credit per 10 steps and backend function invocations about 1 per 100, plus whatever each step or function does. No preview shows the cost before an action runs.

Picture a Builder app in an ordinary month: 2,000 confirmation emails, 300 agent messages on Automatic and 50,000 backend function calls. That comes to at least about 2,000 + 900 + 500 = 3,400 integration credits by our arithmetic (more if functions call AI or email, or if emails go out from your own domain), roughly a third of Builder's 10,000. The emails and agent messages alone would overrun the 2,000 a month that Starter includes. Your own keys change the math. Calling Stripe or Google Maps with your own key uses no integration credits, while metered connectors, added in November 2026, bill each call to the workspace pool.

Your visitors spend these credits too. Every email, AI call or image an end user triggers draws on the owner workspace, and an anonymous agent chat counts like a signed-in one. Base44's security scan flags pages where outsiders could burn your credits, and since October 2026 a core integration protection setting forces built-in calls through backend functions. At zero, built-in actions pause until the reset, users see a generic error and a running workflow is canceled, while pages and the database keep working. Credits expire at each monthly reset and cannot be topped up, as our Base44 pricing breakdown explains.

Taking money: Base44 Payments, Stripe and PayPal

Selling inside an app needs the Builder plan or higher, for one-time charges and recurring subscriptions alike. Base44 Payments, powered by Wix, requires a published app and a business with a bank account in one of 13 supported countries, among them the US, the UK, Canada, Switzerland and nine euro countries. Buyers can pay by card, Apple Pay or Google Pay, with PayPal in the US only. Base44's product pages put the Base44 Payments fee at 2.9% + $0.30 per US card sale, though its help page states no percentage. Payouts typically arrive in 2 to 5 business days.

Stripe starts in a test sandbox that you must claim within 60 days by connecting a Stripe account, which then receives the payouts; Base44 creates the live keys once Stripe activates the account. Since November 2026 the SDK payments module also handles PayPal checkouts next to Stripe and Base44 Payments, all from backend functions. Other providers connect through their own API in a backend function, and their sales show only in their own dashboard. Two cautions apply. Subscription renewals may not trigger a payment workflow yet, so do not build fulfillment on renewals alone. Store-wrapped mobile apps cannot sell digital goods.

GitHub, CLI, SDK and MCP for developers

GitHub two-way sync needs the Builder plan or higher ^[3]. Only the app owner connects it, an app built in Base44 gets a new private repository, and changes then sync automatically with no manual push. The default branch must be named main. After connecting, version history restores only versions in the repository, and moving the app to another workspace breaks the sync. ZIP export also starts on Builder. Either way, exported code still reaches Base44's backend through its SDK, Base44 does not support self-hosting that backend, and data, secrets, app users and history stay out of the export.

The CLI, in beta and needing Node.js 20.19 or later, scaffolds, deploys and ejects projects, and the typed SDK gives any frontend access to data, auth, AI and integrations. Each app has an API page with ready code for the JS SDK, fetch, cURL and Python, plus a downloadable OpenAPI spec; personal access tokens replaced account API keys in September 2026, and the old keys have been switched off gradually since October 2026. The Base44 MCP server, Builder or higher, lets Claude, ChatGPT or Cursor create and edit apps. MCP connections inside the AI chat help only while you build, never at runtime, and can raise credit use. Outgoing workspace webhooks need Base44's Enterprise offering, which its help center splits into a self-serve Business plan and a sales-led Enterprise plan; neither price is published.

The bottom line

Base44's integrations split cleanly by plan. Free and Starter get the built-in services, enough for email, AI text, images and uploads, all metered in integration credits that your users spend as well. Once an app needs a connector, an outside API, a GitHub repository or a checkout, the floor is Builder, and moving from Starter to Builder adds $24 a month billed annually or $30 a month billed monthly by our arithmetic. A later downgrade may stop connectors, custom integrations, MCP connections and backend-function APIs, so budget for Builder from the start. Before paying, run the export and data questions through our Base44 buyer's checklist.