Sync Supabase to Fortnox — Without Code
Push your Postgres data into Fortnox without writing sync jobs, schedulers or webhook glue.
No sync code to write
Skip the schedulers, webhooks and retry logic. Ziikly maps your Supabase rows to Fortnox invoices and runs the sync for you.
Always-fresh invoices
You choose when the sync runs — on a schedule or on demand — so Fortnox never lags behind your Postgres data.
Safe, idempotent sync
Every run is idempotent with duplicate protection, so a retry or a re-run can never double-post an invoice into Fortnox.
Why syncing Supabase to Fortnox is hard
A real sync means moving rows from Postgres into Fortnox and keeping them in step — which usually means a worker, a scheduler, webhook handling and retry logic, plus the risk of double-posting if anything fails. Most teams end up with a bespoke integration that needs babysitting.
How the Supabase → Fortnox sync works
Ziikly reads your Supabase database, maps the rows you choose to Fortnox invoices with a field mapping you control, and pushes them in on the schedule you set. Each run is idempotent: the same row can never create a duplicate invoice, and a failed run retries cleanly instead of posting twice.
What you see after connecting both
Your Supabase rows appear in Fortnox as invoices, with the mapping you configured and the status from the latest run. You can preview the field mapping before enabling writes, and every run leaves a log you can audit.
Limits worth knowing
Rows are pushed on the schedule you set, not continuously by default. The mapping is explicit — fields you don't map don't transfer — and invoices are created, not retroactively edited, so keep your field mapping in mind before you enable writes.
Frequently asked questions
Is this a real-time webhook sync?
You choose. Ziikly can push matched rows from Supabase into Fortnox on a schedule or on demand from your app. Runs are idempotent with duplicate protection, so a re-run or a retry never double-posts an invoice.
Does Ziikly write rows into Fortnox?
Yes — that's the point. The sync creates invoices in Fortnox from your Supabase rows. You control the field mapping and can preview it before enabling writes, and every run is logged so you can audit what was created.
Sync Supabase to Fortnox — Without Code
Push your Postgres data into Fortnox without writing sync jobs, schedulers or webhook glue.