The Base44 Cheat Sheets

Base44 is a backend as a service (BaaS) platform combined with an AI powered app builder. It provides: Backend: Auth, database (entities), i

Layer Technology Frontend framework React 18 Build tool Vite Styling Tailwind CSS + design tokens (CSS variables) UI components shadcn/ui (R

The app is a standard Vite + React project. Files live in specific directories: src/ ├── pages/ React page components (.jsx, subfolders ok)

The Base44 builder interface has two panels: Left: Chat interface where the user communicates with the AI builder. Right: Live app preview t

Pages React components exported as default, named same as their file. A page without a <Route in src/App.jsx is unreachable. Main/home page

Main/home page on "/" only — no second route under the component name. Changing the main page: the "/" route in src/App.jsx is the source of

Token based design system src/index.css owns token values; tailwind.config.js maps tokens to Tailwind classes. Theme changes: update values

Installed packages (only these can be used): Frontend: React 18, react dom tailwind css shadcn/ui (all components in @/components/ui/ ) luci

Auth pages ship in English. When the user's language differs: Translate visible strings proactively. Preserve every flow step (register → OT

Base44 provides several backend primitives: Primitive Description Entities JSON schemas defining stored data (the database) Functions HTTP h

Backend functions are HTTP handlers in base44/functions/{functionName}/entry.ts , for external APIs with no built in integration. Integratio

The SDK client is pre configured inside Base44 apps — just import it: js import { base44 } from "@/api/base44Client"; For external apps (non

Beyond the built in Core integrations, the SDK supports custom workspace integrations: js base44.integrations.custom.call(slug, operationId,

In backend functions with service role, generate SSO access tokens for users: js const token = await base44.asServiceRole.sso.getAccessToken

Code passes Deno lint validation before deployment. Rejected (blocks deployment): Syntax errors Missing imports Unmatched brackets/braces Wr

Execute JavaScript in the app's Node.js CommonJS sandbox (not the Deno runtime used by backend functions). Key rules: base44 is pre initiali

Entities are JSON schema objects defining stored data. Each entity is a .jsonc file in base44/entities/ . Built in attributes (never declare

js import { useEffect } from "react"; import { base44 } from "@/api/base44Client"; useEffect(() = { // event: { id, type: 'create' 'update'

Apps can have two separate databases : Production and Test. By default, data operations use the Production database. To operate on the Test

Import data from CSV, Excel, or JSON files into entities: import_data(entity_name, file_url, sheet_name?) APPENDS new records — does NOT upd

The platform owns the auth backend entirely — never implement auth backend logic . Auth pages (pre existing, never recreate) src/pages/Login

js await base44.users.inviteUser("foo@gmail.com", "user"); // email + app role "user" or "admin" Rules: Public app: admins invite both roles

Built in integrations are always available via base44.integrations.Core . No API keys required. js import { base44 } from '@/api/base44Clien

AI agents are JSON config files in base44/agents/ . Delete the config file to delete an agent. Agent config: jsonc { "description": "This is

When an in app agent needs missing entity permissions, a backend function it should call, or an app user connector it should create connect

Workspace skills are loadable instruction sets that provide step by step guidance for specific tasks. Activate with: activate_workspace_skil

Workspace skills provide step by step instructions for specific tasks. Activate with activate_workspace_skill(skill_name) . Maximum 3 active

The "Super Agent" is the AI builder you chat with in the Base44 editor — the agent that writes your entities, pages, functions, and automati

Custom instructions are standing rules the AI builder follows on every message — set once in your app's dashboard settings, applied forever.

A practical end to end recipe for shipping an in app AI agent your users can actually talk to. Step 1 — Define the agent An agent is a JSON

Workflows are trigger driven automated processes — from one step (scheduled function call) to complex (multi step, switch branching, durable

App connectors integrate the app with external services via OAuth. Three connector types: Type Description Shared Builder connects their own

request_oauth_authorization Requests OAuth authorization from the app builder for a third party integration. Two modes: SHARED mode (platfor

Automations run backend functions automatically — no user action required. They are the "when X happens, do Y" engine of Base44. The four au

Analytics Track custom events with base44 from '@/api/base44Client': js base44.analytics.track({ eventName: "user_contact_form_submit", prop

When the user wants to accept payments, donations, sell products, or set up billing, and no payment integration is configured: 1. Check <ava

Two GitHub features exist: 1. 2 way repo sync — sync the Base44 app with a GitHub repository. 2. GitHub connector — build features on GitHub

Apps are hosted on the Base44 platform. Publish to iOS/Android from the same React codebase. For local development: Full stack: base44 dev F

General: Before editing, account for dependent files, earlier changes, and the user's own edits. Export every page/component as default, nam

Backend functions: test_backend_function('myFunction', payload={param: "value"}) — returns response + logs (logs catch logical errors even o

Entity files: Always use write_file (full schema) — never find_replace on .jsonc entity files. Never declare built in attributes ( id , crea

The Base44 AI builder has access to these platform tools: File operations: read_file(file_path, offset?) — read a file (use read_file for up

Response pacing: When the first message instructions require a user facing plan, make it the first visible output. Use one sentence or at mo

The Base44 AI builder follows these core operating principles: Action over discussion: Act on concrete requests (build/add/change/fix → impl

Use ask_clarifying_questions when the user's request lacks specific details (WHERE, WHAT, or HOW). When to use: "add a button" → WHERE shoul

Tool selection: Tool Use case find_replace DEFAULT and PRIMARY for modifying existing code files write_file New files, full rewrites, entity