Resources · Make integration

BlueStone API - Public Make integrationAutomate BlueStone API - Public with Make.

Need BlueStone catalog data inside your other tools without copying it by hand? The BlueStone API - Public Make integration gives you 5 action modules that read products, categories and attributes. This guide connects your account, then walks you through a first scenario you can test safely.

Try the BlueStone API - Public integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the BlueStone API - Public Make integration do for you?

It lets Make, the no-code automation tool, fetch data from BlueStone API - Public inside a scenario, which is the automation you build as a chain of modules. The module names point to a product catalog: you can look up a product, a category, the products of a category, or attributes, then pass that data to any other app Make supports.

A product sheet that fills itself. A merchandiser types a product ID in a spreadsheet, Get Product by ID fetches the record, and the next module writes the details back next to it. Nobody opens BlueStone to copy a description again.

A category export on demand. Start from a category name with Get Categories by Name, then hand the result to Get Products by Category ID. Every product comes out as its own bundle, one item flowing to the next module, ready for a sheet, an email or a storefront.

Attributes where the sales team needs them. Get Attributes by ID reads attribute data so a quote, a spec sheet or a support reply can quote it without guessing.

Know the limits before you start. Every module here is an action, so nothing in BlueStone starts a scenario by itself: you run it on a schedule or behind another app's trigger. Make also says its documentation for this app is limited, because little public information exists about it. When a listed module falls short, Make an API Call reaches the rest of the API. If you are still weighing tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains operations and plans, and Make troubleshooting helps when a run fails.

Connect

How do you connect BlueStone API - Public to Make?

  1. 01

    Add a BlueStone module

    In your scenario, click the +, search for BlueStone API - Public and pick any of its modules. Then click Create a connection. A connection is your BlueStone account linked to Make once and reused by every BlueStone module after that.

  2. 02

    Name the connection

    This step is optional, but it pays off later. Give the connection a name that tells you which BlueStone account or environment it points to, so you pick the right one when a second scenario needs it.

  3. 03

    Authorize and save

    Depending on what BlueStone asks for, either approve Make on the BlueStone page that opens or paste the key BlueStone gives you. Click Save. The module can now read your data, and Make starts listing what it finds.

First scenario

Your first scenario with BlueStone API - Public

GoalWhen a new category name lands in your spreadsheet, Make finds that category in BlueStone and returns its products.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Add the trigger of the app that holds your list, for example a spreadsheet that watches for new rows.

  2. 02

    Look up the category

    Click the + on the right, add Get Categories by Name, pick your connection and map the category name from the row. Mapping means dragging a value from the previous module into the field.

  3. 03

    Fetch its products

    Add Get Products by Category ID. As its name says, it works from a category ID: map the one returned by the previous module instead of typing it by hand.

  4. 04

    Test with Run once

    Add a test row, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the products really belong to that category.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default, and never below 15 on the Free plan), then switch the scenario on. From now on, each new row gets its products.

Modules

What each BlueStone API - Public module does

BlueStone API - Public gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

BlueStone API - Public1

Get Attributes by ID

ActionIn the docs only

Hands you the attribute data behind an ID you already have, so a spec sheet or a reply to a customer can show it without anyone opening BlueStone.

When to use it
a previous module or a form already gives you the ID this module asks for, and you need the matching attributes in a document.
Watch out
it reads one ID per run, so each bundle it receives costs an operation, one execution counted on your plan.
BlueStone API - Public2

Get Categories by Name

ActionIn the docs only

Turns a human-readable category name into the category record Make can work with, which is usually the missing step between what people type and what the other modules expect.

When to use it
a teammate writes "Outdoor chairs" in a sheet and the rest of the scenario needs the matching category ID.
Watch out
a name can match more than one category, so run it once and check how many bundles come back before building on it.
BlueStone API - Public3

Get Product by ID

ActionIn the docs only

Brings back a single product when you already know its ID, which makes it the quickest way to enrich an order line, a ticket or a spreadsheet row with catalog data.

When to use it
another app sends you a product ID and you want the full record next to it.
Watch out
it needs the exact ID; if you only have a category, start with Get Products by Category ID instead.
BlueStone API - Public4

Get Products by Category ID

ActionIn the docs only

Lists the products of one category, each one arriving as a separate bundle that the next module handles on its own, ready to fill a sheet or a storefront.

When to use it
you need a whole range at once, for example to refresh a price list or a landing page for that category.
Watch out
a large category means many bundles, and every module after it spends one operation per product.
BlueStone API - Public5

Make an API Call

ActionIn the docs only

Opens the rest of the BlueStone API to your scenario, using the same connection as the other modules, so you are not stuck when the four ready-made lookups do not cover your need.

When to use it
the data you want is in BlueStone but no listed module fetches it.
Watch out
Make says its documentation for this app is limited, so get the endpoint details from BlueStone before you fill in the call.
Need help

Need help automating BlueStone API - Public with Make?

A person reads every message.

FAQ

BlueStone API - Public and Make: common questions

01Is the BlueStone API - Public Make integration free?
Yes, BlueStone API - Public is a standard app, so you can use it on the Make Free plan. That plan has its own limits: 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, allow unlimited active scenarios and 40 minutes of execution. Usage is counted in operations per month, one per module run on each bundle. Your BlueStone subscription is a separate matter this page does not cover.
02What do you need to connect BlueStone API - Public to Make?
You need a BlueStone account and a Make account. The Make documentation lists no extra prerequisite for this app. You add any BlueStone module, click Create a connection, optionally name it, then either authorize Make on the BlueStone page or paste the key BlueStone gives you, and click Save. Make notes its documentation for this app is limited, so it does not say which of the two methods applies. If you are unsure, ask whoever manages BlueStone in your company which credential your account uses.
03Does BlueStone API - Public trigger a Make scenario in real time?
No. The app has no trigger module, only 5 actions, so BlueStone never starts a scenario on its own. You have two ways to start one anyway. The first is a schedule on the first module: every 15 minutes by default, 15 minutes at minimum on the Free plan and 1 minute on paid plans. The second is a trigger from another app, such as a new spreadsheet row or a form submission, followed by the BlueStone modules. If an app or a script can call Make, a Make webhook can also start the scenario the moment it arrives.
04What if the BlueStone API - Public module you need is missing in Make?
Use Make an API Call. This module comes with the app and lets your scenario call any endpoint of the BlueStone API with the same connection as the four lookup modules. It covers whatever those modules do not, such as data they do not return. Keep in mind that Make says its documentation for BlueStone API - Public is limited because little public information exists, so the endpoint, method and expected parameters have to come from BlueStone itself. Test each call with Run once and read the returned bundle before you switch the scenario on.
05Should you use Make or n8n for BlueStone API - Public?
It depends on where the rest of your automations already live. On Make, this app gives you 5 modules, including Make an API Call, and it works from the Free plan. This page does not document whether n8n offers a node for BlueStone API - Public, so check n8n's own list before comparing the two for this app. The practical criteria are the same as for any tool choice: which platform your team already knows, which other apps the scenario has to reach, and how you want to follow runs and errors. The comparison page linked above goes through those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations