Dotwave Import from Notion
Notion databases are a common home for roadmaps, CRMs, content calendars, and operational trackers. Dotwave imports a Notion database as a flat dataset so you can chart it alongside the rest of your data. The one requirement people miss is that Notion never exposes a database to an integration until you explicitly connect them — so this article starts there.
Before you start — set up a Notion integration
Go to notion.so/my-integrations while signed in to the workspace that owns the data.
Click New integration.
Give it a clear name such as Dotwave and select the workspace whose databases you want to import.
Under Capabilities, enable Read content. Dotwave only needs to read; it never writes back to Notion.
Submit the integration, then copy the internal integration token. It starts with secret_ or ntn_. Treat it like a password.
Open each Notion database you want to import, click ··· in the top-right, choose Add connections, and select your integration.
Skipping step 6 is the most common mistake. Dotwave won't see any databases until you explicitly share them with your integration.
Import a database
From the Data sources page, click Add data source and choose Notion.
Paste the secret_ or ntn_ token you copied earlier.
Dotwave lists every database the integration can see — that is, the ones you shared in step 6. Choose the one to import.
Dotwave reads the rows and creates a dataset with one row per Notion page.
Property type mapping
Notion properties are richer than a flat table, so Dotwave maps each property type to a column type:
- title and rich_text → text
- number → number
- select → text
- multi_select → comma-joined text
- date → date string
- checkbox → true/false
- url, email, and phone → text
Limitations
A few Notion behaviors are worth knowing before you build on the imported data:
- A single import returns a maximum of 10,000 rows. For larger databases, filter within Notion or split the data across databases.
- Relation columns show page IDs, not titles. A relation resolves to the related page's ID string rather than its human-readable name.
- Formulas and rollups may lose precision when they are flattened into a single column value.
An integration only sees databases explicitly shared with it, so you can keep the token scoped tightly. If you later need another database, repeat step 6 for that database — there is no need to create a new integration or token.