Base44 AI agents and integrations: what they do, and what moves when you leave

The short version

Base44 agents are AI assistants that live inside your app. Each one can read and change records in the tables you allow, call your backend functions, search the web, follow your instructions, remember things between conversations, and talk to people on WhatsApp, Telegram or LINE as well as in the app. Every message uses integration credits: about 3 per message on the default model, as of October 2026.

Base44 integrations connect your app to everything else, and come in three kinds: built-in services that Base44 runs for you (AI calls, email, file uploads), connectors that sign in to tools like Gmail or Slack, and your own API calls from backend functions, such as Stripe or Twilio.

When you move an app with Unbase44, its agents move with their settings and conversations, and remember from the move on. AI runs on your own key, email goes through your own Resend account or SMTP server, files go to your own storage, connectors and secrets come along, and the switch-over helps move Stripe, PayPal, Twilio and Telegram webhooks. A few services that Base44 runs at the platform level need their own plan. This article covers what each piece is and where it ends up. Workflows have their own article: migrating Base44 workflows.

What Base44 agents are

An agent is a chat assistant with access to your app. Base44’s guide to setting up an AI agent gives examples: “mark my booking as done” makes the agent update a record, and a general-knowledge question makes it search the web. You create one from Dashboard, Agents, from a template or from scratch, and agents are available on every plan, including Free.

Don’t confuse these with Superagents, a separate Base44 product: assistants that work across your workspace and your tools rather than inside one app (Building a Superagent). This article is about agents in your app.

What an agent can do

• Use tools. Entity tools let it read, create, update or delete records in the tables you choose, operation by operation. Function tools let it call your backend functions, to send a notification or call an outside service.
• Follow guidelines. A description, detailed instructions, and up to 10 context files such as price lists or policies.
• Run on a model you choose. The default, Automatic, is Base44’s pick for fast, low-cost answers. As of October 2026 you can also choose Google Gemini, OpenAI GPT, Anthropic Claude or GLM models, which cost from about the same to many times more per message (Supported models).
• Use skills. Reusable instruction sets, such as a refund policy or a brand voice, up to 10 per agent.
• Remember. Memory is on by default for new agents. It can be shared by everyone, kept per user, or both, and the agent condenses older memories at around 50,000 characters.
• Act for each user. User connectors let each person link their own account, such as their Google Calendar, from inside a conversation.
• Talk to visitors. Anonymous access, off by default, lets people chat without signing in, with no access to per-user data.

Agents on WhatsApp, Telegram and LINE

Base44 can connect an agent to messaging apps, with the same abilities it has in your app. As of October 2026:

• WhatsApp is free on all plans, for up to 3 in-app agents across all your apps. Base44 assigns each agent its own number. Each message sent or received uses 1 integration credit for the relay, plus whatever the agent does. People have to send the first message.
• Telegram connects the agent to a bot; people open it and send /start.
• LINE is available only in Japan, with plain-text replies.

WhatsApp and Telegram agents can also work in group chats, with all credit usage billed to the app owner.

What agents cost

Each message to an agent uses integration credits from your workspace’s monthly pool. Base44’s credits page puts Automatic at about 3 credits a message, rising with the length of the answer; other models cost more. Anonymous conversations draw on the same pool, which is why Base44 suggests anonymous access only for agents you want open to everyone.

For developers, agents are JSONC files in base44/agents/, one per agent, synced with base44 agents pull and push (About agents).

Base44’s integrations, in three kinds

Base44’s integrations overview sorts app integrations like this:

Two more sit outside a single app: custom OpenAPI integrations, which a workspace owner or admin sets up once for every app in the workspace (custom integrations), and App MCP, which lets assistants such as Claude, ChatGPT and Cursor work with your published app’s data and agents (App MCP). Base44’s integrations page is the current catalog.

Connectors come in two types: one connection you make for the whole app, such as Slack alerts to your team’s channel, or one per user, where each person connects their own account (Connectors overview).

Email

SendEmail is built in. On any plan your app can email anyone who has signed up to it; emailing other addresses needs a paid plan and a verified custom domain. It can’t send attachments or to mailing lists, and uses about 1 integration credit per email, or about 2 from a custom email domain. For more volume or control, Base44 connects to Resend on the Builder plan and up, or to another provider through a backend function (Sending emails from your app).

Stripe and other payments

Since January 2026, you set up Stripe from the AI chat on the Builder plan and up. Base44 starts you in a Stripe test sandbox, which you claim with your own Stripe account within 60 days; Base44 then creates your live keys, or you paste your own (Setting up Stripe). Base44 registers the webhook endpoints with Stripe itself, and its docs say you can’t repoint them (Apps API: payments). Base44 also recommends confirming a payment on the success page rather than relying on webhooks alone. Separately, Base44 Payments powered by Wix handles cards, wallets, payouts and refunds inside Base44 (Base44 Payments).

Some apps call Stripe directly from a backend function instead, with their own keys as secrets and a webhook pointing at that function. That kind of integration is code in your app.

What moves with Unbase44

The backend that runs your moved app speaks Base44’s API and serves the AI and email integrations, file storage and agents, so the app’s code needs only a few small patches, listed in the repository’s docs/MIGRATION.md. Your free analysis lists your app’s agents, functions, workflows and files before you connect any account or pay. Start it here.

Test mode while you check

The new copy starts in test mode, next to the Base44 app that keeps serving your users. It runs no automations or workflows, and anything it would send out, such as emails, texts, notifications, payments or changes to other services, is held and logged instead. You can talk to each agent and run each function without a customer getting a message.

Parts to plan separately

Some services belong to Base44’s platform rather than to your app’s code. If your app relies on one of these, plan for it before you move your users, and try it on the new copy in test mode:

• Base44’s messaging channels for agents. The WhatsApp number is one Base44 assigns, and LINE runs through Base44’s bot.
• Payments that Base44 runs: the built-in Stripe setup, whose webhooks Base44 registers and you can’t repoint, and Base44 Payments powered by Wix.
• Push notifications to Base44’s native mobile builds. One-click mobile builds after the move are coming soon.
• Workspace-level pieces: custom OpenAPI integrations and App MCP.
• Base44’s media generators for images, video and speech.

Checking agents and integrations before you switch

• Ask each agent the questions your users ask, on the old app and the new copy. Choose the model on your own key deliberately: Automatic is Base44’s choice, and Base44’s own docs note that answers change in style and quality when the model does.
• Check each agent’s tools. Its table permissions should still be the narrowest that work.
• Run every function that calls an outside service and read what test mode held back.
• List your incoming webhooks from each provider’s dashboard: Stripe, PayPal, Twilio, Telegram and anything else that calls your app. The switch-over helps move Stripe, PayPal, Twilio and Telegram webhooks to the new address; any others you change yourself.
• Check workflows that start from an agent conversation; the workflows article covers triggers and schedules.