Support
Set up and troubleshoot Nordsynk
Connect your AI client to Fortnox with Nordsynk. Start at /setup for connection steps. After signing in, /dashboard shows your connected company, authorization, and licensing status. Use the guidance below for common connection and access problems.
Start here
- Open /setup to choose your AI client, confirm the MCP endpoint, and start the Fortnox connection.
- After signing in, open /dashboard to review the selected company, connection, authorization, and license status.
- If you need help, start a chat here or contact support with the details below.
Include this in the first support message
- The MCP client used, such as Claude Desktop, Claude Code, ChatGPT, or another MCP client.
- The Fortnox company or tenant involved, plus the database or organization number if it is visible.
- The approximate time of the problem, including timezone if the team is distributed.
- The exact Fortnox or MCP error text shown to the user, copied verbatim when possible.
These details help support route the issue without another round of questions. Never include passwords, API keys, OAuth tokens, BankID codes, or bank details.
Useful endpoints
- Main MCP endpoint: https://mcp.nordsynk.se/mcp
- SSE fallback: https://mcp.nordsynk.se/sse
- Worker health: https://mcp.nordsynk.se/mcp/health
Common issues
The MCP client keeps asking me to sign in again.
If a previously working Fortnox connection asks you to sign in again, keep the Nordsynk connector in your AI client and use the company-specific reconnect link it provides. Remove and re-add the connector only if it is missing or the first Nordsynk sign-in never finished.
The dashboard says Fortnox licensing could not be verified.
First check whether your Nordsynk access is through Fortnox Marketplace (Classic) or Nordsynk Byrå. Classic/Marketplace access is licensed per Fortnox company and user: activate Nordsynk and assign the affected user a seat in that company in Fortnox, then retry. A standard Nordsynk Byrå agreement is based on active connected client companies and includes all consultants; its agreement governs access instead of Marketplace seat multiplication. If a paid and assigned Marketplace seat still cannot be verified, send support the company, user, approximate time, and exact message.
The client cannot finish MCP connection.
Confirm that the client uses https://mcp.nordsynk.se/mcp; use https://mcp.nordsynk.se/sse only when the client requires SSE. Let the client discover OAuth settings and leave manual OAuth Client ID and Client Secret fields empty. Restart the connection flow. If one previously connected company fails, use its Nordsynk reconnect link while keeping the connector connected. If Fortnox denies access, check that the company and user have the required Fortnox permissions. For a Classic/Marketplace purchase, also confirm the Nordsynk seat is assigned to that user in the same company. For Nordsynk Byrå, do not buy a Marketplace seat; contact Nordsynk if the agreement or company access appears wrong.
An admin needs to reconnect or remove access.
Open /dashboard and sign in if prompted. Select the company there to review its connection and use the reconnect or disconnect controls. When renewing an existing connection, use the same Fortnox user.
Can we use Nordsynk while blocking HR and payroll?
Yes. Nordsynk can enable the company policy hr_payroll_blocked. It blocks HR/payroll, employees/personnel, absence/attendance, schedules, time reporting, and vacation debt inside the MCP server. Fortnox consent remains broad for the existing Nordsynk app; the restriction is enforced by Nordsynk at runtime, not by reducing Fortnox scopes per user.
When you need escalation
For customer-facing support, email hello@nordbeam.io or call 0724488319. Include the MCP client, company or tenant, approximate time, and visible error text from Fortnox or the MCP client. Never send passwords, API keys, OAuth tokens, BankID codes, or bank details.