Resources · Make integration

Quable PIM Make integrationAutomate Quable PIM with Make.

Your product data can move on its own the moment a document changes. The Quable PIM Make integration gives you 14 modules: 1 instant trigger, 7 actions and 6 searches. This guide connects your account, builds a first scenario with you and explains each module.

Try the Quable PIM integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Quable PIM Make integration do for you?

The Quable PIM Make integration links your Quable account to Make, a no-code tool where you build a scenario (the automation itself) out of modules (one brick each: a trigger, an action or a search). Quable PIM tells Make when a document changes, and Make can read catalogs, assets, variants and links, or create new documents.

Keep other tools in step with Quable. Start with Watch Document Updates, add Get a Document to read the current version, then hand the result to the next app in your scenario, such as a spreadsheet or a message to your team.

Feed Quable from the outside. A row, a form answer or an email from another app can become a new record through Create a Document, so nobody has to retype it in the PIM.

Pull an inventory on demand. List Assets, List Variants or List Catalogs return every item as its own bundle (one item passed to the next module), which you can write into a sheet for a quick review.

Know the limits before you start. Make's own documentation for Quable PIM is marked as limited, so the page you are reading sticks to what the module names and descriptions say. When a listed module falls short, Make an API Call reaches the rest of the Quable API with the same connection.

Comparing tools? Read n8n vs Make. New to the editor? The Make training walks through it, and the Make pricing page explains how operations are counted.

Connect

How do you connect Quable PIM to Make?

  1. 01

    Add a Quable PIM module

    In a scenario, click the +, search for Quable PIM and pick any module. Then click Create a connection. A connection is your Quable account linked to Make once, and every Quable module reuses it afterward.

  2. 02

    Name it and authorize Make

    Give the connection a clear name if you like, for example the workspace it points to. Then either approve Make on the Quable page that opens or paste the key Quable gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. Back in the module, Make can now list what it is able to read from your account, which is the simplest sign that the connection works.

First scenario

Build your first scenario with Quable PIM

GoalWhen a document is updated in Quable PIM, Make fetches that document so the next module works with its current content.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the large + in the middle of the canvas. That empty circle becomes your first module.

  2. 02

    Add Watch Document Updates

    Search for Quable PIM, choose Watch Document Updates and pick your connection, or click Create a connection if this is your first Quable module. This trigger carries the lightning badge: Quable calls Make itself.

  3. 03

    Add Get a Document

    Click the + on the right of the trigger and choose Get a Document. In its code field, map the document code from the trigger's output instead of typing a fixed value.

  4. 04

    Test with Run once

    Click Run once, then update a document in Quable PIM. Open the bubble above each module to read the bundles it received and confirm the right document came through.

  5. 05

    Switch it on

    Once the test looks right, save and turn the scenario on. From then on, each document update starts a run and every module run counts as one operation on your Make plan.

Triggers

What starts a Quable PIM scenario

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

Quable PIM1Watch Document Updates

Watch Document Updates

Instant trigger

In Make“Triggers when a document is updated.”

This trigger gives your scenario a start signal each time someone edits a document in Quable PIM, so the change can travel to other tools without anyone copying it by hand. It is the only trigger this app offers.

How it fires
instant, meaning Quable PIM calls Make through a webhook as soon as the update happens. No polling interval to set.
When to use it
a product manager fixes a record and you want your spreadsheet, shop or team chat to hear about it right away.
Watch out
its description only mentions updates, so do not count on it for brand new documents; start from the module that created them.
Modules

Every Quable PIM module, explained

Quable PIM gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Quable PIM1

Create a Document

Action

In Make“Creates a document.”

Turns data from another app into a fresh document in Quable PIM, so a supplier row or form answer lands in the PIM without retyping.

When to use it
a new item arrives in a spreadsheet or form and should exist in Quable as well.
Watch out
Run once creates a real document too, so test with data you can delete right after.
Quable PIM2

Get a Catalog

Action

In Make“Retrieves a catalog by code.”

Hands you one catalog's details when you already know its code, which is handy for adding catalog context to a message or report.

When to use it
your scenario holds a catalog code and the next step needs the rest of that catalog's information.
Watch out
it needs the exact code; if you do not have it, run List Catalogs first and pick the code from there.
Quable PIM3

Get a Document

Action

In Make“Retrieves a document by code.”

Reads one document by its code and returns its current content, so later modules work with the latest version rather than an old copy.

When to use it
right after Watch Document Updates, or whenever another app hands you a document code.
Watch out
map the code from an earlier module; a typed value always fetches the same document on every run.
Quable PIM5

Get an Asset

Action

In Make“Retrieves an asset by code.”

Brings back one asset from Quable PIM, found by its code, so its details can travel to the next app in the flow.

When to use it
a document points to an asset and you want that asset's own information next to it.
Watch out
when the code is wrong or missing, the module has nothing to return; check the bundle in Run once before switching on.
Quable PIM6

Get a Variant

Action

In Make“Retrieves a variant by code.”

Pulls up one variant by its code, so a scenario can work on a precise version of an item instead of the whole family.

When to use it
another tool sends you a variant code and you need the matching record from Quable.
Watch out
to cover every variant, List Variants fits better than repeating this module by hand.
Quable PIM7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Quable PIM API to your scenario, using the connection you already created, for anything the ready-made modules do not cover.

When to use it
you need an action that appears in none of the other modules on this page.
Watch out
Make's documentation for Quable PIM is limited, so you will need Quable's own API reference to know which request to send.
Quable PIM8

List Assets

Search

In Make“Retrieves a list of all assets.”

Returns all the assets of your account, one bundle per asset, which is the easy way to build an inventory in a spreadsheet.

When to use it
a full review or export of your assets, not a single lookup.
Watch out
each returned asset flows through every following module, and each of those runs counts as an operation.
Quable PIM9

List Catalog Classification

Search

In Make“Retrieves all classifications of a catalog.”

Shows how one catalog is organized by returning all of its classifications, handy when you map categories into another tool.

When to use it
you are rebuilding a catalog's category tree in a shop, a sheet or a report.
Watch out
it works on one catalog at a time, so pair it with List Catalogs when you need them all.
Quable PIM10

List Catalogs

Search

In Make“Retrieves a list of all catalogs.”

Gives you every catalog in your Quable PIM account as separate bundles, a good starting point before drilling into any one of them.

When to use it
you need catalog codes for Get a Catalog or List Catalog Classification.
Watch out
follow it with a filter in your scenario if only a few catalogs matter, or every one will run through the next modules.
Quable PIM11

List Documents

Search

In Make“Retrieves a list of all documents.”

Collects all your Quable documents in one run, each as its own bundle, so you can copy or check them in bulk.

When to use it
a first sync into another tool, before the update trigger takes over the ongoing changes.
Watch out
a large account produces many bundles, and every module after it runs once per document.
Quable PIM13

List Variants

Search

In Make“Retrieves a list of all variants.”

Lists all the variants in your account, one bundle each, which helps when a whole range needs to reach another system.

When to use it
you are exporting variants to a shop or checking them against another source.
Watch out
for a single variant, Get a Variant costs far fewer operations than filtering this full list.
Need help

Need help automating Quable PIM with Make?

A person reads every message.

FAQ

Quable PIM and Make: common questions

01Is the Quable PIM Make integration free?
Yes, you can use it on Make's Free plan, because Quable PIM is a standard app and not one reserved to the Enterprise plan. The Free plan has limits though: 2 active scenarios, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios and allow runs of up to 40 minutes. Every plan counts usage in operations, one per module run, so a List module that returns many bundles uses more of your monthly allowance.
02What do you need to connect Quable PIM to Make?
A Quable PIM account that can authorize Make, and a Make account. Make's documentation lists no specific prerequisite for this app. You add any Quable module, click Create a connection, optionally name it, approve Make on the Quable page or paste the key Quable provides, then click Save. The connection is created once and shared by every Quable module in your scenarios. If the authorization window asks for access you do not have, the person who manages your Quable account can grant it.
03Does the Quable PIM trigger fire instantly in Make?
Yes. Watch Document Updates is an instant trigger: Quable PIM calls Make through a webhook as soon as a document is updated, so there is no polling schedule to configure. That is different from scheduled triggers, which Make checks at intervals (every 15 minutes by default on a new scenario). The trigger only covers updates to documents. For other starting points, such as reviewing all variants, you can put a List module after a schedule or after a trigger from another app.
04What if a Quable PIM module is missing in Make?
Use Make an API Call. It sends any request to the Quable PIM API with the connection you already have, so you are not limited to the 14 listed modules. Keep in mind that Make marks its own Quable documentation as limited, so it will not tell you which endpoint to call; you will need Quable's API reference for that. If a scenario gets hard to debug, the Make troubleshooting guide on this site covers the usual errors in plain language.
05Should you use Make or n8n for Quable PIM?
It depends on the tool your team already runs. Make offers Quable PIM as a standard app with 14 modules, including an instant trigger and Make an API Call for anything else. Many apps also have an n8n node, so check whether one exists for Quable PIM before deciding, and compare the modules each side gives you for your use case. The n8n vs Make comparison linked earlier on this page lays out the general differences between the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations