Connects from Settings → Integrations · read-only · disconnect any time
What you get
What Fynex does with Notion
Fynex reads from Notion and does the finance work on top; it writes nothing back.
One database, read as jobs
Pick the database — clients, projects, jobs. Each page becomes something invoices, payments and payouts can be tied to.
Follows the database
Add a page, rename it, change a property: Notion tells Fynex and the job list updates without an export.
Matched to the money
An invoice paid, a contractor paid out, a bill due — each lands against the right page, so you see the money per job.
Read only
Fynex reads what you shared and writes nothing to Notion. Your workspace stays exactly as your team keeps it.
How to connect
Connect it in three steps
Done once, from the dashboard, by whoever owns the account.
1
Approve Fynex
OAuth — you sign in to Notion and choose which pages Fynex may see.
2
Choose the database that holds your jobs or clients
Fynex lists what your account can see; pick the database that holds your jobs or clients. One choice per connection, changeable later.
3
Let it run
Notion notifies Fynex when a page changes; Fynex verifies the notification and resyncs on a schedule.
Reads and writes
What Fynex reads, and what it writes
Read from Notion: pages in the database you chose, with their properties.
Written to Notion: nothing. This connection is read-only — Fynex keeps its own record of what happened to the money and shows it on the dashboard.
Clients · NotionSynced
Harbor Ltd2 invoices · 1 paid
£4,200
Elm Studiooverdue 12 days
£1,850
Northgatedeposit received
£600
Page addedRidge & Co → new job
—
Security
How the connection is held
The same three rules on every connection Fynex makes.
OAuth, never a password
You approve Fynex inside the provider's own sign-in. Fynex holds an access token, not your credentials, and you can revoke it from either side.
Tokens encrypted at rest
Every connection token is stored encrypted (AES-256-GCM) with a key that never leaves the Fynex environment. One connection per business per provider.
Every write is logged
Where Fynex writes back, the write is recorded with what changed and why — only after the underlying event actually happened, never speculatively.
FAQ
Questions, answered
Through Notion's OAuth. From Settings → Integrations you sign in, choose which pages Fynex may access, then pick the database that holds your jobs or clients. The token is stored encrypted.
The pages in the database you chose and their properties. Each page becomes a job or client that invoices, payments and payouts are matched to. Changes arrive by notification, verified before use.
No. The Notion connection is read-only today. Fynex keeps its own record of what happened to the money per page and shows it on the dashboard.
The one your team already keeps: clients, projects or jobs. If you track work in several databases, connect the one a payment most naturally belongs to.
Yes, from Settings → Integrations, or by removing Fynex from your Notion workspace's connections. Nothing in Notion changes.
We do Fridays so you don't have to.Payouts at midnight. You, asleep.Invoices that chase themselves. Ruthlessly.We carry the chargebacks. You carry on.We do Fridays so you don't have to.Payouts at midnight. You, asleep.Invoices that chase themselves. Ruthlessly.We carry the chargebacks. You carry on.We do Fridays so you don't have to.Payouts at midnight. You, asleep.Invoices that chase themselves. Ruthlessly.We carry the chargebacks. You carry on.
Nothing to copy across — the finance side follows the database
Essential cookies keep the site working. With your OK we also use analytics cookies (PostHog and Google) to see how the site is used and improve it. See our Cookie Policy.
