Resources · Make integration

Fortnox Make integrationAutomate Fortnox with Make.

Can Make keep Fortnox in step with the rest of your tools? The Fortnox Make integration gives you 47 modules, 37 actions and 10 searches, for invoices, customers, suppliers, projects and staff time. This page shows you how to connect Fortnox and build a first working flow.

Try the Fortnox integration on MakeSee the 47 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Fortnox Make integration do for you?

The Fortnox Make integration links your Fortnox account to Make so your other apps can create, read, update and cancel records there without code. You build a scenario, the automation Make runs, out of modules, one brick per step. Fortnox brings no trigger of its own, so a scenario starts from another app or from a schedule.

Invoice a deal the moment it closes. When your CRM reports a won deal, Create a Customer opens the client record, Create an Invoice bills it and Download an Invoice hands the PDF to your mail tool.

Onboard a supplier without retyping. A vendor onboarding form feeds Create a Supplier, then Create a Supplier Invoice books the first bill against that record.

Keep staff data in one place. Create an Employee and Create an Absence Transaction carry new hires and approved leave from your HR tool into Fortnox.

What the integration cannot do: react on its own when something changes in Fortnox, since no module watches it. The Make documentation page for Fortnox also says it was generated with AI from vendor docs, so double-check critical details with Fortnox. Anything the modules skip goes through Make an API Call. Many apps also have an n8n node, and the n8n vs Make page compares both tools. If you would rather not build alone, Make training covers the basics and the Make agency can build it with you.

Connect

How do you connect Fortnox to Make?

  1. 01

    Create an integration in Fortnox

    In Fortnox, open the menu and choose Developer Portal, then Create new integration. Name it, select the scopes it needs and paste https://www.integromat.com/oauth/cb/fortnox as the callback URI before you click Save.

  2. 02

    Copy your credentials

    Once saved, Fortnox shows a Client ID and a Client secret on screen. Copy both. Make uses them to open your connection, meaning your Fortnox account linked to Make once and reused by every Fortnox module.

  3. 03

    Create the connection in Make

    Add any Fortnox module to a scenario and click Create a connection. Type a label in Connection name if you like, then enter the credentials you copied or follow the on-screen prompts to finish.

First scenario

Build your first Fortnox scenario

GoalWhen a deal is won in your CRM, Make creates the customer in Fortnox and bills them.

  1. 01

    Start a new scenario

    From the Scenarios page, create a new scenario and click the +. Pick the CRM where deals are closed and its trigger, which becomes the first bubble of the flow.

  2. 02

    Add Create a Customer

    Click the + on the right, search for Fortnox and choose Create a Customer. Link your account with Create a connection, then map the client's name and details from the deal.

  3. 03

    Bill with Create an Invoice

    Add Create an Invoice right after it. Map the customer the previous module just created, then map what was sold from the deal data of the first module.

  4. 04

    Test with Run once

    Click Run once and mark a test deal as won. Open each module's bubble to read the bundles it received, then check the new customer and invoice in Fortnox.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default), then switch the scenario on. From then on, every won deal becomes a Fortnox invoice without anyone retyping it.

Modules

What can each Fortnox module do?

Fortnox gives you 47 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Fortnox1

Cancel an Invoice

Action

In Make“Cancels an invoice.”

Cancel an Invoice stops a customer invoice you issued in Fortnox straight from your scenario, without anyone opening the accounting screen.

When to use it
an order is refunded or called off in your online shop, and the matching invoice should stop chasing the client.
Watch out
treat cancelling as final and make sure only genuine cancellations ever reach this module.
Fortnox2

Cancel a Supplier Invoice

Action

In Make“Cancels a supplier invoice.”

Bills from vendors that turn out wrong or duplicated leave the pile with Cancel a Supplier Invoice, so your team does not process them by mistake.

When to use it
a supplier sends a corrected bill and your approval tool rejects the first version.
Watch out
this works on the payables side only; customer invoices are handled by Cancel an Invoice.
Fortnox3

Create a Customer

Action

In Make“Creates a new customer.”

Create a Customer adds a new client record to Fortnox from data another app already holds, so sales and accounting share the same name and details.

When to use it
a quote is signed in your CRM and the client has to exist in Fortnox before anyone can bill them.
Watch out
run List Customers first when the client may already exist, or you risk two records for one company.
Fortnox4

Create an Absence Transaction

Action

In Make“Creates a new absence transaction.”

Leave approved elsewhere lands in Fortnox as an absence transaction, the record of time an employee was away. Create an Absence Transaction writes it for you.

When to use it
a manager approves sick leave or a holiday in your HR tool and payroll has to see it.
Watch out
the employee needs a Fortnox record first; Create an Employee or List Employees covers that part.
Fortnox5

Create an Article

Action

In Make“Creates a new article.”

With Create an Article, a product or service you start selling also exists on the accounting side, as an article in Fortnox.

When to use it
a new product goes live in your online store and the Fortnox catalog should follow without a second entry.
Watch out
check with List Articles before creating, since the same product added twice makes reports messy.
Fortnox6

Create an Attendance Transaction

Action

In Make“Creates a new attendance transaction.”

Hours worked recorded in another tool become an attendance transaction in Fortnox, so nobody copies timesheets by hand. That is the job of Create an Attendance Transaction.

When to use it
a technician logs a site visit in a field service app and the time spent should reach Fortnox.
Watch out
map the right employee carefully; a wrong match puts the hours on a colleague's record.
Fortnox7

Create an Employee

Action

In Make“Creates a new employee.”

New hires reach Fortnox without a second form: Create an Employee opens their record from what your recruiting or HR tool already knows.

When to use it
a candidate is marked as hired and has to exist in Fortnox before any absence or attendance gets logged.
Watch out
when someone rejoins the company, check List Employees first so the same person does not end up with two records.
Fortnox8

Create an Expense

Action

In Make“Creates a new expense.”

Create an Expense records a new expense in Fortnox from a claim captured in another tool, so it reaches accounting without retyping.

When to use it
a team member submits a receipt through an expense form and the claim should land in Fortnox.
Watch out
test with Run once on a single claim, then open the expense in Fortnox to see how your mapped data landed.
Fortnox9

Create an Invoice

Action

In Make“Creates a new invoice.”

Billing becomes a step of the scenario: Create an Invoice issues a customer invoice in Fortnox from an order, a signed quote or a finished job.

When to use it
an order is paid or shipped in your store and the invoice should exist without anyone typing it.
Watch out
make sure the customer exists first by placing Create a Customer or List Customers in front of it.
Fortnox10

Create a Project

Action

In Make“Creates a new project.”

Create a Project opens a new project in Fortnox straight from the tool where the job was won, so the assignment exists on the accounting side from the start.

When to use it
a consulting firm signs a new engagement and wants it set up in Fortnox before any work is billed.
Watch out
names repeat across clients more often than expected, so look at List Projects first to avoid near duplicates.
Fortnox11

Create a Supplier

Action

In Make“Creates a new supplier.”

Vendors you start working with get their Fortnox record through Create a Supplier, fed by the form or purchasing tool where they signed up.

When to use it
a new vendor fills in your onboarding form with their company details.
Watch out
the supplier record should exist before bills are booked against it, so this module usually sits before Create a Supplier Invoice.
Fortnox12

Create a Supplier Invoice

Action

In Make“Creates a new supplier invoice.”

A bill received by email or read by a document scanning tool turns into a supplier invoice in Fortnox with Create a Supplier Invoice.

When to use it
a purchase is approved in your spend tool and accounting needs the bill logged.
Watch out
map the supplier returned by List Suppliers or created by Create a Supplier, so the bill lands on the right vendor.
Fortnox13

Delete a Customer

Action

In Make“Deletes a customer.”

Delete a Customer removes a client record from Fortnox, the way to clean out test entries or duplicates a scenario left behind.

When to use it
a client record was created by mistake while you were testing and has to disappear.
Watch out
a deletion cannot be undone from Make, so run Retrieve a Customer first and check you are aiming at the right record.
Fortnox14

Delete an Absence Transaction

Action

In Make“Deletes an absence transaction.”

When leave is cancelled at the source, Delete an Absence Transaction takes the matching record out of Fortnox so the hours stay accurate.

When to use it
an employee withdraws a holiday request that was already pushed to Fortnox.
Watch out
if only the dates moved, Update an Absence Transaction keeps the record and is the safer choice.
Fortnox15

Delete an Article

Action

In Make“Deletes an article.”

Products you stop selling can leave your Fortnox catalog through Delete an Article, which keeps the list of items short and current.

When to use it
an item is retired for good from your store and should no longer be offered on new invoices.
Watch out
nothing brings a deleted article back from Make, so point the module at the exact article you found with List Articles.
Fortnox16

Delete a Project

Action

In Make“Deletes a project.”

A project opened by mistake, or duplicated by an early version of your scenario, disappears from Fortnox with Delete a Project.

When to use it
a deal falls through before any work starts and the project created for it is no longer needed.
Watch out
run Retrieve a Project beforehand to confirm the target, because a removed project does not come back.
Fortnox17

Download an Invoice

Action

In Make“Previews an invoice as pdf.”

Download an Invoice gives you the PDF of a Fortnox invoice as a file your scenario can pass on, to an email, a shared folder or a client portal.

When to use it
right after Create an Invoice, to send the document to the client from your own mailbox.
Watch out
on the Make Free plan, files are capped at 5 MB, which matters as soon as the PDF travels to other modules.
Fortnox18

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Fortnox API with the connection you already set up, which covers everything the listed modules leave out.

When to use it
the data you need has no module of its own in this list and you would rather not set up a second login.
Watch out
you write the request yourself, so keep the Fortnox API documentation open while you build it.
Fortnox19

Retrieve a Customer

Action

In Make“Retrieves a specific invoice.”

Retrieve a Customer fetches one client record from Fortnox so later modules can reuse its details in an email, an invoice or a CRM update.

When to use it
a support ticket names a client and the agent wants the billing details from Fortnox right beside it.
Watch out
it returns the single record you point it to; when you do not know which record you need, List Customers is the better start.
Fortnox20

Retrieve an Absence Transaction

Action

In Make“Retrieves a specific absence transaction.”

Pulling back a single absence record is what Retrieve an Absence Transaction does, handing its data to the next step of your scenario.

When to use it
before changing a leave entry, to compare what Fortnox holds with the new request.
Watch out
you need to know which transaction you want; to browse several, List Absence Transactions returns them as separate bundles.
Fortnox21

Retrieve an Article

Action

In Make“Retrieves a specific article.”

Retrieve an Article reads one product or service from Fortnox, so a quote, a store listing or a message can reuse what accounting has on file.

When to use it
a sales rep builds an offer in another tool and wants the article details exactly as Fortnox knows them.
Watch out
it aims at one article only; List Articles is the module for going through the whole catalog.
Fortnox22

Retrieve an Attendance Transaction

Action

In Make“Retrieves a specific attendance transaction.”

A single logged shift or block of hours comes back from Fortnox with Retrieve an Attendance Transaction, ready to be checked or reused.

When to use it
a team lead questions an entry and you want its details posted in a chat channel.
Watch out
this module only reads; changing the hours is the job of Update an Attendance Transaction.
Fortnox23

Retrieve an Employee

Action

In Make“Retrieves a specific employee.”

Retrieve an Employee brings back one person's record from Fortnox, so HR tools, chat bots or reports can reuse it without a manual lookup.

When to use it
an internal request mentions a colleague and the next module needs their Fortnox details.
Watch out
employee data is personal, so only send it on to tools and channels that are meant to hold it.
Fortnox24

Retrieve an Expense

Action

In Make“Retrieves a specific expense.”

With Retrieve an Expense, the scenario reads one expense from Fortnox and passes it on for a check, an approval message or a report line.

When to use it
a finance manager wants a specific claim posted in a review channel before it gets updated.
Watch out
it returns one item only; List Expenses is the choice when you need several at once.
Fortnox25

Retrieve an Invoice

Action

In Make“Retrieves a specific invoice.”

Looking up one customer invoice in Fortnox lets its data drive the next move, a reminder, a CRM update or a message to sales. Retrieve an Invoice handles that lookup.

When to use it
a client asks about a bill in your help desk and the agent should see the invoice details there.
Watch out
this reads the data, not the document; Download an Invoice is the module that gives you the PDF.
Fortnox26

Retrieve a Project

Action

In Make“Retrieves a specific project.”

Checking one project before acting on it gets simple with Retrieve a Project, which returns its Fortnox record to the scenario.

When to use it
just before Update a Project or Delete a Project, to confirm you are touching the right one.
Watch out
when you are not sure the project exists yet, start with List Projects and see what comes back.
Fortnox27

Retrieve a Supplier

Action

In Make“Retrieves a specific supplier.”

Retrieve a Supplier returns one vendor record from Fortnox, handy when another tool needs the supplier details accounting already keeps.

When to use it
a purchase request comes in and your approval message should show who the vendor is on the Fortnox side.
Watch out
it reads a single supplier; use List Suppliers as a starting point when you do not know which record matches.
Fortnox28

Retrieve a Supplier Invoice

Action

In Make“Retrieves a specific supplier invoice.”

One vendor bill, read straight from Fortnox: Retrieve a Supplier Invoice feeds its data into the next module for a check or a notice.

When to use it
a supplier asks about a bill and your team wants its details posted where they discuss payments.
Watch out
reading changes nothing; Update a Supplier Invoice or Cancel a Supplier Invoice are the modules that act on it.
Fortnox29

Update a Customer

Action

In Make“Updates a customer.”

Update a Customer keeps a Fortnox client record in line with your CRM when an address or a contact person changes there.

When to use it
a client moves offices and the change entered by sales should reach invoicing too.
Watch out
test on a single client with Run once before switching on, so you see exactly what lands in Fortnox.
Fortnox30

Update an Absence Transaction

Action

In Make“Updates an absence transaction.”

Update an Absence Transaction corrects leave already recorded in Fortnox without removing the original entry.

When to use it
an employee shifts a holiday by a day after the request was approved and synced.
Watch out
the scenario must know which transaction to change, so keep a link between the request in your HR tool and its Fortnox record.
Fortnox31

Update an Article

Action

In Make“Updates an article.”

Changes made to a product in your store reach Fortnox through Update an Article, so both catalogs tell the same story.

When to use it
a product is renamed or repriced in your e-commerce back office.
Watch out
decide which tool owns the article data; updating from both sides can bounce changes back and forth between them.
Fortnox32

Update an Attendance Transaction

Action

In Make“Updates an attendance transaction.”

Update an Attendance Transaction fixes hours already logged in Fortnox, so corrections made in the time tracker do not stay stuck there.

When to use it
a shift was logged too long and the manager corrects it in the scheduling app.
Watch out
this list has no delete module for attendance, so from Make the only ways to correct an entry are this module and Make an API Call.
Fortnox33

Update an Employee

Action

In Make“Updates an employee.”

Changes in someone's situation, a new role or a new address, reach Fortnox with Update an Employee instead of a second manual edit.

When to use it
HR records a promotion in the tool that holds your master staff data.
Watch out
there is no module to delete an employee here, so plan how departures are handled on the Fortnox side.
Fortnox34

Update an Invoice

Action

In Make“Updates an invoice.”

Update an Invoice changes a customer invoice that already exists in Fortnox, so a late correction does not mean starting over.

When to use it
an order gains an extra item after the scenario already created its invoice.
Watch out
once an invoice should no longer apply at all, Cancel an Invoice fits better than editing it.
Fortnox35

Update a Project

Action

In Make“Updates a project.”

Project details follow the real work when Update a Project applies changes from your project tool to the Fortnox record.

When to use it
an engagement changes status or owner in your planning software.
Watch out
find the project with List Projects or Retrieve a Project first, since the update needs a precise target.
Fortnox36

Update a Supplier

Action

In Make“Updates a supplier.”

Update a Supplier keeps vendor records in Fortnox current by pushing the changes made in your purchasing tool or a vendor form.

When to use it
a supplier sends new contact details and your buyer records them in the purchasing app.
Watch out
check the mapping on one supplier with Run once before you switch the scenario on.
Fortnox37

Update a Supplier Invoice

Action

In Make“Updates a supplier invoice.”

Corrections to a vendor bill already in Fortnox go through Update a Supplier Invoice, keeping the record aligned with what the supplier finally sent.

When to use it
a credit or a corrected amount is agreed with the supplier after the bill was logged.
Watch out
a bill that should never have been booked is better handled by Cancel a Supplier Invoice.
Fortnox38

List Absence Transactions

Search

In Make“Retrieves a list of all absence transactions.”

List Absence Transactions returns every absence record Fortnox holds, each as its own bundle, the item that travels from one module to the next.

When to use it
to build a leave overview in a spreadsheet or to see who is away before staffing a project.
Watch out
every bundle that goes through later modules costs an operation, one module run on one item, so a long list adds up on your plan.
Fortnox39

List Articles

Search

In Make“Retrieves a list of all articles.”

The whole Fortnox catalog comes back with List Articles, one bundle per product or service, ready to compare with your store or a price sheet.

When to use it
before Create an Article, to check whether an item already exists.
Watch out
the module can return nothing, one or many articles, so test with Run once and see how the next module behaves in each case.
Fortnox40

List Attendance Transactions

Search

In Make“Retrieves a list of all attendance transactions.”

List Attendance Transactions pulls the hours logged in Fortnox so they can feed a spreadsheet, a dashboard or a check against your time tracker.

When to use it
a project manager wants logged time next to the project budget in another tool.
Watch out
a large set of transactions means many bundles, and each later module counts operations for every one of them.
Fortnox41

List Customers

Search

In Make“Retrieves a list of all customers.”

List Customers hands your scenario the whole Fortnox customer register, one bundle per customer (a bundle is one item passed to the next module).

When to use it
you want to copy each customer into a sheet or a CRM without picking them one by one; if you already hold the customer you need, Retrieve a Customer is the lighter choice.
Watch out
each module placed after this search runs once per customer, and every run counts as one operation on your Make plan.
Fortnox42

List Employees

Search

In Make“Retrieves a list of all employees.”

List Employees gives you every employee recorded in Fortnox as a separate bundle, ready to feed a staff directory or an HR tool.

When to use it
the next step concerns the whole workforce, such as syncing names into a shared roster; for a single person, Retrieve an Employee avoids pulling everyone.
Watch out
the search may return zero bundles, in which case the modules after it simply do not run, so test it with Run once before switching the scenario on.
Fortnox43

List Expenses

Search

In Make“Retrieves a list of all expenses.”

List Expenses brings back the expenses stored in Fortnox so a scenario can review them together, for instance to push each one into your finance lead's reporting table.

When to use it
you need the complete set of expenses rather than one entry; Retrieve an Expense fits better when an earlier module already gives you the exact record.
Watch out
Make lists what the search returns, not a summary, so add an aggregator (the Make tool that groups bundles) if you want one total instead of many rows.
Fortnox44

List Invoices

Search

In Make“Retrieves a list of all invoices.”

List Invoices returns your Fortnox customer invoices one by one, which is the starting point for chasing unpaid ones, archiving PDFs or mirroring billing in another tool.

When to use it
place it first in a scenario started by the Make schedule, then chain Download an Invoice or Update an Invoice on each bundle it produces.
Watch out
this module covers customer invoices only; bills you receive from vendors come from List Supplier Invoices, a separate search.
Fortnox45

List Projects

Search

In Make“Retrieves a list of all projects.”

List Projects collects the projects set up in Fortnox and sends each one down the scenario, handy for keeping a planning board or a time tracker aligned with your accounting.

When to use it
a project tool on the other side must know every Fortnox project; reach for Retrieve a Project instead when only one project matters to the next step.
Watch out
run the scenario once and read the bundles Make received before mapping anything, so you see the project data your Fortnox account really exposes.
Fortnox46

List Supplier Invoices

Search

In Make“Retrieve a list of all supplier invoices.”

List Supplier Invoices fetches the bills your suppliers sent you and recorded in Fortnox, giving the scenario each purchase invoice to approve, forward or log elsewhere.

When to use it
an accounts payable team wants every incoming bill copied into its approval tool; follow it with Update a Supplier Invoice or Cancel a Supplier Invoice when a decision comes back.
Watch out
sales invoices never show up here, only purchase ones, so pick List Invoices for what you bill your own customers.
Fortnox47

List Suppliers

Search

In Make“Retrieves a list of all suppliers.”

List Suppliers outputs your full vendor list from Fortnox, one supplier per bundle, so the scenario can check, enrich or copy each vendor record into a purchasing tool.

When to use it
you are cleaning up vendor data or syncing it with another system; Retrieve a Supplier suits the case where an earlier module already points to one vendor.
Watch out
anything the listed modules cannot do on suppliers is still reachable through Make an API Call, with the same Fortnox connection.
Need help

Need help automating Fortnox with Make?

A person reads every message.

FAQ

Fortnox and Make: common questions

01Is the Fortnox Make integration free?
Yes. Fortnox is a standard app in Make, so its modules are available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) go down to 1 minute between runs, allow unlimited active scenarios and 40 minutes of execution. Make counts usage in credits, one operation for each module run on one item. Your Fortnox subscription itself is handled separately with Fortnox.
02What do you need to connect Fortnox to Make?
You need a Fortnox developer account and valid authorization credentials. In Fortnox, open Developer Portal from the menu, click Create new integration, name it, select the scopes and enter https://www.integromat.com/oauth/cb/fortnox as the callback URI, then save. Copy the Client ID and Client secret shown on screen. In Make, add a Fortnox module, click Create a connection, give it a name if you want and enter those credentials or follow the on-screen steps. Every Fortnox module then reuses that connection.
03Does Fortnox trigger Make scenarios in real time?
No. The Fortnox app in Make has no trigger module, so nothing in Fortnox starts a scenario on its own. There are two ways around it. Start the scenario with a trigger from another app, such as your CRM or your store, and put the Fortnox modules after it. Or place a Fortnox search such as List Invoices first and set a schedule on it: a new scenario runs every 15 minutes by default, and the Free plan cannot go below that interval. Either way, test with Run once before switching the scenario on.
04What if a Fortnox module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Fortnox API with the connection you already created, so you can reach what the 47 listed modules do not cover without a second login. You write the request yourself from the Fortnox API documentation. Also note that the Make documentation page for Fortnox states it was generated with AI from Fortnox's documentation and may contain mistakes, so verify important details with Fortnox. If the limit comes from your Make plan rather than the app, paid plans shorten the interval between runs and extend execution time.
05Should you use Make or n8n for Fortnox?
It depends more on your team than on Fortnox. On Make, Fortnox comes with 47 modules, 37 actions and 10 searches, plus Make an API Call for everything else, but no trigger, so scenarios start from another app or from a schedule. Many apps also have an n8n node, so check whether one exists for Fortnox and whether it covers the same records you care about: invoices, suppliers, projects or staff time. Then pick the tool your team already builds in and compare coverage on the records you actually need.
Same platform

Other docs you might need on this stack.

Browse all integrations