How to create a Baserow database token
A database token is how Baseify writes Shopify data into Baserow. Here's how to create one with the right scope and permissions, and add it to the app — about five minutes.
A database token can read and write rows but cannot browse your schema. If you also want to pick databases, tables and fields from inside Baseify, add your Baserow account credentials as well — optional, and used only to mint short-lived browsing sessions.
Create a token in five steps
Open database tokens in Baserow
In Baserow, open your workspace settings and find Database tokens (sometimes labelled API tokens). This is where you create tokens that can read and write rows over the REST API — which is exactly what Baseify uses.
Create a token scoped to one database
Create a new token and scope it to the single database Baseify will write into — not your whole workspace. Keeping it scoped limits what the token can touch if it’s ever exposed.
Grant create, read, update and delete
Give the token create, read, update and delete permission on that database. Baseify needs all four: it inserts new rows, updates changed ones, and removes rows when records are deleted in Shopify. A read-only token will fail with “permission denied”.
Copy the token
Copy the token value now and store it somewhere safe — Baserow may only show it in full once. You won’t need to paste it anywhere except Baseify.
Add it to Baseify
In the Baseify Baserow tab, add a connection: paste your Base URL and the token, give it a name, and click Save & test. Baseify encrypts the token at rest and only ever shows its last four characters.
Keep the token safe
Because a self-hosted Baserow is reachable over the internet, the token is the main thing protecting your data — so scope it to one database rather than handing over workspace-wide access. Baseify stores it encrypted (AES-256-GCM) and shows only the last four characters back to you. If a token is ever exposed, revoke it in Baserow and add a new one in the app.
“Permission denied” when syncing
Almost always a scope problem: the token is missing one of create / read / update / delete, or it’s scoped to the wrong database. Fix the scope in Baserow, re-test the connection in Baseify, then retry the failed events from the event log.
Related: Self-hosted Baserow · Connect Baserow (docs) · Sync orders