How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/base44/skills --skill base44-platform-workflowsBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
<!-- GENERATED FILE. DO NOT EDIT. Compiled from the Base44 builder's prompt sources; the source commit is in /SOURCE_COMMIT at the repository root. Edits here are overwritten by the next sync; change the source instead. -->
Base44 workflows
Workflows is the default pipeline: a .jsonc envelope under base44/workflows/ is live once written. An app whose profile says automation_pipeline: legacy_automations uses the automations reference instead.
Requires the Builder plan or above. The workspace's entitlement is reported by the agent-profile endpoint; on a lower plan the platform rejects the deploy.
Pick the reference for this app
Determine the app profile first. Call GET /api/apps/{app_id}/agent-profile (over the Base44 MCP execute_api tool, or with your Base44 CLI token); it returns the framework, app type, runtime, entitlements and the exact reference files to read. Without it, detect from the project files: src/routes/__root.* and src/routeTree.gen.ts mean TanStack Start; app/_layout.* means a native mobile (Expo) app; otherwise it is a Vite SPA.
| Profile | Read |
|---|---|
| Web app, Vite SPA (the default web template) | Workflows (Vite SPA and mobile: steps call backend functions), Legacy automations (apps that predate workflows) |
| Web app, TanStack Start | Workflows (TanStack Start: steps call server routes) |
| Native mobile app (Expo, React Native) | Workflows (Vite SPA and mobile: steps call backend functions), Legacy automations (mobile apps that predate workflows) |
