Resources · Make integration

Quaderno Make integrationAutomate Quaderno with Make.

Stop retyping client details into Quaderno by hand. The Quaderno Make integration gives you 19 modules: 14 actions, 4 searches and one instant trigger. This guide shows how to link your account and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Quaderno Make integration do for you?

The Quaderno Make integration links your Quaderno account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Quaderno then creates invoices, contacts, estimates and expenses on its own, based on what happens in your other apps.

Invoices that write themselves. When a client pays through another app, chain Create a Contact and Create an Invoice so the paperwork exists before anyone opens Quaderno. Each item passing between modules is a bundle: here, one client, then one invoice.

A team that hears about billing events first. Watch Events is an instant trigger: Quaderno calls Make through a webhook as soon as a selected event occurs. Add Get an Invoice behind it and you can pass the full invoice to a chat tool, a spreadsheet or your CRM.

Expenses kept tidy. Search Expenses finds matching records, and Update an Expense or Delete an Expense corrects them in bulk, which beats clicking through the Quaderno dashboard one line at a time.

Make only covers what these 19 modules and the Make an API Call module allow; anything else in the Quaderno API goes through that last one. The official Make documentation for this app also warns that it was partly AI-generated, so double-check a detail before you rely on it. If you are still choosing a platform, the n8n vs Make comparison and our Make review lay out the differences, and Make pricing explains how operations are counted.

Connect

How do you connect Quaderno to Make?

  1. 01

    Copy your Quaderno API key

    Make talks to Quaderno with an API key, so you need an active Quaderno account first. In Quaderno, open your profile section, click API Keys and copy the key shown on screen. Keep that tab open for the next step.

  2. 02

    Add a Quaderno module in Make

    In your scenario, add any Quaderno module and click Create a connection. A connection is your Quaderno account linked to Make once, then reused by every Quaderno module. The Connection name field is optional, but a clear name helps when you manage several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied from Quaderno, or follow the instructions Make shows on screen, then save. Make can now read your Quaderno data, and every other Quaderno module in the scenario reuses that same connection.

First scenario

Build your first Quaderno scenario

GoalWhen a new client lands in another app, Make adds them to Quaderno as a contact and creates their invoice.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Pick the app where your new clients appear first, such as a form tool or your online store, and choose its trigger.

  2. 02

    Add Create a Contact

    Click the + on the right of that first module, search for Quaderno and pick Create a Contact. Link your account with Create a connection, then map the client details that the previous module received.

  3. 03

    Chain Create an Invoice

    Add a third module, Create an Invoice. Map the contact that Create a Contact just returned, so the invoice lands on the right person, then fill the invoice fields Make lists for you.

  4. 04

    Test with Run once

    Click Run once and trigger a real event in the first app. Open each module's bubble to read the bundle it received, then check Quaderno: the new contact and its invoice should be there.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule (every 15 minutes by default, 15 minutes minimum on the Free plan), then flip the scenario on. Make runs it from now on without you.

Triggers

What starts a Quaderno scenario

1 module starts a scenario when something happens in Quaderno. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Quaderno as soon as it happens.

Quaderno1Watch Events

Watch Events

Instant trigger

In MakeTriggers when selected events have occurred.

Watch Events starts your scenario the moment one of the Quaderno events you selected occurs, and hands the event to the next module as a bundle. It is the only trigger this app has, so every Quaderno-first scenario begins here.

How it fires
instant: Quaderno calls Make through a webhook as soon as it happens, so there is no polling interval to wait for.
When to use it
when your team, your accounting sheet or your CRM needs to react to billing activity in Quaderno without anyone checking the dashboard.
Watch out
click Create a webhook before Create a connection, and select only the events you care about, since each one that arrives costs operations further down the scenario.
Modules

Every Quaderno module in Make

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

Quaderno1

Create a Contact

Action

In MakeCreates a new contact.

Adds a new customer record to Quaderno from data another module already has, so nobody copies client details between tools. The contact it returns can feed an invoice or an estimate right away.

When to use it
a client signs up or buys through another app and doesn't exist in Quaderno yet.
Watch out
run Search Contacts first if the same person may come back, or you end up with duplicates.
Quaderno2

Create an Estimate

Action

In MakeCreates a new estimate.

Drafts a quote in Quaderno for a prospect, filled from the request that reached you through another app. You get a proper estimate on file before a sales call even starts.

When to use it
a quote request form is submitted and you want the estimate ready for review, not typed from scratch.
Watch out
run it once with Run once and open the result in Quaderno, so you see exactly what a client would receive.
Quaderno3

Create an Expense

Action

In MakeCreates a new expense.

Records a cost in Quaderno from a receipt, a supplier email or a card payment that shows up elsewhere, which keeps your expense ledger complete without manual entry.

When to use it
a supplier bill lands in a mailbox or a storage folder and should be logged the same day.
Watch out
test with Run once on a single receipt before letting the scenario process a whole batch.
Quaderno4

Create an Invoice

Action

In MakeCreates a new invoice.

Issues a new invoice in Quaderno for a contact, using the order or payment details mapped from an earlier module. This is the module that turns a sale somewhere else into billing paperwork.

When to use it
an order is paid in your store or payment tool and the customer should get an invoice without waiting on you.
Watch out
map the contact returned by Create a Contact or Search Contacts, not a raw email typed by hand.
Quaderno5

Delete a Contact

Action

In MakeDeletes an existing contact.

Removes an existing contact from Quaderno, which helps keep the customer list in step with the tool your team treats as the master record.

When to use it
a record is removed from your CRM and should disappear from Quaderno too.
Watch out
treat the deletion as final. Try it with Run once on a test contact before the scenario goes live, and check which bundles reach this module.
Quaderno6

Delete an Expense

Action

In MakeDeletes an existing expense.

Erases one expense record in Quaderno, typically a duplicate or a line entered by mistake, so your cost totals stay honest.

When to use it
after Search Expenses has surfaced a duplicate you have confirmed should go.
Watch out
a search can return several bundles and each one reaches this module, so check the results in Run once before switching the scenario on.
Quaderno7

Get a Contact

Action

In MakeRetrieves an existing contact.

Fetches the full record of one Quaderno contact you already point to, so later modules can use details the trigger or a previous step didn't include.

When to use it
an earlier module hands you a contact and the next step needs the customer's full details to write a message or update your CRM.
Watch out
it reads a single known contact; to find one by name or email, reach for Search Contacts instead.
Quaderno8

Get an Estimate

Action

In MakeRetrieves an existing estimate.

Pulls one Quaderno estimate with all its details, which lets you share or archive the quote elsewhere without opening Quaderno.

When to use it
an earlier step gives you an estimate and your sales channel needs the full quote, not just its reference.
Watch out
you need to know which estimate to fetch; when you don't, List Estimates is the module that browses them.
Quaderno9

Get an Expense

Action

In MakeRetrieves an existing expense.

Reads a single expense from Quaderno so its amount and details can move into a spreadsheet, a report or a message for the person who approves costs.

When to use it
you already hold the reference of an expense from an earlier module and want its complete contents.
Watch out
Get an Expense returns one item; Search Expenses is the right choice for filtering a set.
Quaderno10

Get an Invoice

Action

In MakeRetrieves an existing invoice.

Retrieves one Quaderno invoice in full, ready to send to your accounting sheet, your team chat or a client follow-up.

When to use it
when an earlier module hands you an invoice and the next one, a message or a spreadsheet row, needs every detail of it.
Watch out
when you only know the client and not the invoice itself, start with Search Invoices, then map its result here.
Quaderno11

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Calls any endpoint of the Quaderno API with the connection you already set up, which covers whatever the ready-made modules leave out.

When to use it
you need a Quaderno object or action that none of the ready-made modules offers.
Watch out
you write the request yourself, so keep the Quaderno API documentation open and test every call with Run once.
Quaderno12

Update a Contact

Action

In MakeUpdates an existing contact.

Changes an existing Quaderno contact so it matches fresh information from another tool, which saves you from invoicing an old address.

When to use it
a customer edits their details in your CRM or store and Quaderno should follow.
Watch out
find the right contact first with Search Contacts, since an update aimed at the wrong record overwrites good data.
Quaderno13

Update an Expense

Action

In MakeUpdates an existing expense.

Edits an expense already recorded in Quaderno, so the record matches the final receipt once it arrives.

When to use it
a corrected supplier bill replaces the first version and the ledger has to reflect it.
Watch out
paired with Search Expenses, every matching bundle gets updated, so narrow the search before running it.
Quaderno14

Update an Invoice

Action

In MakeUpdates an existing invoice.

Modifies an existing Quaderno invoice with data coming from another step, keeping billing aligned with what actually happened in the sale.

When to use it
an order changes after the invoice was created and the two need to match again.
Watch out
test with Run once on a test invoice first, because a change here reaches real customer paperwork.
Quaderno15

List Estimates

Search

In MakeRetrieves a list of estimates.

Returns your Quaderno estimates as a series of bundles, one per quote, so the rest of the scenario can handle each of them in turn.

When to use it
you want to copy every open quote into a sales sheet or check which ones still need follow-up.
Watch out
each estimate becomes its own bundle, and every module after this one runs once per bundle, which adds operations.
Quaderno16

Search Contacts

Search

In MakeSearches for contacts or lists them all.

Looks up Quaderno contacts that match your criteria, or lists all of them, and returns zero, one or several results. It is the safe check before creating anyone.

When to use it
just before Create a Contact, to find out whether the client already exists.
Watch out
zero results means the next modules may not run at all, so plan a route for the no-match case.
Quaderno17

Search Expenses

Search

In MakeSearches for expenses or lists them all.

Finds Quaderno expenses matching what you ask for, or lists them all, giving you the set of records to review, export or correct.

When to use it
to push costs into a reporting spreadsheet, or to spot duplicates before cleaning them with Delete an Expense.
Watch out
listing everything can return a long series of bundles. Each module placed after it then runs once per bundle, and every run counts as an operation.
Quaderno18

Search Invoices

Search

In MakeSearches for invoices or lists them all.

Returns the Quaderno invoices that fit your filter, or every invoice, so you can reconcile billing with payments recorded in another tool.

When to use it
a payment arrives and you need to locate the matching invoice before calling Update an Invoice.
Watch out
several invoices can match, so check in Run once that the right one reaches the next module.
Need help

Need help automating Quaderno with Make?

A person reads every message.

FAQ

Quaderno and Make: common questions

01Is the Quaderno Make integration free?
Yes, Quaderno is a standard app in Make, so you can use it on 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 lift the interval to 1 minute and allow unlimited active scenarios. Each module run on one bundle counts as one operation on your plan. Quaderno itself needs an active account on its side, with its own subscription.
02What do you need to connect Quaderno to Make?
You need an active Quaderno account and a Quaderno API key. Find the key in your Quaderno profile section under API Keys and copy it. In Make, add a Quaderno module, click Create a connection, optionally name it, then paste the key. For the Watch Events trigger, click Create a webhook first and create the connection from there. Once saved, every Quaderno module in your scenarios reuses the same connection.
03Does the Quaderno Make trigger react in real time?
Yes. Watch Events is an instant trigger: Quaderno calls Make through a webhook as soon as one of the events you selected occurs, instead of Make checking on a schedule. The scenario starts right away with the event as its first bundle. Every other Quaderno module is an action or a search, so a scenario that starts from another app follows that app's trigger or the schedule you set on the first module.
04What if a Quaderno module is missing in Make?
Use Make an API Call. It calls any endpoint of the Quaderno API with the connection you already created, so you can reach objects or actions that the ready-made modules don't cover. You build the request yourself, which means reading the Quaderno API documentation and testing with Run once. The Make documentation for this app notes that part of it was AI-generated, so confirm any important detail with Quaderno directly before you build on it.
05Should you use Make or n8n for Quaderno?
It depends on the tool your team already runs. In Make, Quaderno comes with 19 ready modules, including an instant Watch Events trigger and Make an API Call for anything else, all set up without code on the visual editor. n8n often has a node for the same app, so check its catalog for Quaderno if n8n is already part of your stack. Compare the modules you actually need on each side before deciding, rather than the tool's reputation.