Using Basemind

Application builder

The application builder turns your tables into web applications: internal tools, client portals, directories, forms or complete websites. Applications are built visually and published on a domain.

Concepts

Concept Description
Application A set of pages with shared settings, theme and integrations.
Page A URL path such as / or /orders/:id, with optional path and query parameters.
Element A building block on a page: heading, text, image, button, link, table, repeat, form, input, choice, record selector, container columns, menu, header/footer, iframe…
Data source A query that loads rows (list rows / get row) from a table for a page or for all pages.
Integration The connection used by data sources and actions, e.g. Local Basemind (acts with your permissions), SMTP, HTTP, AI.
Workflow action What happens on a click or form submit: create/update/delete a row, send an email, open a page, log in/out, call an HTTP endpoint.
User source A table of end users who can log in to the application.

Build your first page

  1. Sidebar → + New → Application, give it a name.
  2. On the empty home page, click + and add a Heading element.
  3. Open Data (top bar) and add a data source of type List multiple rows, choosing the integration, database and table.
  4. Add a Table element and pick the data source. Choose which fields become columns.
  5. Click Preview to try the page.

Formulas in the builder

Most element properties accept formulas. Click the input and pick data from the side panel:

  • Data source – values of the current page’s data sources.
  • Page parameter – values from the URL, e.g. id on /orders/:id.
  • Current record – inside repeat and table elements.
  • Form data – values of input elements on the page.
  • User – the logged-in end user.

Example: a heading showing Order # followed by the order number of the row loaded by a Get single row data source filtered on the page parameter id.

Forms and actions

  1. Add a Form element with input elements inside (text, choice, checkbox, date, file, record selector).
  2. Open the Events tab of the submit button and add Create row.
  3. Map each field of the table to a form value.
  4. Add more actions, e.g. Notification or Open page.

Login and visibility

  1. Create a table of users with email, name and password fields.
  2. Application settings → Users → add a user source for that table.
  3. Add a Login element.
  4. For each element, the Visibility tab chooses who sees it: everyone, logged-in visitors, logged-out visitors, or visitors with certain roles. Page visibility works the same way.

Theme

Application settings → Theme sets colors, fonts, button and input styles, page width and background. Every element can override the theme.

Publishing

  1. Application settings → Domains → add either a subdomain of the server’s builder domain (e.g. shop.apps.example.com) or a custom domain you own (point a DNS CNAME to your server).
  2. Click Publish in the top bar and choose the domain.
  3. Publish again after each change; the live site does not change until you do.

Agents can do the same with the publish_application MCP tool.