Resources · Make integration

Quentn Make integrationAutomate Quentn with Make.

What can the Quentn Make integration do for your contact list? Make offers 13 Quentn modules: one instant trigger, 9 actions and 3 searches. This guide is for marketers who already run Quentn, and it walks you from the connection to a first working scenario.

Try the Quentn integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Quentn Make integration let you automate?

The Quentn Make integration links your Quentn account to Make, a no-code tool where you build a scenario (the automation itself, a chain of bricks called modules). Quentn can call Make the moment a contact reaches a campaign, and Make can then create, update, search or delete contacts and terms in Quentn for you.

React to a campaign step. Watch New Campaign Events receives the contact as soon as Quentn sends it, and Add Contact Terms gives that contact the term you choose, so you can tell at a glance who reached that step.

Keep contact records in sync from another tool. A signup in your form tool or shop can feed Create or Update a Contact, which writes the person into Quentn whether they already exist or not. Get Contacts by Mail helps first when all you hold is an email address.

Tidy up your terms. Get Terms lists every term in the account, then Update a Term or Delete a Term cleans up the ones nobody uses anymore.

Know the limits before you start: Make's own documentation for Quentn is marked as limited, because little public information about the app exists. When a listed module falls short, Make an API Call reaches the rest of the Quentn API with the same connection. The Make troubleshooting guide helps when a run fails, and if you are weighing another tool, n8n vs Make puts the two side by side. To learn the editor properly, see the Make training.

Connect

How do you connect your Quentn account to Make?

  1. 01

    Open the connection window

    Add any Quentn module to your scenario and click Create a connection. A connection is your Quentn account linked to Make once, then reused by every Quentn module you add later.

  2. 02

    Name it and give access

    Give the connection a name if you like, which helps when you manage several Quentn accounts. Then authorize Make on the Quentn page that opens, or paste the key Quentn gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The module now shows your connection in its dropdown, and Make can read the Quentn objects it needs to fill the fields of the module.

First scenario

Your first scenario with Quentn

GoalWhen a contact reaches a campaign event in Quentn, Make adds a term to that contact.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add its first module. The canvas stays empty until you pick one.

  2. 02

    Pick the Quentn trigger

    Search for Quentn, choose Watch New Campaign Events and click Create a connection to link your account. This is an instant trigger: Quentn calls Make through a webhook.

  3. 03

    Add the term

    Click the + on the right of the trigger, add Add Contact Terms, then map the contact from the trigger and pick the term that should mark people who reached this campaign step.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubbles above each module to read the bundle, meaning the contact, that each module received.

  5. 05

    Switch it on

    When the test looks right, switch the scenario on. From then on, every contact that Quentn sends to Make gets the term without you touching anything.

Triggers

What starts a Quentn scenario?

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

Quentn1Watch New Campaign Events

Watch New Campaign Events

Instant trigger

In Make“Receives contact from campaign”

This trigger hands your scenario a contact the moment a Quentn campaign passes it along, so the follow-up happens right after the campaign step instead of waiting for someone to export a list.

How it fires
instant: Quentn calls Make through a webhook as soon as it happens, which the lightning badge on the module shows.
When to use it
a lead enters a nurturing sequence and your sales team wants the contact pushed into their own tool straight away.
Watch out
Make's documentation for Quentn is limited, so test the link with Run once before you rely on it.
Modules

What can Make do in Quentn?

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

Quentn1

Add Contact Terms

Action

In Make“Adds contact terms.”

Attaches one or more terms to an existing contact, so the person carries the labels your team filters on inside Quentn, without anyone editing the record by hand.

When to use it
a buyer finishes a purchase in your shop and should be marked as a customer in Quentn.
Watch out
this module attaches terms, it does not create them, so a new term goes through Create a Term first.
Quentn2

Create a Term

Action

In Make“Creates a new term.”

Adds a brand new term to your Quentn account, ready to be attached to contacts by other modules later in the same scenario.

When to use it
you launch a new product or webinar and want a matching term created from Make rather than by hand.
Watch out
run Get Terms first if the same name might already exist.
Quentn3

Create or Update a Contact

Action

In Make“Creates or updates a contact.”

Writes a person into Quentn and takes care of both cases: a new record when the contact is unknown, an update when it already exists. One module covers the whole sync.

When to use it
a form submission in another app should always end up as a clean Quentn contact.
Watch out
pick Update a Contact instead when you never want a new record created.
Quentn4

Delete a Contact

Action

In Make“Deletes a contact.”

Removes a contact from your Quentn account for good, which keeps the list free of people who asked to leave or who should never have been there.

When to use it
an erasure request arrives through your support tool and the contact must disappear from Quentn too.
Watch out
no Quentn module in Make brings a deleted contact back, so test it on a dummy contact first.
Quentn5

Delete a Term

Action

In Make“Deletes a term.”

Erases a term from the account, which helps keep the term list short enough that your team still understands what each one means.

When to use it
a campaign has ended and its dedicated term only clutters the filters.
Watch out
no Quentn module in Make restores a deleted term, so check the list with Get Terms before running this module.
Quentn6

Get a Contact by ID

Action

In Make“Returns info about a contact.”

Fetches the full details of one contact when you already hold its Quentn ID, so the next modules can use its data.

When to use it
an earlier step gave you a contact ID and you need the name or email address before writing to another tool.
Watch out
without an ID, use Get Contacts by Mail instead, since this module needs the exact identifier.
Quentn7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Quentn API with the connection you already set up, so you are not stuck when no listed module fits your need.

When to use it
you need a Quentn feature that none of the other 12 modules covers.
Watch out
you write the request yourself, so keep the Quentn API reference open while you fill this module.
Quentn8

Update a Contact

Action

In Make“Updates a contact.”

Changes the data of a contact that already exists in Quentn and never creates a new one, which protects your list from accidental duplicates.

When to use it
a customer edits their details in your billing tool and Quentn should reflect the change.
Watch out
the module needs to know which contact to change, so find it first with a search module.
Quentn9

Update a Term

Action

In Make“Updates a term.”

Edits an existing term in place instead of making you delete it and create a replacement.

When to use it
your team renames a product line and the matching term in Quentn should follow the new name.
Watch out
list the terms with Get Terms first so you target the right one.
Quentn10

Get Contacts by Mail

Search

In Make“Returns contacts with the specified email address.”

Looks up Quentn contacts from an email address, the one piece of data almost every other tool can hand over, and returns what it finds.

When to use it
a new support ticket arrives and you want the matching Quentn contact before replying.
Watch out
as a search, it can return zero, one or several bundles, so plan the case where nobody matches.
Quentn11

Get Contact Terms

Search

In Make“Lists all terms of a specified contact.”

Lists every term attached to one contact, which tells your scenario where that person stands before it decides what to do next.

When to use it
you only want to notify sales about contacts who do not carry a customer term yet.
Watch out
each term comes out as its own bundle, so the modules after it run once per term.
Quentn12

Get Terms

Search

In Make“List all terms.”

Returns all the terms that exist in your Quentn account, a handy inventory before you create, rename or remove any of them.

When to use it
you want a spreadsheet copy of your terms so the team can review which ones are still useful.
Watch out
every term becomes a separate bundle, and each module that follows spends one operation per bundle.
Need help

Need help automating Quentn with Make?

A person reads every message.

FAQ

Quentn and Make: common questions

01Is the Quentn Make integration free?
Yes. Quentn is a standard app in Make, so it works on the Free plan as well as on the paid ones. 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) lift those limits and count usage in credits, meaning operations, each month. Your Quentn subscription is a separate matter.
02What do you need to connect Quentn to Make?
You need a Quentn account and a Make account. Make's documentation lists no prerequisite and gives no official connection steps for Quentn, so the generic flow applies: add a Quentn module, click Create a connection, optionally name it, authorize Make on the Quentn page or paste the key Quentn provides, then click Save. The connection is then reused by every Quentn module in your scenarios. If the window asks for a key, look for API access in your Quentn account.
03Does the Quentn trigger fire in real time?
Yes. Watch New Campaign Events is an instant trigger: Quentn calls Make through a webhook as soon as a campaign passes a contact along, and the scenario starts without waiting for a schedule. That is the only Quentn trigger in Make. If you want to start from something else, such as a new row in a spreadsheet, begin the scenario with another app and use the Quentn actions afterward. Test the setup with Run once before you switch the scenario on.
04What if a Quentn module is missing in Make?
Use Make an API Call. It sends any request the Quentn API accepts, with the same connection as the other modules, so it covers what the 12 listed action and search modules leave out. Keep in mind that Make's documentation for Quentn is marked as limited because little public information about the app exists, so you will rely on Quentn's own API reference to write the request. Test each call with Run once and read the bundle it returns.
05Should you use Make or n8n for Quentn?
It depends on the tool your team already uses. Make gives Quentn 13 modules, including an instant trigger and Make an API Call for anything else, in a visual editor where you test each step with Run once. The same app often has an n8n node too, so check whether it exists and covers your case before you choose. Compare the modules each side offers for your scenario rather than general claims, and pick the editor your team will actually maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations