Resources · Make integration

Sellercloud Make integrationAutomate Sellercloud with Make.

Can Make take the copy-paste out of your Sellercloud orders and stock? The Sellercloud Make integration offers 28 modules: 3 triggers, 16 actions and 9 searches. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Sellercloud integration on Make See the 28 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Sellercloud Make integration do for you?

The Sellercloud Make integration links your Sellercloud account to Make, a visual tool where you chain apps without code. You build a scenario (the automation itself) out of modules (one brick each: a trigger, an action or a search), and Make passes orders, products or jobs from one brick to the next.

Orders that reach the rest of your tools. Watch New Orders picks up every order created in Sellercloud, and Get a Customer adds the buyer record, so your helpdesk or spreadsheet receives the full picture without a manual export.

Payments recorded where they belong. When a check or a bank transfer is confirmed elsewhere, Receive Check or Receive Manual Payment writes it onto the matching order, and Update Quickbooks Status flags orders as exported or unexported for your bookkeeping.

Reports that fetch themselves. Create Queued Job starts a Sellercloud job from a scheduled task ID, Watch Queued Jobs spots it once completed, and Get Output File from Queued Job hands you the file (CSV jobs only, today).

Keep the limits in mind. All 3 triggers are scheduled: Make checks Sellercloud on the scenario's schedule, it does not get pinged the moment something happens. And the Make documentation for this app is flagged as AI-generated from Sellercloud's own docs, so confirm anything critical with Sellercloud. The same app may also exist as an n8n node; the n8n vs Make comparison helps you weigh both, and our Make review covers the tool itself. Stuck on a run? See Make troubleshooting.

Connect

How do you connect Sellercloud to Make?

01
Add a Sellercloud module
In your Make account, open a scenario, add any Sellercloud module and click Create a connection. A connection is your Sellercloud account linked to Make once, then reused by every Sellercloud module you add later.
02
Name the connection
The Connection name field is optional, but a clear label pays off when you run several Sellercloud accounts or users. Something like the store name plus the purpose of the integration is enough to recognize it later.
03
Enter your credentials
Type the Username and Password of an active Sellercloud account, or follow the on-screen instructions, then save. Make uses them to obtain its access token, and the module can now list what your account is allowed to read.

First scenario

Your first scenario: fetch finished job files

GoalWhen a queued job completes in Sellercloud, Make downloads its output file and passes it on.

01
Create the scenario
From the Scenarios page, create a new scenario and click the big + to place the first module. The empty canvas is where every step of the automation will sit.
02
Add Watch Queued Jobs
Search for Sellercloud, pick Watch Queued Jobs and click Create a connection (or reuse one). This trigger returns the jobs that completed since the previous check.
03
Add the output file module
Click the + on the right of the trigger, choose Get Output File from Queued Job and map the job ID coming from the trigger. Remember that only jobs returning CSV are supported.
04
Test with Run once
Click Run once after a job has finished in Sellercloud. Each module shows a bubble with the bundles it received, one bundle per job, so you can check the file came through.
05
Schedule and switch on
Open the clock on the first module under Scheduling. A new scenario checks every 15 minutes by default, and the Free plan cannot go faster. Then switch the scenario on.

Triggers

Triggers: what starts a Sellercloud scenario

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

Sellercloud1Watch New Orders

Watch New Orders

Scheduled trigger

In Make“Returns all newly created orders.”

Every order freshly created in Sellercloud lands in your scenario as its own bundle (one item passed to the next module), ready to be copied, announced or enriched elsewhere.

How it fires

scheduled. Make checks the app on the scenario's schedule, which is every 15 minutes by default.

When to use it

you care about new orders only, for example to post each sale in a team channel or open a picking task.

Watch out

it only returns newly created orders; to receive orders matching settings you choose, use Watch Orders.

Sellercloud2Watch Orders

Watch Orders

Scheduled trigger

In Make“Returns all orders based on your configuration.”

Here the scenario receives orders that match the configuration you set in the module, not just the newest ones, which gives you a filtered stream of the orders that matter to one workflow.

How it fires

scheduled. Make checks the app on the scenario's schedule rather than waiting for a signal from Sellercloud.

When to use it

one team only needs a slice of your orders and you would rather filter at the source than after the fact.

Watch out

test the settings with Run once before switching on, so you see exactly which orders the configuration lets through.

Sellercloud3Watch Queued Jobs

Watch Queued Jobs

Scheduled trigger

In Make“Returns Completed Jobs since the last run.”

You get a bundle for each Sellercloud job that has completed since the last run, which turns long exports and imports into something the rest of your tools can react to.

How it fires

scheduled. Make checks Sellercloud on the scenario's schedule, so a finished job surfaces at the next check, not the second it ends.

When to use it

you launch reports as queued jobs and want the result filed or shared without watching the queue.

Watch out

pair it with Get Output File from Queued Job, since the trigger alone tells you a job ended but does not hand over its file.

Modules

Actions and searches for Sellercloud

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

Sellercloud1

Adjust Physical Inventory

Action

In Make“Adjusts a specific products inventory.”

This action corrects the physical stock of one product in Sellercloud, so a count fixed in a warehouse app or a spreadsheet reaches your catalog without anyone retyping it.

When to use it

a return, a damaged unit or a manual correction should move the stock from where it currently stands.

Watch out

if you hold the final figure after a full count, Set Physical Inventory is the better fit.

Sellercloud2

Create an Order

Action

In Make“Creates a new order in SellerCloud.”

A new order appears in Sellercloud from data collected elsewhere, which saves you from keying in sales that happen outside your usual channels.

When to use it

a form, a quote tool or a marketplace that Sellercloud does not cover produces an order that belongs in your order list.

Watch out

guard against duplicates with Search Orders before creating, in case the same sale is sent twice.

Sellercloud3

Create Queued Job

Action

In Make“Create a queued job using scheduled task ID.”

Starting a Sellercloud queued job from Make means an export or process defined as a scheduled task can be launched by an event instead of by hand.

When to use it

a report should be produced right after something happens in another tool, and you already have the scheduled task ID in Sellercloud.

Watch out

the job runs inside Sellercloud; catch its result later with Watch Queued Jobs.

Sellercloud4

Delete an Order

Action

In Make“Deletes a specific order by order ID.”

Pass it an order ID and the matching order disappears from Sellercloud, which keeps test orders or cancelled duplicates out of your figures.

When to use it

a cleanup scenario removes orders you have already identified as unwanted, for instance duplicates flagged by a search.

Watch out

treat deletion as final and add a filter before this module so only the orders you really mean to remove reach it.

Sellercloud5

Get a Customer

Action

In Make“Retrieves a specific customer by customer ID.”

With a customer ID in hand, this module brings back that customer's full Sellercloud record, handy when an order only carries the ID and you need the person behind it.

When to use it

right after an order trigger, to send the buyer's details to a CRM or a support tool.

Watch out

without an ID, reach for Search Customers instead.

Sellercloud6

Get an Order

Action

In Make“Gets a specific order by order ID.”

One order, fetched by its ID with all its current details, so a later step always works on up-to-date data rather than an older copy.

When to use it

another app sends you an order ID, for example a support ticket, and you need the order before replying or updating it.

Watch out

it returns a single order; to scan several, use Search Orders.

Sellercloud7

Get a Purchase Order

Action

In Make“Retrieves a specific purchase order by purchase order ID.”

Retrieving a purchase order by its ID gives your scenario the supplier side of the story, what was ordered and from whom, without opening Sellercloud.

When to use it

a supplier email or a receiving tool mentions a purchase order ID and you want its details logged or shared with the buying team.

Watch out

no ID yet? Search Purchase Orders finds it first.

Sellercloud8

Get a Warehouse

Action

In Make“Retrieves a specific warehouse by warehouse ID.”

Feed it a warehouse ID and it returns that warehouse's record, which is useful when other modules only give you the ID and a person needs a readable name.

When to use it

you build a stock alert or a report and want to show the actual warehouse instead of a number.

Watch out

to see every warehouse at once, Search Warehouses is the right tool.

Sellercloud9

Get Inventory Info for a Product

Action

In Make“Get inventory info for a specific product.”

Stock information for one product comes back into the scenario, so you can check availability before promising anything to a customer or a channel.

When to use it

a new order arrives and you want to confirm the item is in stock before routing it.

Watch out

for a batch of products, Search Inventory Info for Multiple Products saves you from one call per item.

Sellercloud10

Get Output File from Queued Job

Action

In Make“Get Output File from a Completed Queued Job, by Job ID. Currently supports Jobs that return CSV format.”

Once a queued job has completed, this module downloads the file it produced, so the export can be stored, emailed or parsed in the next step.

When to use it

straight after Watch Queued Jobs, mapping the job ID from the trigger.

Watch out

only jobs that return CSV are supported for now, so other output formats will not come through this module.

Sellercloud11

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

When none of the ready-made modules covers what you need, this one calls any endpoint of the Sellercloud API with the connection you already set up.

When to use it

you need a Sellercloud feature missing from the list, such as an update the other modules do not offer.

Watch out

you write the request yourself, so keep the Sellercloud API documentation open while you fill it in.

Sellercloud12

Receive Check

Action

In Make“Add a payment via check to the order specified.”

A check payment gets recorded against the order you name, so payment status in Sellercloud follows what your finance team already knows.

When to use it

checks are logged in a spreadsheet or an accounting tool and the matching orders should show as paid.

Watch out

payments that are not checks belong in Receive Manual Payment.

Sellercloud13

Receive Manual Payment

Action

In Make“Adds a manual payment to the order specified.”

Use it to attach a manual payment to a given order, closing the gap between money received outside Sellercloud and the order record.

When to use it

a bank transfer or an in-person payment is confirmed in another tool and the order must reflect it.

Watch out

make sure the scenario cannot run twice for the same payment, or the order will show it twice.

Sellercloud14

Set Physical Inventory

Action

In Make“Sets the physical inventory of a product.”

This action replaces the physical stock of a product with the figure you provide, which is what you want after a real count on the shelves.

When to use it

a stocktake app or a sheet holds the counted quantity and Sellercloud should match it exactly.

Watch out

the value overwrites the old one; to nudge stock up or down, use Adjust Physical Inventory.

Sellercloud15

Update Inventory Info for Single Product

Action

In Make“Updates inventory info for single product.”

Inventory details of one product are updated from your scenario, keeping Sellercloud aligned with the source that really owns that information.

When to use it

a supplier feed or an internal sheet changes the inventory info of a specific product.

Watch out

it handles one product per run, so a list of products means one operation (one module execution counted on your plan) each.

Sellercloud16

Update Quickbooks Status

Action

In Make“Updates the quickbooks status for one or many orders as exported or unexported.”

Mark one or many orders as exported or unexported to QuickBooks, so your bookkeeping and Sellercloud agree on what has already been sent.

When to use it

after an export to your accounting tool succeeds, or to reset orders that need to go out again.

Watch out

resetting orders to unexported can lead to a second export, so check the list first.

Sellercloud17

List Shipping Containers

In Make“List Shipping Containers”

You get the shipping containers from Sellercloud as separate bundles, which lets a scenario review or report on them one by one.

When to use it

a logistics sheet or dashboard should reflect the containers Sellercloud knows about.

Watch out

as a search, it can return many items; each one flowing into the next module costs an operation.

Sellercloud18

Search Companies

In Make“Searches for specific companies or returns all companies.”

Look up specific companies in Sellercloud, or pull all of them, to reuse those records in another tool.

When to use it

you sync companies to a CRM, or need to check a company exists before acting on it.

Watch out

leaving the search open returns every company, so narrow it when you only need one.

Sellercloud19

Search Customers

In Make“Searches for a specific customer or returns all customers.”

Finding a customer when you lack the ID starts here: search for a particular customer or list them all.

When to use it

a form or an email gives you a name or an address, and you need the Sellercloud customer before creating an order.

Watch out

a search can match zero, one or several customers; add a filter so later steps know what to do with each case.

Sellercloud20

Search Inventory Info for Multiple Products

In Make“Searches products for inventory info or returns all products inventory info.”

Stock information for several products at once, or for the whole catalog, arrives as one bundle per product.

When to use it

you build a stock report or push availability to another channel for a range of items.

Watch out

returning every product can mean a lot of bundles and operations; narrow the search whenever you can.

Sellercloud21

Search Items

In Make“Searches all items (catalogs in api).”

Browse your Sellercloud items, called catalogs in the API, to bring product records into a scenario.

When to use it

you mirror the catalog to a sheet, a website or a marketing tool.

Watch out

the naming differs between Make and the API, so if the Sellercloud docs mention catalogs, this is the module they mean.

Sellercloud22

Search Orders

In Make“Searches for specific orders or returns all orders.”

Specific orders, or all of them, come back one bundle each, which is the way to check, count or export orders in bulk.

When to use it

you look for an order before creating a new one, or gather orders for a report.

Watch out

unlike the Watch triggers, it does not remember what it already returned, so a scenario running it repeatedly sees the same orders again.

Sellercloud23

Search Purchase Orders

In Make“Searches for specific purchase orders or returns all purchase orders.”

Pull specific purchase orders, or the full list, so the buying side of Sellercloud can feed a sheet or a supplier tool.

When to use it

your buyers live in a spreadsheet or a supplier portal, and they want the purchase orders to show up there.

Watch out

for one known purchase order, Get a Purchase Order is simpler and returns a single bundle.

Sellercloud24

Search Queued Jobs

In Make“Searches all queued jobs.”

This search lists your Sellercloud queued jobs, finished or not, which is handy to audit the queue from outside Sellercloud.

When to use it

you want a snapshot of all jobs, for instance to spot one stuck in the queue.

Watch out

it does not only return new completions; for that, Watch Queued Jobs is the trigger.

Sellercloud25

Search Warehouses

In Make“Searches for specific warehouses or returns all warehouses.”

Specific warehouses, or every warehouse, return as separate bundles for reports or lookups.

When to use it

a scenario loops over warehouses to compare stock, or needs the right warehouse before adjusting inventory.

Watch out

if you already have the ID, Get a Warehouse avoids a broad search.

Need help

Need help automating Sellercloud with Make?

A person reads every message.

FAQ

Sellercloud and Make: common questions

01Is the Sellercloud Make integration free?

Yes, Sellercloud is a standard app in Make, so it works from the Free plan. The Free plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) go down to a 1 minute interval and count usage in operations per month. You still need your own Sellercloud account.

02What do you need to connect Sellercloud to Make?

You need an active Sellercloud account with a valid username and password. In a Sellercloud module, click Create a connection, give it a name if you like, then enter those credentials or follow the on-screen instructions. If several applications use Sellercloud, create a separate user (employee) for each integration, including Make, so every tool has its own login and you can trace what each one did. Once saved, every Sellercloud module in your scenarios reuses that same connection.

03Do Sellercloud triggers in Make fire in real time?

No. All 3 Sellercloud triggers, Watch New Orders, Watch Orders and Watch Queued Jobs, are scheduled: Make checks Sellercloud on the scenario's schedule. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. None of the triggers is instant, so an event shows up at the next check. If a few minutes of delay is a problem, a faster schedule on a paid plan is the lever.

04What if a Sellercloud module is missing in Make?

Use Make an API Call. It calls any endpoint of the Sellercloud API with the connection you already set up, which covers what the 28 listed modules do not. You write the request yourself, so keep the Sellercloud API documentation at hand. Also note that Get Output File from Queued Job currently supports CSV jobs only, and that Make flags its Sellercloud documentation as AI-generated, so confirm key details with Sellercloud.

05Should you use Make or n8n for Sellercloud?

It depends on what you need. With Make you get 28 ready-made Sellercloud modules, 3 scheduled triggers, 16 actions and 9 searches, plus Make an API Call for anything else, all in a visual editor. The same app often has an n8n node too, so check what that node covers for your use case before deciding. Compare the modules you need on both sides rather than the tool names. The n8n vs Make comparison linked above lays out the criteria.

Add a Sellercloud module

Name the connection

Enter your credentials

Create the scenario

Add Watch Queued Jobs

Add the output file module

Test with Run once

Schedule and switch on

Need help automating Sellercloud with Make?