Base44 Integrations: Every Way to Connect Your App

Base44 connects to other tools in five main ways: built-in integrations, connectors, backend functions, custom API integrations and MCP connections. Built-in integrations like AI and email work on every plan. Most of the others, including connectors to apps like Slack and HubSpot and custom code that calls services like Stripe, need the Builder plan or higher.

We are a Base44 Legend Partner and connect Base44 apps to payment, phone, CRM and AI voice tools on client projects. This guide is based on the current Base44 integrations docs and what we see in practice.

What integration options does Base44 have?

Plan names and limits come from the Base44 pricing page and docs as of November 2026. Check both before you commit, since they change.

Which Base44 integrations are built in?

Base44 includes a set of integrations you can use right away, just by asking for them in a prompt.

• AI (InvokeLLM): send a prompt to a language model and use the answer in your app.
• Email (SendEmail): send notifications and confirmations.
• Push notifications: alert users on their devices.
• File upload: let users attach files and images.
• Image generation: create images from a text description.
• Data extraction: pull structured data out of uploaded files, such as invoices or forms.

Each use spends integration credits. The free plan includes 100 a month and paid plans include far more, per the pricing page.

What are Base44 connectors?

Connectors let your app act on a user's or your team's account in another service, after signing in with OAuth. The docs list services such as Google Workspace, Notion, Slack, Salesforce, HubSpot, LinkedIn and TikTok. Connectors need the Builder plan or higher.

Typical uses: create a Google Calendar event when a booking is made, post a Slack message when a form is submitted, or add a contact to HubSpot when a lead signs up.

How do you connect Stripe, Twilio or other APIs to Base44?

Use backend functions. These are small pieces of server code that run on Base44's backend, which the docs describe as Deno-based serverless functions written in TypeScript. Your API keys are stored as secrets, so they never reach the browser. Backend functions need the Builder plan or higher.

Common examples we build:

• Stripe: take payments, create subscriptions and update a customer record when a payment succeeds.
• Twilio: send text message reminders or verification codes.
• GoHighLevel: sync leads and appointments with a CRM many agencies already use.
• ElevenLabs: add AI voice features, such as reading content aloud or powering a voice assistant. See our AI voice services.
• Google APIs: read and write Sheets, Calendar or Maps data beyond what connectors cover.

Some services send data back to your app when something happens, through webhooks. A backend function can usually act as the receiving endpoint, but test this carefully for each service, including how it verifies that requests are genuine.

What are custom API integrations in Base44?

If a service publishes an OpenAPI spec, you can add it as a custom integration at the workspace level. Calls are routed through Base44, so the app does not need to handle the credentials directly. Creating a custom integration needs the Builder plan or higher, but apps on any plan, including Free, can use one once it exists.

This is useful for agencies and teams with several apps that all need the same outside service.

Does Base44 support MCP?

Yes. MCP, the Model Context Protocol, is a standard way for AI tools to connect to other systems. On the Builder plan and up, Base44 apps can connect to MCP servers. A published Base44 app can also expose its own MCP server, so AI assistants can work with the app's data, according to the docs.

Can Base44 connect to Zapier or Make?

Base44 does not list Zapier or Make as built-in connectors in the docs we reviewed. You can still link them: a backend function can call a Zapier or Make webhook when something happens in your app, and an automation can call your app through its API. For bigger workflows across several tools, our automation services team designs the whole chain.

What should you watch out for with Base44 integrations?

1. 1Credit usage. AI and email calls spend integration credits. Estimate monthly volume before launch.
2. 2Plan limits. Connectors, backend functions and MCP need Builder or higher. Do not design around a feature your plan lacks.
3. 3Key safety. Keep API keys in secrets, never in the app's front-end code.
4. 4Permissions. A backend function running with admin rights can bypass your security rules, so check who can trigger it. Our Base44 security guide explains why.
5. 5Error handling. Outside services go down. Show users a clear message and log the failure.

When should you get help with Base44 integrations?

Payments, phone systems and two-way syncs with a CRM are where most of the hard bugs live. If your app depends on one of those, a review before launch is cheap insurance. We are a Base44 Legend Partner and can build or check integrations for you. See our Base44 developers page or our AI receptionist work for voice and phone setups.

New to Base44? Start with our Base44 tutorial and Base44 pricing guide.

Roenic Natarelli

Founder, Virtual Horizons

Roenic runs Virtual Horizons and is a Base44 Legend Partner, Ambassador and Community Pillar, Base44 Shark Tank winner and multiple-time Vibe Sprint winner. The studio builds web and mobile apps, AI voice agents and automations, with more than 10 apps live on the App Store and Google Play. More about us