Views: Connect, Enrich, Share, Flow
Automation between Boost.space and other apps runs on Make — you connect your own Make account, and your scenarios run there against your Boost.space data. Rather than hiding those scenarios away, Boost.space surfaces them on the module itself as a set of Views, each one a direction of data flow. Switch views from the toolbar; each lists the relevant scenarios as nodes you can open, edit, or add to.
Views appear for admins on a module that's connected to Make. Everyone else works in the data (Organize) view.
The views
| View | What it shows | Direction |
|---|---|---|
| Organize | The normal data table (and Kanban, etc.). | — |
| Connect | Scenarios that import data into this module. | External app → Boost.space |
| Enrich | Scenarios that augment existing records. | Boost.space → app → Boost.space |
| Share | Scenarios that export data out of this module. | Boost.space → external app |
| Flow | A single diagram of every scenario and connection wired to the module. | The whole picture |
Adding or editing a scenario from any view opens the Make editor; the finished scenario appears as a node in that view. Each scenario uses connections — authenticated access to the external apps it reads from and writes to.
Connect your Make account
Link your Make account once — during onboarding, or in System settings → Integration:
- In Make, create a Make API token.
- Paste it into Boost.space and choose your team / organization (and hosting region, if asked).
- Save. Your modules can now use Make scenarios, and the views above appear.
Keeping incoming data clean
Connect and Enrich scenarios write into your records, so consolidation matters. The key field decides whether an incoming record updates an existing one or creates a new one, and API token prioritization decides which source wins when values conflict — you set both from the Flow view. (The Share view exports data out, so it has no consolidation settings.)
Import a file instead
Bringing in a one-off file rather than an ongoing sync? Use Import data from a file — it maps columns to fields with AI, no scenario needed.
Going deeper
Building complex scenarios, working with specific apps, and the app marketplace are covered in the automation & app documentation.
