Code automations, without the fixed menu
A new Code action lets an automation run your own Python in a secure, isolated sandbox. Credentials stay in Secrets rather than inside the script, so the step can do exactly what your workflow needs without exposing the values it depends on.
Build it your way
Describe the automation in Agent Chat and it can write the code, connect the trigger, store the Secrets, test it against your data, fix what fails, and deploy it. Your own agent can build the same flow over MCP, or you can write the Python yourself in the editor when you want full control.
Rollups turn linked records into answers
The new Rollup field aggregates a value across linked records. Total the value of a company’s deals, count how many are still open, or show the latest order date for a customer without maintaining another calculation by hand. Rollup fields are available on higher plans.
Formula fields, rebuilt
The Formula editor now inserts fields as clear chips instead of raw text and validates your formula while you write. The expanded function library covers math, logic, text, dates, arrays, conversion, and record metadata. Formula fields are available on higher plans.
Start automations at the right moment
Scheduled triggers handle time-based work, while filters on Created, Updated, and Deleted triggers keep an automation focused on the records it should process. Custom fields are now available in the Record-updated trigger too.
Large modules only load what changed
When you return to a large module, Boost.space fetches the records that changed since your last visit instead of loading the entire table again. The result is a faster return to the work already in progress.
Choose what AI can retrieve
Vectorization can now be switched on or off per system, space, and field. That gives you control over exactly what becomes available for semantic retrieval. These controls are rolling out to selected systems.
Also in this release
- Record-update webhooks now include the data that changed, and high-volume webhooks can batch their deliveries.
- “Custom modules” are now simply “modules” across the product, API, and MCP server. The old API routes remain available as deprecated aliases while integrations move to the new field routes.
- Move a field group to another view directly from its context menu.
- New modules receive a default logo and icon and appear in the menu as soon as they are created.
- Invite an administrator while a system is being created.
- Permissions selected for a new API or OAuth token now apply immediately, without a second save.
- Appflows are hidden on new systems, while existing Appflows remain manageable.
Agent Chat and the MCP server ship on their own cadence. During the same weeks, Agent Chat gained web search, attachment previews, and support for reading spreadsheets and documents. The MCP server moved from v2.2 to v2.3 with automation, menu, status, and label tools.
