Automation overview

Automation keeps your data current without manual work. Boost.space gives you three complementary kinds — and one conversational way to build them all:

	Native actions & triggers	Code automations	Make scenarios
What runs	Notification, email, webhook	Your own Python, in a secure sandbox	Flows on your connected Make account
Good for	Reacting to record changes and schedules	Any logic you can express in code	Moving data between Boost.space and 2,600+ apps
Set up in	Actions & triggers	Code automations	The Connect / Enrich / Share views

Native actions and triggers

A trigger fires the automation — when a record is created, updated, or deleted (scoped to a module, optionally specific spaces), or at a scheduled time (minutes to months, or once). An action is what runs: a system notification, an email, a webhook — or code. See Actions and triggers.

Code automations

The most powerful action is your own: a Python script running in a secure, isolated sandbox against your data, with credentials kept in a secret vault that never leaks into code or chat. Write it by hand, or don't write it at all — see the vibecoded path below. Full guide: Code automations.

Vibecoded: built by describing

You don't have to configure any of this by hand. Tell the Agent Chat what should happen — "every Monday at 8:00, summarize last week's orders and email me" — and the agent creates the automation, wires the trigger, writes the code, stores the Secrets, tests it, and deploys. It can also list your automations, edit them, run them, and read their logs when something needs a look. The same works from any agent connected over MCP.

Make scenarios

For moving data in and out of other apps, Boost.space connects to Make. You link your own Make account once, then build scenarios that import data into a module, enrich existing records, or share data out — surfaced directly on the module as the Connect, Enrich, and Share views. See Make scenarios and views.

Keeping data clean

Every kind of automation writes to the same records, so consolidation matters: the key field decides whether incoming data updates a record or creates one, and API token prioritization decides which source wins when values conflict.