Resources · Make integration

sevDesk Make integrationAutomate sevDesk with Make.

What could your invoicing look like if sevDesk handled the follow-up on its own? The sevDesk Make integration gives you 44 modules: 3 triggers, 28 actions and 13 searches. This guide shows how to link your account and build a first scenario, no code involved.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the sevDesk Make integration automate?

The sevDesk Make integration links your sevDesk account to Make, a visual tool where you chain apps together without writing code. Each chain is a scenario: a trigger notices something in sevDesk, then modules create, update, search or send records such as contacts, orders, invoices and vouchers.

Orders that turn into invoices. Watch Orders spots each order created in sevDesk, Create an Invoice builds the matching bill with data mapped from that order, and Send an Invoice via Email puts it in the customer's inbox. The sales team stops copying lines from one document to the next.

A cleaner contact base. A form or another tool can feed Create a Contact, after Check Customer Number Availability confirms the number is free. Create a Contact Address and Create a Communication Way then complete the record with a postal address and a phone or email.

Receipts filed where they belong. Watch Vouchers picks up each new voucher at the next scheduled check, Upload a Voucher File attaches the scan, and Book a Voucher finishes the job. Bookkeepers get a folder they no longer have to chase.

The listed modules do not cover the whole sevDesk API. For anything missing, Make an API Call reaches any endpoint with the same connection. Many apps also exist as an n8n node; if you are weighing both tools, the n8n vs Make comparison lays out the criteria. To learn scenario building step by step, see the Make training, and check Make pricing before you scale.

Connect

How do you connect sevDesk to Make?

  1. 01

    Copy your sevDesk API token

    Log in to sevDesk, open Settings then User, and click the user name you want Make to act as. Copy the API Token shown on that page and keep it at hand for the next step.

  2. 02

    Add the connection in Make

    In your Make scenario, insert any sevDesk module and click Add next to the Connection field. A connection is your sevDesk account linked to Make once, then reused by every sevDesk module you add later.

  3. 03

    Paste the token and save

    Give the connection a clear label in Connection name, for example the company it belongs to. Paste the token into API Key and click Save. The module can now list your sevDesk records.

First scenario

Your first scenario: bill every new sevDesk order

GoalWhen an order is created in sevDesk, Make creates the invoice and emails it to the customer.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for sevDesk and pick Watch Orders as the first module.

  2. 02

    Link your account

    Click Add next to the connection field and paste your API token, as described above. Once saved, the trigger is ready to read the orders of your sevDesk account.

  3. 03

    Add the invoice

    Click the + on the right of Watch Orders and choose Create an Invoice. Map the customer and the amounts from the order that the trigger passed along.

  4. 04

    Send it by email

    Add Send an Invoice via Email after it and map the invoice returned by the previous module. Each order now flows through three modules, and each one counts as an operation on your plan.

  5. 05

    Test with Run once

    Create a test order in sevDesk, then click Run once. Open each module's bubble to read the bundle it received, one order and one invoice, and fix any mapping that looks off.

  6. 06

    Schedule and switch on

    Click the clock on Watch Orders to set Scheduling. A new scenario checks every 15 minutes by default. Switch the scenario on and it keeps billing new orders without you.

Triggers

What can start a sevDesk scenario?

3 modules start a scenario when something happens in sevDesk. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by sevDesk as soon as it happens.

sevDesk1Watch Contacts

Watch Contacts

Scheduled trigger

In MakeTriggers if a contact has been created.

Watch Contacts picks up each contact created in sevDesk, customer or supplier, at the scenario's next check, so the rest of your stack learns about them without a manual export. Each new contact arrives as one bundle you can map into a CRM, a mailing list or a spreadsheet.

How it fires
scheduled. Make checks sevDesk on the scenario's schedule, every 15 minutes by default, and does not get a push from sevDesk.
When to use it
your accountant creates customers in sevDesk and the sales team needs them in their own tool.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes, so a contact can wait that long.
sevDesk2Watch Orders

Watch Orders

Scheduled trigger

In MakeTriggers if an order has been created.

Watch Orders hands every freshly created sevDesk order to the next module, which is the natural starting point for billing, delivery or stock follow-up. You pick what happens next; the trigger only tells Make that the order exists.

How it fires
scheduled. Make polls sevDesk on the scenario's schedule, with the clock badge on the module, rather than being called by sevDesk.
When to use it
an order is recorded in sevDesk and you want the invoice, a warehouse message or a task created from it.
Watch out
the trigger is built around order creation, so for changes to existing orders start the flow from the app where the change happens.
sevDesk3Watch Vouchers

Watch Vouchers

Scheduled trigger

In MakeTriggers if a voucher has been created.

Watch Vouchers collects each new voucher in sevDesk, the receipts and supplier bills your bookkeeping runs on, and passes it on as a bundle. That lets you route expense documents to approval, storage or a team channel without opening sevDesk.

How it fires
scheduled. Make asks sevDesk for new vouchers at the interval set in the scenario's Scheduling, 15 minutes by default.
When to use it
a colleague scans a supplier bill into sevDesk and the finance lead should be told.
Watch out
a voucher only reaches the scenario at the next scheduled check, 15 minutes at best on the Free plan.
Modules

What can Make do in sevDesk?

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

sevDesk1

Book an Invoice

Action

In MakeBooks an invoice.

Book an Invoice runs the booking step on an existing sevDesk invoice from inside your scenario, so the invoice moves forward in your books without anyone clicking through sevDesk.

When to use it
a payment notice lands in another tool and the matching invoice should be booked right after.
Watch out
the module needs the right invoice; fetch it first with Get an Invoice or Search Invoices.
sevDesk2

Book a Voucher

Action

In MakeBooks a voucher.

With Book a Voucher, a supplier bill or receipt already stored in sevDesk gets its booking done by Make, which closes the loop on expense documents that used to sit waiting for someone.

When to use it
after Upload a Voucher File has attached the scan and the voucher is complete.
Watch out
book only vouchers you have checked; add a filter between modules if some need a human look first.
sevDesk3

Cancel an Invoice

Action

In MakeCancels an invoice.

Cancel an Invoice cancels an invoice in sevDesk, the clean way to reverse a bill that went out by mistake or for an order the customer dropped.

When to use it
an order is cancelled in your shop and the invoice created for it must follow.
Watch out
cancelling is not deleting; reach for Delete an Invoice only when the document should disappear entirely.
sevDesk4

Check Customer Number Availability

Action

In MakeChecks if a given customer number is available or already used.

Before a new contact is created, this module tells you whether a given customer number is still free or already taken in sevDesk, which keeps your numbering free of duplicates.

When to use it
your CRM assigns its own customer numbers and you want sevDesk to match them.
Watch out
the answer only informs the scenario; place a filter after it so Create a Contact runs only when the number is available.
sevDesk5

Check if an Invoice is Partially Paid

Action

In MakeChecks if an invoice is already partially paid.

Here you learn whether an invoice has already received part of its payment, which is the detail that decides between a firm reminder and a gentle nudge.

When to use it
a dunning scenario should skip customers who have started paying and treat them differently.
Watch out
it answers yes or no about partial payment; route the result with a router or filter rather than stacking separate scenarios.
sevDesk6

Create a Communication Way

Action

In MakeCreates a new contact communication way.

A communication way is a way to reach a contact, such as an email address or a phone number. This module adds one to a contact, so a record created elsewhere arrives with the details your team actually uses to reach people.

When to use it
right after Create a Contact, to attach the email captured by a web form.
Watch out
map the contact returned by the previous module, or the detail lands on the wrong record.
sevDesk7

Create a Contact

Action

In MakeCreates a new contact.

Create a Contact adds a new customer or supplier to sevDesk from data coming out of another app, which spares you retyping names from a form, a shop or a CRM.

When to use it
a lead signs a quote in another tool and needs to exist in sevDesk before the first invoice.
Watch out
run Search Contacts first if the same person could come in twice, otherwise each run creates a duplicate.
sevDesk8

Create a Contact Address

Action

In MakeCreates a new contact address.

The postal side of a contact lives in its own record in sevDesk. This module adds an address to an existing contact so invoices and deliveries go to the right place.

When to use it
a customer fills in a billing address at checkout and sevDesk should store it on their card.
Watch out
as its name says, it adds an address rather than replacing one, so check what the contact already holds before adding more.
sevDesk9

Create an Accounting Contact

Action

In MakeCreates a new accounting contact.

Create an Accounting Contact sets up the bookkeeping side of a sevDesk contact, the part your accountant relies on when entries are posted, which saves a separate trip into sevDesk after each new customer.

When to use it
in the same scenario that creates the contact, as the next module, so the record is complete from the start.
Watch out
map the contact produced upstream; the module does not create one on its own.
sevDesk10

Create an Invoice

Action

In MakeCreates a new invoice.

This is the module that produces the bill itself: Create an Invoice creates a new sevDesk invoice from the customer and line data you map, ready to be sent, rendered or booked by the modules that follow.

When to use it
an order, a signed quote or a finished project in another tool should end in an invoice.
Watch out
test with Run once on a single record before switching on, since every run creates a real invoice.
sevDesk11

Create an Order

Action

In MakeCreates a new order.

Orders from a shop or a booking tool can reach sevDesk automatically through Create an Order, which gives your sales records one home instead of two diverging lists.

When to use it
a checkout completes in your web shop and sevDesk should hold the matching order.
Watch out
products are added as separate lines with Create an Order Position, one module further along.
sevDesk12

Create an Order Position

Action

In MakeCreates a new order position for an order.

An order position is one line of an order: a product, a quantity, a price. This module adds such a line to an existing sevDesk order, one bundle at a time.

When to use it
a shop order carries several products and each one must appear on the sevDesk order.
Watch out
with several products, put an iterator before this module so each line becomes its own bundle and its own operation.
sevDesk13

Create a Part

Action

In MakeCreates a new part in your sevDesk inventory.

Parts are the products and items of your sevDesk inventory. Create a Part adds a new one, so a product launched in your shop or your product sheet also exists where your invoices pick it up.

When to use it
a new item goes live in your catalogue and sevDesk should list it too.
Watch out
check with Search Parts first when the same product might already exist under another name.
sevDesk14

Create a Voucher

Action

In MakeCreates a new voucher.

Expense documents collected elsewhere become proper sevDesk vouchers through this module, which saves the bookkeeper from keying in each supplier bill by hand.

When to use it
a supplier bill arrives by email or in a shared folder and should be recorded in sevDesk.
Watch out
the voucher carries data, not the scan; attach the file afterwards with Upload a Voucher File.
sevDesk15

Delete a Communication Way

Action

In MakeDeletes a communication way.

Delete a Communication Way removes an outdated phone number or email from a contact, which keeps reminders and invoices from going to an address nobody reads anymore.

When to use it
a customer unsubscribes or changes email in another tool and the old detail must go.
Watch out
deletion cannot be undone; find the exact entry with Search Communication Ways before this module runs.
sevDesk16

Delete an Invoice

Action

In MakeDeletes an invoice.

Delete an Invoice removes an invoice from sevDesk entirely, useful for clearing out test documents or drafts that should never have existed.

When to use it
a scenario test left draft invoices behind and you want a clean account.
Watch out
nothing brings a deleted invoice back; for a bill the customer already received, Cancel an Invoice is the safer choice.
sevDesk17

Delete an Order

Action

In MakeDeletes an order.

When an order should vanish from sevDesk, this module deletes it, which keeps your order list aligned with what your shop or CRM still considers live.

When to use it
an order entered twice by mistake, or a test order created while building the scenario.
Watch out
the deletion is final; add a filter so only the orders you really mean to remove reach this module.
sevDesk18

Get a PDF Document of an Invoice

Action

In MakeRetrieves a PDF document of an invoice.

You get the invoice as a PDF file inside the scenario, ready to be stored in a drive, attached to an email from another tool or sent to a customer portal.

When to use it
invoices should be archived as files in cloud storage as soon as they exist.
Watch out
on the Free plan Make handles files up to 5 MB, which matters if your invoices carry heavy attachments.
sevDesk19

Get Stock of a Part

Action

In MakeReturns the current stock amount of the given part.

Get Stock of a Part returns how many units of a given item sevDesk currently has, so a scenario can react to low stock or show availability in another tool.

When to use it
after an order comes in, to warn purchasing when the item runs short.
Watch out
the module reads the stock of one part at a time; pair it with Search Parts to cover several items.
sevDesk20

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call is the escape hatch: it lets you reach any endpoint of the sevDesk API with the connection you already set up, for everything the listed modules do not cover.

When to use it
you need a sevDesk object or action that has no dedicated module on this page.
Watch out
you write the request yourself, so keep the sevDesk API documentation open while you set it up.
sevDesk21

Mark an Invoice as Sent

Action

In MakeMarks an invoice as sent by a chosen send type.

Mark an Invoice as Sent updates the invoice status in sevDesk and records how it went out, using the send type you choose, so your open items reflect reality even when the bill left through another channel.

When to use it
the invoice was mailed by post or sent from your own email tool, not by sevDesk.
Watch out
pick the send type that matches the real channel, or your records will say the bill left another way.
sevDesk22

Render a PDF Document of an Invoice

Action

In MakeRenders a PDF document of an invoice.

Rendering asks sevDesk to build the PDF of an invoice, the step that turns the data you created into the document the customer will see.

When to use it
right after Create an Invoice, before fetching the file with Get a PDF Document of an Invoice.
Watch out
test it with Run once on a single invoice and read the bundle before wiring more modules behind it.
sevDesk23

Send an Invoice via Email

Action

In MakeSends a specified invoice via email.

With one module the invoice leaves sevDesk by email and reaches the customer, which removes the last manual step between a sale and getting paid.

When to use it
at the end of a billing scenario, once Create an Invoice has produced the document.
Watch out
during tests, point the invoice at your own contact so Run once does not email a real customer.
sevDesk24

Update a Contact

Action

In MakeUpdates an existing contact.

Update a Contact rewrites an existing sevDesk contact with fresher data, so a company name or detail changed in your CRM does not linger in its old form on the next invoice.

When to use it
a customer edits their profile in another app and sevDesk should follow.
Watch out
you need the contact's identity first; get it with Search Contacts or Get a Contact.
sevDesk25

Update an Order

Action

In MakeUpdates an existing order.

Orders change after they are placed. This module brings those changes into the sevDesk order, keeping delivery, billing and your shop in line with each other.

When to use it
a customer changes an order in your shop and the sevDesk copy must match before invoicing.
Watch out
Watch Orders does not fire on edits, so start this flow from the app where the change happens.
sevDesk26

Update a Part

Action

In MakeUpdates an existing part.

Update a Part edits an existing item of your sevDesk inventory with the data you map, so your invoices keep using current product data.

When to use it
a price changes in your product catalogue and sevDesk should carry the new one.
Watch out
identify the part first with Search Parts or Get a Part, or the update targets nothing.
sevDesk27

Update a Voucher

Action

In MakeUpdates an existing voucher.

Corrections to a supplier bill or receipt reach sevDesk through Update a Voucher, so the bookkeeping record matches the corrected document your supplier sent.

When to use it
a supplier issues a corrected bill and the voucher already in sevDesk needs the new data.
Watch out
book vouchers after the corrections, not before, so Book a Voucher runs on final data.
sevDesk28

Upload a Voucher File

Action

In MakeUploads a voucher file.

This module sends the scan or PDF of a receipt into sevDesk, so every voucher comes with its proof attached when the accountant reviews it.

When to use it
receipts land in an email inbox or a cloud folder and should end up in sevDesk.
Watch out
the Free plan caps files at 5 MB, so a large photo of a receipt may need compressing first.
sevDesk29

Get a Contact

Search

In MakeRetrieves a single contact.

Get a Contact fetches one sevDesk contact when you already know which one, giving the next modules its full details to map into an email, an invoice or a CRM.

When to use it
an order comes in with a contact reference and you need the customer's details.
Watch out
it needs the exact contact; when you only have a name or email, use Search Contacts instead.
sevDesk30

Get an Invoice

Search

In MakeRetrieves a single invoice.

One invoice, fully loaded: this search reads a single sevDesk invoice so the rest of the scenario can use its amounts, customer and status.

When to use it
a payment tool reports a payment and you need the invoice it refers to before booking it.
Watch out
it reads one invoice you already identify; to list invoices by criteria, Search Invoices is the right module.
sevDesk31

Get an Order

Search

In MakeRetrieves a single order.

Get an Order pulls a single sevDesk order with its data, so a later module can bill it, update it or forward it to your warehouse.

When to use it
another tool stores the sevDesk order reference and you need the order details at a given step.
Watch out
positions are separate; read them with Search Order Positions when you need the lines.
sevDesk32

Get a Part

Search

In MakeRetrieves a single part.

This search returns a single inventory item from sevDesk, handy when a scenario needs the product's data before creating an order line or updating a price.

When to use it
a shop sale names a product and you need its sevDesk record for the order position.
Watch out
for the quantity in stock, Get Stock of a Part is the dedicated module.
sevDesk33

Get a Voucher

Search

In MakeRetrieves a single voucher.

Get a Voucher reads one voucher from sevDesk, giving you its data to check, correct or book in the next modules.

When to use it
an approval tool returns a voucher reference and you want to book only what was approved.
Watch out
it fetches one voucher you already identify; to find vouchers by criteria, use Search Vouchers.
sevDesk34

Search Communication Ways

Search

In MakeSearches for communication ways or lists them all.

Search Communication Ways finds the phone numbers and emails stored on your contacts, or lists them all, which is the first step before cleaning or syncing them.

When to use it
you want to know whether an email already exists in sevDesk before adding it.
Watch out
a search can return zero, one or many bundles, and each following module runs once per bundle.
sevDesk35

Search Contacts

Search

In MakeSearches for contacts or lists them all.

Search Contacts looks up contacts that match your criteria, or lists the whole address book, and is the usual guard against duplicates before any contact is created.

When to use it
a new lead arrives and you first check whether sevDesk already knows them.
Watch out
an empty result does not stop the scenario by itself; add a filter to decide what happens next.
sevDesk36

Search Invoices

Search

In MakeSearches for invoices or lists them all.

With Search Invoices a scenario can gather the invoices that match what you ask for, or all of them, which is the base for reminders, reports or exports to a spreadsheet.

When to use it
you want a sheet of open invoices refreshed whenever the scenario runs.
Watch out
each invoice returned is a bundle, and every module after it spends one operation per invoice.
sevDesk37

Search Order Positions

Search

In MakeSearches for order positions or lists them all.

This search returns the lines of your orders, product by product, so you can copy them into an invoice, a packing list or a stock sheet.

When to use it
after Watch Orders, to read what each new order actually contains.
Watch out
an order with several lines yields several bundles; add an aggregator if the next app expects them all at once.
sevDesk38

Search Orders

Search

In MakeSearches for orders or lists them all.

Search Orders finds sevDesk orders that meet your criteria or lists them all, which helps when you need to act on a group of orders rather than on a single new one.

When to use it
checking whether an order from your shop already exists in sevDesk before Create an Order runs.
Watch out
long result lists multiply operations downstream, so narrow the search as much as the module allows.
sevDesk39

Search Parts

Search

In MakeSearches for parts or lists them all.

Your sevDesk inventory becomes readable to other apps through Search Parts, which finds items by your criteria or returns the full list.

When to use it
matching a product sold in your shop with its sevDesk part before adding an order line.
Watch out
when two parts share similar names, check the result count before mapping, or the wrong item may be used.
sevDesk40

Search Voucher Positions

Search

In MakeSearches for voucher positions or lists them all.

Search Voucher Positions reads the individual lines of your vouchers, which is where the detail of an expense sits when a supplier bill covers several items.

When to use it
sending the line detail of new supplier bills to a cost-tracking spreadsheet.
Watch out
expect one bundle per line; aggregate them if you want a single row per voucher.
sevDesk41

Search Vouchers

Search

In MakeSearches for vouchers or lists them all.

You get the sevDesk vouchers matching your search, or all of them, and each one travels on as its own bundle (one item passed to the next module).

When to use it
pick it over Get a Voucher when you do not know the exact voucher yet, for example to review every receipt tied to a supplier before booking them.
Watch out
the search can return zero, one or many bundles, so every module placed after it runs once per voucher found.
Need help

Need help automating sevDesk with Make?

A person reads every message.

FAQ

sevDesk and Make: common questions

01Is the sevDesk Make integration free?
Yes, sevDesk is a standard app in Make, so its modules are available from the Free plan onward. The Free plan does come with limits: 2 active scenarios, at least 15 minutes between two 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) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module per bundle, so a billing scenario with three modules spends three operations per order.
02What do you need to connect sevDesk to Make?
You need a sevDesk account and its API token, and the sevDesk documentation for Make lists no other prerequisite. In sevDesk, open Settings then User, click the user name and copy the API Token. In Make, insert any sevDesk module, click Add next to the Connection field, name the connection and paste the token into the API Key field before saving. That connection is then reused by every sevDesk module of your scenarios, so you only set it up once per account.
03Does the sevDesk trigger react instantly in Make?
No. The three sevDesk triggers, Watch Contacts, Watch Orders and Watch Vouchers, are scheduled triggers. Make checks sevDesk on the schedule of your scenario, every 15 minutes by default, rather than receiving a signal from sevDesk the moment something happens. On a paid plan you can shorten the interval to 1 minute; on the Free plan 15 minutes is the minimum. If a contact, order or voucher must be handled sooner, a shorter schedule on a paid plan is the lever Make gives you.
04What if a sevDesk module is missing in Make?
It depends on what you need, but the sevDesk app includes Make an API Call, which covers most gaps. With it you can call any endpoint of the sevDesk API from your scenario, reusing the connection you already created, so an object or action without a dedicated module stays reachable. You write the request yourself, which asks a little more care than a ready-made module. The sevDesk documentation on Make lists no numbered limits, so the main constraints you will meet are those of your Make plan, such as operations and execution time.
05Should you use Make or n8n for sevDesk?
It depends on how you like to work. In Make, sevDesk comes as a ready app with 44 modules: 3 scheduled triggers, 28 actions and 13 searches, plus Make an API Call for the rest, all set up through a visual editor and one API token. Many apps also have an n8n node, so check whether one exists for sevDesk and which operations it offers before choosing. Compare the modules each tool provides for your exact flow, the way usage is counted on each side and who in your team will maintain the scenario over time.