Notion destination
Sync your categorised transactions into a Notion database
Fin creates a Notion database inside a page you choose and keeps it filled with your sorted transactions — as typed properties, so Notion’s own filters, views, rollups and relations work on them from the first row.
Notion
What does the Notion destination do?
It creates a database inside a Notion page you nominate, and adds each categorised transaction to it as a row with typed properties — date, number, category, tax treatment and receipt reference.
The database lives in your Notion workspace, next to whatever else you keep there. That is most of the reason to choose Notion over a spreadsheet: transactions stop being a file you open separately and become something you can relate to a client page, roll up into a project, filter into a board, or drop into a monthly review as a linked view.
Each row is a real Notion page, so it opens. You can write notes inside a transaction, attach context, or link it to anything else in your workspace — none of which a grid of cells can do.
How do you connect Notion to AI2Fin?
You authorise the AI2Fin integration on Notion’s own screen and choose exactly which pages it may see. Notion’s access model is per-page, so the integration only ever sees what you shared with it.
That is different from the spreadsheet providers, and simpler in one respect: there is no list of permissions to weigh up. Notion has no scopes to narrow — you pick the pages, and the pages you pick are the whole boundary.
You can change what is shared, or remove the integration entirely, from Notion at any time. Anything already written stays in your workspace; it is your database.
What you are agreeing to on Notion’s screen
Only the pages you tick
Notion’s consent screen asks you to select which pages or databases the integration may access. Nothing outside that selection is visible to it, and there is no wider permission to grant even if you wanted to.
Enough to build the database
Inside the page you nominate, the integration creates the database and adds the nine properties. It does not go looking anywhere else in your workspace.
Nothing is read back
The connection exists to write your transactions in. It has no reason to read your other content, and you can confirm the boundary yourself from Notion’s connections settings.
Which Notion page does the database get created in?
One you choose during setup. Notion creates databases inside a page rather than at the top level of a workspace, so nominating the parent page is genuinely part of setting this up.
The picker shows both: databases you already have that could receive rows, and pages a new database could be created inside. Only pages you shared with the integration appear, and your existing transaction rows are filtered out of that list, since offering them as places to put a new database would be noise.
If no page is chosen, Fin stops and asks rather than picking one for you. Putting your financial data in a page you did not choose is not a reasonable default, so it is not one.
A database has to live inside a page you shared
Notion does not let an integration create a database at the top level of a workspace, and Fin can only see the pages you ticked on the consent screen. So if the page you had in mind is not in the list, the fix is on Notion’s side: share that page with the AI2Fin integration, then come back and it will be there. Nothing needs reconnecting.
Why is each transaction a page rather than a spreadsheet row?
Because that is what a Notion database row is. Each transaction becomes a page with typed properties, which is what makes Notion’s filters, grouped views, calendars, rollups and relations work on your transactions immediately.
The types are chosen rather than defaulted, and it matters. Everything-as-text is the easy option and it throws away the reason to pick Notion at all: a text amount cannot be summed or rolled up, a text date cannot drive a calendar view, and a text category cannot be grouped.
Fin also fits itself to a database you already had. If you point it at one of your own, it adds only the properties that are missing, by name — it never renames, retypes or removes a property you created. Before each push it reads the database’s current schema and writes each value in the shape that database actually expects, so a column you converted later keeps working.
| Field | Type | Why |
|---|---|---|
| Description | Title | Notion allows exactly one title per database; the description is the column that reads like a row’s name. |
| Date | Date | Sortable, and usable as a calendar or timeline view. |
| Merchant | Text | Free text, because merchants are high-cardinality — a select would grow forever. |
| Amount | Number | The summable one. This is the point of typing it properly. |
| Currency | Select | A tiny closed set, so it groups — and “AUD” cannot become two things by typo. |
| Category | Select | Group-by and filter-by is most of what this database gets opened for. |
| Tax deductible | Checkbox | Genuinely boolean, and filterable as one. |
| Tax category | Select | A small closed set, same reasoning as Category. |
| Receipt | URL | Clickable, rather than a string that looks like a link and is not. |
Select options fill themselves in from your real data on first use, so nothing is seeded with guessed category names. One honest note on the checkbox: a Notion checkbox cannot be blank, so a transaction nobody has assessed yet shows as unticked in a Fin-built database — where the spreadsheet destinations can leave that cell genuinely empty.
Which of your transactions get sent to Notion?
The ones you entered yourself, imported from a CSV, or captured from a receipt — categorised, tax-tagged and receipt-linked before they land. Transactions that arrived through a connected bank feed stay inside AI2Fin, where your reports and your tax view still count them.
It works the same way for every destination, so the file you keep in Notion carries the records you assembled. The reasoning behind that, and what it means for a file you share with your accountant, is on the Destinations overview.
Would another destination suit you better?
The same nine fields go to all four, so the choice is about where you already work rather than about what you would be giving up.
Transactions to Google Sheets
Connect your own Google account, let Fin create a fresh spreadsheet or reuse one you have already opened with AI2Fin, and your categorised transactions land there as rows — kept updated on a schedule, or pushed the moment you ask.
Transactions to Microsoft Excel
Yes — into a real .xlsx workbook in your own OneDrive. Sign in with your Microsoft account, have Fin create the workbook, and rows append into it on a schedule or on demand.
Transactions to Airtable
Yes. Authorise AI2Fin from Airtable’s own screen, choose where the table should live, and your categorised transactions arrive as records.
The Destinations overview compares all four side by side and covers what every push has in common. Outbound Destinations is included on the ELITE+ and AUTO+ plans — see what each plan covers.
Notion, answered
Common questions about the Notion destination
- Why does each transaction become a Notion page instead of a spreadsheet row?
- Because a row in a Notion database is a page — that is Notion’s own model rather than a choice Fin made. It works in your favour: each transaction opens, so you can write notes inside it, attach context, or relate it to a client, project or invoice page elsewhere in your workspace. The trade is that adding rows is one call per transaction rather than one call for the batch, so a very large first import takes longer here than it would into a grid.
- Can Fin add its columns to a Notion database you already built?
- Yes. Point it at your own database and it adds only the properties it cannot already find, matched by name, then leaves everything else exactly as it is — nothing you created is renamed, retyped or removed. Where your database already has a title property under your own name for it, the description is added as an ordinary text property instead, since Notion permits only one title per database.
- Do Notion filters, rollups and calendar views work on the transactions?
- Yes, straight away, because the properties are properly typed rather than dumped in as text. The date is a real date, so a calendar or timeline view works. The amount is a real number, so a rollup or a sum works. Category, currency and tax category are selects, so grouping and filtering work. Tax deductible is a checkbox, so you can filter to deductible spend in one click.
- What happens if you un-share the Notion page after connecting?
- The next push stops and tells you the page is no longer shared with AI2Fin, rather than failing silently. Nothing already written is affected — the database and every row in it stay in your workspace, because they belong to you. Re-share the page in Notion and the next push carries on from where the last one finished.
Your transactions, in your Notion workspace
Getting your transactions sorted and categorised is the free part. Turn on the Notion destination when you want them arriving as a properly typed database you can build views on.
Get 2Fin free