Resources · Make integration

Seller Assistant Make integrationAutomate Seller Assistant with Make.

Product research that fills itself in while you look at something else. The Seller Assistant Make integration gives you 15 modules: 11 actions and 4 searches. This page shows sellers how to link an API key and build a first scenario step by step.

Try the Seller Assistant integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Seller Assistant Make integration do?

The Seller Assistant Make integration lets Make, a no-code automation tool, call your Seller Assistant account for you. You build a scenario, the automation made of modules chained together, and each module asks Seller Assistant for one piece of information: a product, a sales estimate, a shipment.

A sourcing sheet that completes itself. Paste an ASIN in a spreadsheet, and a scenario runs Get Product Info, then Estimate Sales by ASIN and Get Product Restrictions, and writes the answers next to the code. Your list of leads stops depending on copy and paste.

Barcodes ready for a supplier. Convert ASIN to UPC or EAN turns the identifiers of a product list into the codes a wholesaler or a catalog tool expects, one bundle (one item passed between modules) at a time.

A view of your inbound shipments. List Inbound Plans, List Plan Shipments and List Shipment Items walk through your plans down to each item, so a team tool can show what is on its way.

What Make does not do here: the app has no trigger, so Seller Assistant never starts a scenario by itself. The scenario starts on the schedule you set or on another app. The documentation also warns that its own text is AI-generated, so double check a field before you rely on it. The same app often has an n8n node too; the n8n vs Make comparison lays out both tools, and Make training helps if Make is new to you. To size your plan, read Make pricing.

Connect

How do you connect Seller Assistant to Make?

  1. 01

    Generate your API key

    You need an active Seller Assistant account. In its settings, open the API Keys section, click Generate API Key and copy the key that appears on screen. Keep it handy for the next step.

  2. 02

    Open the connection window

    In your Make scenario, add any Seller Assistant module and click Create a connection. A connection is your Seller Assistant account linked to Make once, then reused by every module of the app.

  3. 03

    Paste the key and save

    Give it a label in Connection name if you like, which helps when several accounts coexist. Paste the API key you copied, follow the on-screen instructions, and the connection is ready.

First scenario

Your first scenario with Seller Assistant

GoalWhen a new ASIN lands in your sourcing sheet, Make fetches its product info and its restrictions from Seller Assistant.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app that holds your list of ASINs, such as a spreadsheet, as the first module of the flow.

  2. 02

    Add Get Product Info

    Click the + on the right of the first module, search Seller Assistant and choose Get Product Info. Click Create a connection and paste your API key.

  3. 03

    Map the ASIN

    In the module fields, map the ASIN coming from the previous module. Mapping means clicking the value from the earlier bubble instead of typing it, so each new row feeds the module.

  4. 04

    Chain Get Product Restrictions

    Add Get Product Restrictions after it with the same connection and the same mapped ASIN. You can then add a module that writes both answers back to your sheet.

  5. 05

    Test, schedule, switch on

    Click Run once and read the bundles each module received. When the output looks right, set the schedule on the first module (every 15 minutes by default) and switch the scenario on.

Modules

What Seller Assistant modules can you use in Make?

Seller Assistant gives you 15 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Seller Assistant1

Convert ASIN to UPC or EAN

ActionIn the docs only

You get the barcode behind an ASIN, as a UPC or an EAN, without looking it up by hand. It is the bridge between a marketplace listing and the codes suppliers use.

When to use it
before you send a product list to a wholesaler who asks for barcodes rather than ASINs.
Watch out
run it once on a known product and check which code comes back before you process a whole list.
Seller Assistant2

Estimate Sales by ASIN

ActionIn the docs only

Hand it an ASIN and it returns the sales estimate Seller Assistant computes for that product, so a lead in your sheet arrives with a demand figure attached.

When to use it
when you already know the exact product and want to rank several candidates before you order stock.
Watch out
an estimate stays an estimate; treat it as a sorting signal, not a forecast.
Seller Assistant3

Estimate Sales by BSR

ActionIn the docs only

This one starts from a best sellers rank instead of a product code and gives back an estimated sales volume. Handy when the rank is the only data point you have.

When to use it
a report or an export lists ranks but no ASINs, and you still want an order of magnitude.
Watch out
pick Estimate Sales by ASIN instead whenever the ASIN is available, since it targets the product directly.
Seller Assistant4

Get Inbound Plan

ActionIn the docs only

Pulls the details of one inbound plan into your scenario, so the plan you prepared in Seller Assistant can feed a tracker, a message or a sheet.

When to use it
you already hold the plan identifier, for example from List Inbound Plans, and need that single plan.
Watch out
it works on one plan at a time; to cover all of them, start with the list module.
Seller Assistant5

Get Keepa Product

ActionIn the docs only

Brings the Keepa record of a product into Make through your Seller Assistant connection, so the product data you would look up by hand lands in your scenario.

When to use it
you have one product in mind and want its Keepa data next to your own notes.
Watch out
to find products rather than read a known one, the search module Search Keepa Products is the better start.
Seller Assistant6

Get Product Info

ActionIn the docs only

The workhorse of a sourcing scenario: give it a product and it returns what Seller Assistant knows about it, ready to map into the next module.

When to use it
a new ASIN shows up in your sheet, and you want its details filled in without opening Seller Assistant at all.
Watch out
the documentation does not list the values it returns. Read the bundle after Run once to see what you can map.
Seller Assistant7

Get Product Restrictions

ActionIn the docs only

Tells you whether a product carries selling restrictions, which saves you from buying stock you may not be allowed to list.

When to use it
right after Get Product Info in a sourcing flow, so every candidate is checked before anyone places an order.
Watch out
use a filter after this module to stop the scenario on restricted products instead of writing them to your list.
Seller Assistant8

Get Product Statistics

ActionIn the docs only

Returns the statistics Seller Assistant keeps on a product, as data you can store in a sheet or compare from one run to the next.

When to use it
you want a snapshot of a product saved to a sheet each time the scenario runs, to follow how it moves.
Watch out
each call counts as one operation, meaning one module run that Make counts on your plan.
Seller Assistant9

Get Shipment Fees

ActionIn the docs only

Fetches the fees tied to a shipment, so the cost of sending stock shows up in your margin sheet rather than in a surprise later.

When to use it
after List Plan Shipments, to attach the fees to each shipment you plan to send.
Watch out
it needs a shipment to work on; map the identifier from an earlier module rather than typing it.
Seller Assistant10

Get shipment

ActionIn the docs only

Reads a single shipment and hands its details to the rest of the scenario, useful to post a status in a team channel or update a row.

When to use it
you track one shipment you already know and want its latest details on demand.
Watch out
for the items inside the shipment, add List Shipment Items; this module stays at the shipment level.
Seller Assistant11

List Inbound Plans

SearchIn the docs only

Returns your inbound plans as a list, which gives a scenario the starting point for any overview of what you are preparing to send.

When to use it
at the top of a reporting flow, before Get Inbound Plan or List Plan Shipments.
Watch out
as a search, it can return zero, one or several bundles, and every following module runs once per plan.
Seller Assistant12

List Plan Shipments

SearchIn the docs only

Lists the shipments that belong to one inbound plan, so you can follow a plan down to each shipment it contains.

When to use it
after List Inbound Plans, to break every plan into its shipments before you fetch fees or items.
Watch out
a plan with no shipment yet returns nothing, and the modules after it simply do not run.
Seller Assistant13

List Shipment Items

SearchIn the docs only

Opens a shipment and returns the items inside it, one bundle per item, ready for a packing list or a stock sheet.

When to use it
your team wants to see, product by product, what a given shipment contains.
Watch out
a large shipment produces many bundles, and each module placed after this one uses operations for every item.
Seller Assistant14

Make an API Call

ActionIn the docs only

Covers what the other modules leave out: it calls any endpoint of the Seller Assistant API with the connection you already set up.

When to use it
you need a piece of data none of the listed modules returns, and the API documentation of Seller Assistant describes it.
Watch out
you write the request yourself here, so keep the API documentation open and test with Run once.
Seller Assistant15

Search Keepa Products

SearchIn the docs only

Looks for products in Keepa through Seller Assistant and returns every match, which turns an idea into a list of candidates to study.

When to use it
you explore a niche and want matching products dropped into a sheet, then checked by Get Product Restrictions.
Watch out
each result is a separate bundle, so add a filter before costly steps to keep operations under control.
Need help

Need help automating Seller Assistant with Make?

A person reads every message.

FAQ

Seller Assistant and Make: common questions

01Is the Seller Assistant Make integration free?
Yes on the Make side: Seller Assistant is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, stops a run after 5 minutes and counts usage in operations, one per module run. Paid plans lower the interval to 1 minute and lift the scenario cap. Your Seller Assistant subscription is separate, and an active account with an API key is required to connect.
02What do you need to connect Seller Assistant to Make?
An active Seller Assistant account and an API key. In your Seller Assistant settings, open the API Keys section, click Generate API Key and copy the value shown. Then add any Seller Assistant module in Make, click Create a connection, optionally name it, and paste the key. The connection is saved once and reused by all fifteen modules of the app, so you never paste the key twice, whichever module you add next.
03Can Seller Assistant start a Make scenario in real time?
No. Seller Assistant has no trigger module in Make, scheduled or instant, so it cannot start a scenario on its own. You start the flow another way: set a schedule on the first module, every 15 minutes by default, or place another app first, such as a spreadsheet where new ASINs arrive or a webhook from Make. Seller Assistant modules then run as steps inside that flow, once per bundle they receive.
04What if a Seller Assistant module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Seller Assistant API with the connection you already have, so a request the 15 listed modules do not cover stays possible. You write the request yourself, following the Seller Assistant API documentation. Keep in mind that the Make documentation for this app is marked as AI-generated, so check any field against the vendor before you depend on it, and test the call with Run once.
05Should you use Make or n8n for Seller Assistant?
It depends on the tool you already run. Make offers Seller Assistant as a native app with 15 modules and a visual editor where you test with Run once. The same app often exists as an n8n node too, so check that side before you decide. If your other automations already live in Make, keeping Seller Assistant there means one place to maintain; the choice rests on your stack rather than on the app.
Same platform

Other docs you might need on this stack.

Browse all integrations