Resources · Make integration

Quipu Make integrationAutomate Quipu with Make.

Need invoices, contacts and tickets in Quipu to move without copy and paste? The Quipu Make integration gives you 21 modules: 3 triggers, 15 actions and 3 searches. This page shows how to connect your account, build a first scenario and pick the right module.

Try the Quipu integration on MakeSee the 21 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Quipu Make integration do for you?

The Quipu Make integration links your Quipu account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick of that chain, either a trigger that starts the run, an action that changes something in Quipu, or a search that finds records for you.

Invoices shared without anyone chasing them. At each scheduled check, Watch New Invoices picks up every new invoice and hands it to the next module, which can copy it to a spreadsheet or alert whoever follows up on payments.

Contacts kept clean when they come from outside. When a new client signs in your sales tool, List Contacts checks whether the person is already in Quipu, then Create a Contact or Update a Contact finishes the job.

Refunds that follow the decision. An approval recorded in another app can call Refund an Invoice or Refund a Ticket, for the full amount or part of it, without anyone reopening Quipu.

What you will not find here: instant triggers (all 3 are scheduled) and detailed documentation, which Make itself describes as limited for Quipu. Make an API Call covers what the listed modules leave out. The same app often has an n8n node as well, and the n8n vs Make comparison sets the two tools side by side. To see how plans count usage, read Make pricing.

Connect

How do you connect Quipu to Make?

  1. 01

    Add a Quipu module

    Open your scenario, click the +, type Quipu and choose any module, for example Watch New Invoices. Then click Create a connection. A connection is your Quipu account linked to Make once and reused by every Quipu module.

  2. 02

    Name the connection

    Give it a name you will recognize later, such as the company the account belongs to. The step is optional, but it helps a lot once several Quipu accounts live in the same Make workspace.

  3. 03

    Authorize and save

    Make then asks you either to approve access on Quipu's own page or to paste the key Quipu gives you. Finish with Save, and the module can now list what it reads from your account.

First scenario

Your first scenario: from a new order to a Quipu invoice

GoalWhen a new order lands in another app, Make creates the customer in Quipu, then the invoice.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. The first module comes from the app where orders arrive, your online store or your form tool, and it starts every run.

  2. 02

    Add Create a Contact

    Click the + to the right of the first module, search Quipu and pick Create a Contact. Click Create a connection if this is your first Quipu module, then map the customer data from the order.

  3. 03

    Add Create an Invoice

    Add one more module to the right: Create an Invoice. Fill it by mapping data from the order and from the contact you just created, so the invoice lands on the right person.

  4. 04

    Test with Run once

    Click Run once and place a test order. Open each module to read the bundles it received, then check in Quipu that exactly one contact and one invoice appeared.

  5. 05

    Schedule and switch on

    Set the schedule with the clock on the first module (every 15 minutes by default), then switch the scenario on. From that point, each new order is handled without you.

Triggers

What starts a Quipu scenario

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

Quipu1Watch New Contacts (deprecated)

Watch New Contacts (deprecated)

Scheduled trigger

In Make“Triggers when a new contact is added”

Watch New Contacts starts a scenario each time a contact appears in Quipu, handing Make one bundle (one item passed to the next module) per new contact. The documentation marks this trigger as deprecated, so it still shows up in the list but should not carry anything new.

How it fires
scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
only to read or repair an older scenario that already relies on it.
Watch out
for a new build, start from Watch New Invoices instead, or from List Contacts placed after a schedule, rather than from a module flagged as deprecated.
Quipu2Watch New Invoices

Watch New Invoices

Scheduled trigger

In Make“Triggers when a new invoice is added”

Watch New Invoices gives you a scenario that wakes up whenever an invoice is added in Quipu. Each new invoice arrives as its own bundle, ready to be copied to a spreadsheet, announced to a team channel or used to look up the customer behind it.

How it fires
scheduled: Make checks the app on the scenario's schedule, which is every 15 minutes on a new scenario unless you change the clock.
When to use it
when every new invoice should kick off your billing follow-up, and a short wait until the next check is fine.
Watch out
the trigger is not instant, so a fresh invoice waits for the next check before your scenario sees it.
Quipu3Watch New Tickets

Watch New Tickets

Scheduled trigger

In Make“Triggers when a new ticket is added”

Watch New Tickets turns every ticket added in Quipu into the starting point of a scenario. Make passes each ticket along separately, so the modules that follow handle one ticket at a time.

How it fires
scheduled: Make checks the app on the scenario's schedule; on the Free plan the shortest gap between two checks is 15 minutes.
When to use it
when a new ticket should lead to a follow-up elsewhere, such as a row in a sheet or a message to the person who handles tickets.
Watch out
each ticket a module processes counts as an operation, the unit Make counts on your plan.
Modules

What each Quipu module does

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

Quipu1

Create a Contact

Action

In Make“Creates a new contact”

Create a Contact adds a new contact record to Quipu from data another module hands over, so nobody retypes a name that came from a form or an order.

When to use it
when a new client shows up in another tool and must exist in Quipu before you bill them.
Watch out
put List Contacts in front of it if the person may already be there, otherwise you end up with a duplicate.
Quipu2

Create an Invoice

Action

In Make“Creates a new invoice”

Create an Invoice produces a new invoice in Quipu from data mapped out of earlier modules. It is the step that turns a closed sale into something you can collect on.

When to use it
right after an order or a quote is confirmed in another app, once the matching contact exists in Quipu.
Watch out
every run creates a real invoice, test runs included, so try it on a dummy customer first.
Quipu3

Create a Ticket

Action

In Make“Creates a new ticket”

Create a Ticket records a new ticket in Quipu without opening the app, using whatever the previous module collected.

When to use it
when an event in another tool, for example a submitted form or an incoming message, should leave a ticket behind in Quipu.
Watch out
the Make documentation for Quipu is limited, so look at the fields Make displays once the connection exists before you map anything into them.
Quipu4

Delete a Contact

Action

In Make“Deletes a specific contact”

Delete a Contact removes one specific contact from Quipu, which keeps your list tidy when a record should no longer exist.

When to use it
when a duplicate has been spotted, or when another scenario created a contact by mistake.
Watch out
treat the deletion as final. Place Get a Contact just before it and read its output with Run once, so you only remove the record you meant.
Quipu5

Delete an Invoice

Action

In Make“Deletes a specific invoice”

With Delete an Invoice, a scenario erases a given invoice from Quipu instead of someone hunting for it by hand.

When to use it
for invoices your scenario produced while you were testing, or ones created twice by an error upstream.
Watch out
deleting is not refunding. When the customer should get money back, Refund an Invoice is the module designed for that job.
Quipu6

Delete a Ticket

Action

In Make“Deletes a specific ticket”

Delete a Ticket gets rid of one ticket in Quipu, so a scenario can clean up after itself or drop an entry that should never have been recorded.

When to use it
once List Tickets or Get a Ticket has confirmed which ticket is wrong.
Watch out
map the ticket from a previous module rather than typing it, and try it on a test ticket first, because Run once deletes for real.
Quipu7

Get a Contact

Action

In Make“Gets a single contact using the contact ID”

Get a Contact fetches the full record of one contact when you already hold its ID, so later modules can work with everything stored on it.

When to use it
when an earlier module gave you a contact ID and the next step needs the whole record, not just that reference.
Watch out
it only works from an ID. If what you have is anything else, start with List Contacts to find the right one.
Quipu8

Get an Invoice

Action

In Make“Gets a single invoice using the invoice ID”

Get an Invoice pulls one invoice out of Quipu by its ID and hands the whole record to the next module as a single bundle.

When to use it
when another app keeps the Quipu invoice ID and you want the current version before a reminder or a report goes out.
Watch out
the result reflects the invoice at the moment the module runs, so place it right before the step that uses it.
Quipu9

Get a Ticket

Action

In Make“Gets a single ticket using the ticket ID”

Get a Ticket loads a single ticket from Quipu by its ID and gives the rest of the scenario everything recorded on it.

When to use it
right after Watch New Tickets or List Tickets, when one ticket deserves a closer look before you decide what happens next.
Watch out
this is a lookup, not a search. Without a ticket ID coming from an earlier module, it has nothing to read.
Quipu10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call”

Make an API Call lets you reach any endpoint of the Quipu API from your scenario, reusing the connection the other modules already share. You are not stuck when the ready-made modules stop short.

When to use it
when you need something the 21 listed modules do not offer.
Watch out
you have to know the Quipu API yourself, and the Make documentation for this app is limited, so the details of each request come from Quipu's side.
Quipu11

Refund an Invoice

Action

In Make“Fully or partly refunds an existing invoice”

Refund an Invoice records a refund against an existing invoice in Quipu, for the full amount or only part of it, without anyone reopening the invoice by hand.

When to use it
when a return or a cancellation is approved in another tool and your books should follow.
Watch out
decide before building whether your case is a full or a partial refund, then test with Run once on a sample invoice.
Quipu12

Refund a Ticket

Action

In Make“Fully or partly refunds an existing ticket”

Refund a Ticket applies a refund to a ticket already stored in Quipu, covering either the whole ticket or a portion of it.

When to use it
when a ticket has to be reversed after the fact, for example once a manager approves a correction in a shared form.
Watch out
pair it with Get a Ticket earlier in the scenario, so you refund the ticket you checked and not the first one that came through.
Quipu13

Update a Contact

Action

In Make“Updates a specific contact”

Update a Contact changes an existing contact in Quipu, so a detail corrected somewhere else reaches your billing records too.

When to use it
when your CRM or a form is where contact details really get edited, and Quipu should stay in step with it.
Watch out
you need the contact's ID. List Contacts can find it from the data your scenario already has.
Quipu14

Update an Invoice

Action

In Make“Updates a specific invoice”

Update an Invoice edits an invoice that already sits in Quipu, which spares you deleting and recreating it when something changes.

When to use it
when an order is amended in your sales tool after the invoice went out.
Watch out
fetch the invoice first with Get an Invoice and run the scenario once, so you can see what the update is about to change.
Quipu15

Update a Ticket

Action

In Make“Updates a specific ticket”

Update a Ticket rewrites the details of one ticket in Quipu, so a correction made elsewhere does not need a second manual edit.

When to use it
when a colleague fixes a ticket in a shared spreadsheet and Quipu should reflect the change.
Watch out
the module works on one ticket per bundle. Feed it several and it performs one update, and one operation, for each.
Quipu16

List Contacts

Search

In Make“Retrieves a list of contacts”

List Contacts searches Quipu and returns each contact it finds as its own bundle, which is how a scenario discovers an ID it did not have.

When to use it
before Create a Contact, to check whether the person already exists, or before Update a Contact, to target the right record.
Watch out
a search can return zero, one or many results, so plan what the next module does in each case.
Quipu17

List Invoices

Search

In Make“Retrieves a list of invoices”

List Invoices pulls a set of invoices out of Quipu and sends them down the scenario one by one, which suits reports kept outside Quipu.

When to use it
when you want a batch of invoices in a sheet or a dashboard rather than reacting to each new one.
Watch out
every invoice returned becomes a bundle, and each module that handles it uses an operation on your plan.
Quipu18

List Tickets

Search

In Make“Retrieves a list of tickets”

List Tickets reads the tickets stored in Quipu and returns them as separate bundles, ready to be reviewed or exported by the rest of the scenario.

When to use it
when you need to go through existing tickets, for instance to find the one a refund or an update should target.
Watch out
nothing guarantees a match. When the search comes back empty, the modules after it simply have no bundle to work on.
Need help

Need help automating Quipu with Make?

A person reads every message.

FAQ

Quipu and Make: common questions

01Is the Quipu Make integration free?
Yes. Quipu is a standard app in Make, so its modules work on the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations, one per module per bundle. Your Quipu subscription is a separate matter.
02What do you need to connect Quipu to Make?
A Quipu account and a Make account are enough, since the Make documentation lists no other prerequisite for Quipu. You add a Quipu module, click Create a connection, optionally name it, authorize Make on the Quipu page or paste the key Quipu provides, then click Save. All 21 modules reuse that connection, so you set it up once per account. Because the documentation is limited, rely on the fields Make displays once the connection exists.
03Do Quipu triggers in Make fire in real time?
No. The 3 Quipu triggers, Watch New Contacts, Watch New Invoices and Watch New Tickets, are scheduled: Make checks Quipu on the scenario's schedule instead of being called by Quipu. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan, while paid plans go down to 1 minute. Quipu has no instant trigger in Make, so build with that delay in mind. Also note that the documentation marks Watch New Contacts as deprecated.
04What if a Quipu module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Quipu API with the same connection as the other modules, so anything the API supports becomes reachable from a scenario. The catch is knowledge: you need to know which request to send, and the Make documentation for Quipu is limited, so those details come from Quipu. For everyday needs, check first whether one of the 15 actions or 3 searches already covers your case.
05Should you use Make or n8n for Quipu?
It depends on what you need from Quipu and on who will maintain the automations. Make offers 21 ready modules for Quipu, with 3 scheduled triggers and Make an API Call for anything else, and the Free plan is enough to test a first scenario. The same app often has an n8n node too, so check what that node covers before you decide. List the modules your process really needs, then pick the tool your team will keep running.
Same platform

Other docs you might need on this stack.

Browse all integrations