Nordsynk or Zapier MCP for Fortnox?
Nordsynk and Zapier MCP solve the same underlying problem in different ways: both connect an AI assistant like Claude or ChatGPT to Fortnox. Nordsynk is its own MCP server built directly against the full Fortnox API, with write approvals and support for Swedish accounting workflows like invoice attest and SIE export. Zapier MCP is instead a layer on top of Zapier's existing automation platform, limited to the set of Fortnox actions Zapier has chosen to expose. The difference shows up most clearly in coverage, activation, and how you pay.
Nordsynk runs this page and is one of the two options compared — the Zapier details below come solely from Zapier's own product documentation.
Quick comparison
| Nordsynk | Zapier MCP | |
|---|---|---|
| Architecture | Its own MCP server against the full Fortnox API | A relay on top of Zapier's automation platform |
| Coverage | Full API (377 operations) plus Swedish workflows like OCR, attest, and SIE | The actions Zapier has chosen to expose for Fortnox |
| Activation | The Fortnox portal, OAuth 2.0 | A Zapier account plus a Fortnox connection |
| Write safety | Browser approval preview by default; company-scoped auto-approve and activity logging | Zapier's general Zap history, no Fortnox-specific approvals |
| Price | 199 SEK per Fortnox company and user/month | A Zapier subscription plus task-based metering |
| Data path | Directly against the Fortnox API | Through Zapier's infrastructure |
The coverage gap is what you feel most in practice. Nordsynk's 377 operations mirror the entire Fortnox REST API, plus ready-made workflows for things that aren't single API calls — the supplier invoice inbox, OCR rows, and attest chains. Zapier MCP instead exposes a fixed set of actions: create and find customers, invoices, orders, and articles, plus one freeform API-call action for everything else. That covers simple automations well, but any task without a ready-made action needs either a custom API call in Zapier or waiting for Zapier to add it.
The pricing models differ just as fundamentally. Nordsynk bills per Fortnox company and user through Fortnox Marketplace — no separate Zapier account needed. Zapier MCP costs nothing beyond your existing Zapier plan, but every call your AI assistant makes draws two tasks from the same quota your regular Zaps use, according to Zapier's own documentation — so the price tracks how much Zapier you already use.
When Zapier MCP is the better fit
Zapier MCP is the better fit if you're already a Zapier customer and Fortnox is just one of several apps in your automations. Say you have a Zap that creates a Fortnox customer the moment a deal closes in your CRM, posts to Slack, and logs the row in a Google Sheet — you'd rather let the AI assistant drive that same Zap infrastructure than wire in another tool. The Fortnox side of MCP is included in the Zapier plan you already pay for — no new purchase, and it reuses the same Zapier authentication as the rest of your Zaps, according to Zapier's own documentation. That profile — several systems, already invested in Zapier, rarely needing Fortnox-specific workflows like attest or SIE export — is exactly what Zapier MCP is built for, and it's not one Nordsynk competes for.
When Nordsynk is the better fit
Nordsynk is the better fit when the Fortnox work itself is the point, not one app among several in a chain. Supplier invoices are the clearest example: an invoice lands in the inbox, OCR reads the source document, a colleague attests it, and only then is it posted — the whole chain exists as ready-made workflows in Nordsynk, not as separate actions you have to wire together yourself. SIE export for the accountant, searching the ledger, and coding entries to the right account are the same story: built directly against the Fortnox API instead of assembled from several Zap steps. Accounting bureaus feel the difference most. A bureau running ten client companies connects each company's Fortnox account separately while keeping the same AI assistant and write-approval flow. Licensing is still per Fortnox company and user: one user across ten client companies needs ten seats, one in each company. Zapier MCP's fixed action list doesn't cover that kind of Fortnox-specific, multi-step work, and that's exactly the gap Nordsynk is built to fill.
Frequently asked questions
Can I use both?
Yes. Nordsynk and Zapier MCP each connect to Fortnox independently, so a bureau could run Nordsynk for attest and SIE export while an existing Zap handles CRM sync against the same Fortnox company.
What does Zapier MCP cost?
It depends on your Zapier plan. Zapier MCP isn't a separate purchase — every call draws two tasks from the same quota your Zaps use, according to Zapier's own documentation, so the cost tracks how much Zapier you already use.
Do I need a Zapier account for Nordsynk?
No. Nordsynk activates directly in the Fortnox portal with Fortnox OAuth 2.0 — no Zapier account required, no Zap to build.
Can Zapier MCP attest supplier invoices or export SIE files?
Zapier's public documentation doesn't list attest or SIE export among its Fortnox actions — it covers customers, invoices, orders, and articles. Nordsynk has ready-made workflows for both.
Related
Ready to activate Nordsynk?
Activate in the Fortnox portal. Done in under five minutes.
Activate in Fortnox