Connect Baserow to 360Crafter CMS

Use a Baserow grid view as the data source for a CMS table. Baserow is the most robust source 360Crafter supports: syncs are instant (no publish cache), rows keep a stable identity even when renamed, and all you need is a share link.

Set up the view

1. In Baserow, open the table’s grid view and click Share view.

2. Click Create a public link and copy it. It looks like https://your-baserow.example.com/public/grid/….

3. Optionally, protect the link with a password in the share settings.

The view controls what 360Crafter sees: hidden columns and filtered-out rows are not imported, so you can share exactly the slice of data your tour needs.

Import the view

1. In the CMS, click Add or import → Baserow (shared view).

2. Paste the public link. If the view has a password, enter it in the View password field — it’s remembered, so future syncs won’t ask again.

3. Click Fetch and preview, check the detected field types, and import.

Rich Baserow values come through in a readable form: select options and linked rows arrive as their labels, checkboxes as true/false, and file attachments as URLs.

Linking rows to panoramas or hotspots

A column can become a Linked field: in the preview, set its type to Linked field and pick the target table (for example Panoramas). Fill the column in Baserow with the target’s names — 360Crafter matches them to the actual records on every import and sync. Use commas for multiple links. Names that don’t match anything stay visible as text so you can spot and fix them.

Keeping the table in sync

Open the table tab’s dropdown and click Sync from Baserow. Syncing:

• Updates all columns that come from Baserow. These are marked with a small lightning icon ⚡ in the column header — Baserow owns them, and any edits you made to their cells in the CMS are overwritten.

• Keeps fields you added manually in 360Crafter, including their values. They have no lightning icon and are never touched by a sync.

• Adds new Baserow columns after asking you for their field types, and removes columns you deleted from the view.

Renaming rows is safe

Every Baserow row has a stable internal id that 360Crafter stores during import and sync. Rows are matched by that id, so you can freely rename rows in Baserow without losing manually added field values or breaking links that point at them. (This is a key difference from Google Sheets, where the first column acts as the row key.)

Live data in published tours

By default, exporting a tour takes a snapshot of your table — later Baserow edits don’t affect it until you export again.

To make published tours always show the current Baserow data, enable Keep synced in exported tours — either in the table tab’s dropdown or in the Data Connections overview of the export window. When enabled, each visitor’s browser fetches the view directly from your Baserow server when the tour loads:

• Changes in Baserow appear on the next tour reload — instantly, with no re-export and no publish delay.

• The tour depends on your Baserow server: every visit makes requests to it, and its address (including the view link) is visible to visitors. If it’s unreachable, visitors see the data as it was at export time.

• Turn the option off to go back to static snapshots (takes effect on your next export).

Password-protected views can’t be live

Live sync would ship the view password inside the tour, where any visitor could read it. 360Crafter therefore refuses to enable Keep synced in exported tours for a protected view and asks you to remove the password first (Baserow → Share view settings). Password-protected views work normally for syncing inside the editor — the password just never leaves your project.

Good to know

• Self-hosted Baserow has no API limits — each tour visit costs your server only a couple of small requests. On Baserow Cloud, very high simultaneous traffic could run into its concurrent-request fair-use limit; heavily trafficked tours are better served by a static snapshot.

• Images and audio referenced by URL in a live-synced table load directly from wherever they’re hosted, so use stable, public URLs.

Troubleshooting