Resources · Make integration

Shift4Shop Make integrationAutomate Shift4Shop with Make.

What could your store do on its own the moment an order lands? The Shift4Shop Make integration gives you 7 instant triggers, 18 actions and 3 searches for orders, customers, carts and products. This guide is for store owners new to Make: connect the account, build a first scenario, pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Shift4Shop Make integration do for your store?

The Shift4Shop Make integration links your online store to Make, a tool where you build automations without code. Each automation is a scenario, a chain of modules, and each module is one brick: a trigger that starts things, an action that changes something in the store, or a search that pulls a list.

Orders that reach the right people. Watch New Orders starts a scenario as soon as a buyer checks out, and Get an Order pulls the full order so the next module (a message, a spreadsheet row) gets clean data. Watch Order Status Change follows the same order later in its life.

A catalog that stays in step with your stock. Watch Products Stock Change reacts when inventory moves, and Update a Product Discount or Update a Product Option adjust the listing without opening the admin panel. Create a Product adds items that arrive from another tool.

A customer base that other tools can use. Watch New Customers hands each new account to your CRM or mailing tool, while List Customers pulls the whole base when you need a bulk export.

Some limits are worth knowing up front. Every trigger here is instant, so there is no clock to set on them, and anything the listed modules skip goes through Make an API Call. Before comparing tools, the Make review and Make pricing pages give the full picture, and n8n vs Make helps if n8n is also on your list.

Connect

How do you connect Shift4Shop to Make?

  1. 01

    Add a Shift4Shop module

    In your scenario, search for Shift4Shop, pick a module and click Create a connection. A connection is your store account linked to Make once, then reused by every Shift4Shop module you add later.

  2. 02

    Create an app in the Developer Portal

    In Shift4Shop, open the Developer Portal dashboard, click Add New, give the application a name and, if asked, paste the callback URI https://www.integromat.com/oauth/cb/a3dcart. Click Create App, then copy the Client ID and the Client secret.

  3. 03

    Paste the credentials into Make

    Back in Make, type a label in Connection name if you like (it is optional), then paste the credentials you just copied or follow the on-screen prompts. Make saves the connection and the module can now read your store.

First scenario

Your first scenario: new products from your catalog sheet

GoalWhen a new product line appears in the tool where you keep your catalog, Make creates the product in Shift4Shop.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Pick the app where your product list lives, such as a spreadsheet, and choose its module that watches new rows.

  2. 02

    Add Create a Product

    Click the + to the right of the first module, search for Shift4Shop and choose Create a Product. Select the connection you set up earlier, or click Create a connection.

  3. 03

    Map the product data

    Fill the fields of Create a Product by dragging values from the first module into them; Make shows which fields the product accepts once the connection exists. Each row arrives as a bundle, one item passing from one module to the next.

  4. 04

    Test with Run once

    Add a test row to your list, then click Run once. Make runs the scenario one time and shows the bundles each module received. Check that the product now exists in your store.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run is an operation, the unit Make counts on your plan.

Triggers

Triggers: what starts a Shift4Shop scenario

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

Shift4Shop1Watch New Customers

Watch New Customers

Instant trigger

In MakeTrigger for new customers.

Every account opened in your store becomes a fresh bundle in Make, ready to be sent to your CRM, your mailing list or a welcome sequence. You stop copying new sign-ups by hand.

How it fires
instant: Shift4Shop calls Make through a webhook as soon as the customer is created, so there is no schedule to tune.
When to use it
you want every new buyer added to your email tool with the right tag.
Watch out
Make asks you to click Create a webhook before Create a connection on this module.
Shift4Shop2Watch New Orders

Watch New Orders

Instant trigger

In MakeTrigger for new orders.

Each checkout in your store reaches Make as one bundle, and the rest of the scenario can notify a team, log a sale or prepare fulfilment.

How it fires
instant: Shift4Shop calls Make through a webhook as soon as the order is placed.
When to use it
the warehouse needs a message the moment an order comes in.
Watch out
it catches new orders only. To follow an order after checkout, pair it with Watch Order Status Change rather than rereading orders with List Orders.
Shift4Shop3Watch New Products

Watch New Products

Instant trigger

In MakeTrigger for the new products.

Adding an item to the catalog is enough to start the scenario, which lets you push the new listing to a marketing tool, a shared sheet or a team channel without a second entry.

How it fires
instant: Shift4Shop calls Make through a webhook as soon as the product is added.
When to use it
your social media manager should hear about every new product the day it goes live.
Watch out
edits to existing items do not count here; they belong to Watch Products Change.
Shift4Shop4Watch Order Status Change

Watch Order Status Change

Instant trigger

In MakeTrigger for order status change.

Customers want to know where their parcel stands, and this trigger tells Make each time an order moves to another status, so a scenario can send the update for you.

How it fires
instant: Shift4Shop calls Make through a webhook as soon as the status changes.
When to use it
you send a shipping email or a text when an order is marked as shipped.
Watch out
if the same scenario also runs Update an Order Shipment, a shipment update may well change the status and start it again. A filter keeps it from looping.
Shift4Shop5Watch Products Change

Watch Products Change

Instant trigger

In MakeTrigger for the product changes.

Price edits, new descriptions, renamed items: any change to a product reaches Make, which keeps copies of your catalog in other tools accurate without a manual export.

How it fires
instant: Shift4Shop calls Make through a webhook as soon as the product is edited.
When to use it
a marketplace feed or a price sheet must match the store after every edit.
Watch out
a scenario that starts here and runs Update a Product Feature on the same item will most likely edit it again. Guard it with a filter.
Shift4Shop6Watch Products Deleted

Watch Products Deleted

Instant trigger

In MakeTriggers when a product has been deleted.

When an item leaves the catalog, the tools that still list it need to know. This trigger hands Make the removed product so you can archive it or take it down elsewhere.

How it fires
instant: Shift4Shop calls Make through a webhook as soon as the product is deleted.
When to use it
you mirror your catalog on another channel and want dead listings gone without checking by hand.
Watch out
the product no longer exists in the store, so a later Get a Product on it has nothing to return.
Shift4Shop7Watch Products Stock Change

Watch Products Stock Change

Instant trigger

In MakeTrigger for the product stock changes.

Inventory moves are what this trigger follows: each stock change on a product sends a bundle to Make, which can warn a buyer, update a sheet or reorder from a supplier.

How it fires
instant: Shift4Shop calls Make through a webhook as soon as the stock level changes.
When to use it
purchasing should hear about it when a best seller runs low.
Watch out
sales move stock too, so a busy store can send many bundles. Put a filter right after it to keep only the levels you care about and save operations.
Modules

Shift4Shop modules: what each one does

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

Shift4Shop1

Create a Cart

Action

In MakeCreates a cart.

Opens a new cart in your store from Make, so a quote or an order taken outside the site can be rebuilt as a real Shift4Shop cart.

When to use it
a sales rep closes a deal by phone and wants the buyer to finish checkout online.
Watch out
a cart is not an order yet; nothing is sold until the buyer pays.
Shift4Shop2

Create a Customer

Action

In MakeCreates a customer.

Adds a customer account to the store with data mapped from another app, which saves retyping contacts that already live in your CRM or on a form.

When to use it
a wholesale lead is approved in your CRM and should get a store account right away.
Watch out
run a List Customers search first if the person might already have an account, to avoid duplicates.
Shift4Shop3

Create a Product

Action

In MakeCreates a Product.

Puts a new item in your catalog without touching the admin panel. You map the details from wherever your product data already sits.

When to use it
a supplier sheet or a product database is your source of truth and the store should follow it.
Watch out
the scenario creates a product on every run it receives, so check the source rows are truly new before letting it loose.
Shift4Shop4

Delete a Cart

Action

In MakeDeletes a cart.

Removes a cart from the store, which is handy to clean up the test carts or leftover drafts a scenario may have created.

When to use it
a quote built with Create a Cart was cancelled and the cart should disappear.
Watch out
assume a deletion is final, since Make offers no undo. Test on a dummy cart with Run once before you point it at real ones.
Shift4Shop5

Delete a Customer

Action

In MakeDeletes a customer.

Erases a customer account, the step you need when a person asks for their data to be removed and that request is handled in another tool.

When to use it
a deletion request is approved in your ticketing tool and the store must follow.
Watch out
treat it as final. Pull the record with Get a Customer first if you need to keep a copy.
Shift4Shop6

Delete a Product

Action

In MakeDeletes a product.

Takes an item out of the catalog for good, driven by a decision made somewhere else, such as a discontinued line in your inventory sheet.

When to use it
a supplier ends a product and the listing must vanish from the store.
Watch out
treat it as final; it will probably also start Watch Products Deleted if another scenario listens to it.
Shift4Shop7

Get a Cart

Action

In MakeGets a cart.

Reads one cart and returns its content as a bundle, so the next modules can see what the shopper put in it.

When to use it
a support agent needs the cart contents attached to a ticket before calling the customer back.
Watch out
it reads a single cart you already know; to browse many records, the List modules are the right tool.
Shift4Shop8

Get a Customer

Action

In MakeGets a customer.

Fetches the full record of one customer, which fills the gaps when a trigger or another app only gives you a reference to that person.

When to use it
an order scenario needs the buyer's details to address a thank-you note.
Watch out
it returns one customer. If you do not know which one yet, search with List Customers instead.
Shift4Shop9

Get an Order

Action

In MakeGets an order.

Returns everything the store holds about one order, so a scenario started by a status change can still work with the complete details.

When to use it
Watch Order Status Change fires and the next module needs the order lines to build a delivery note.
Watch out
there is no Create an Order module in this app; Get an Order only reads existing ones.
Shift4Shop10

Get a Product

Action

In MakeGets a product.

Pulls a single product with its data, the quick way to enrich a bundle that only carries a product reference.

When to use it
a stock alert should show the product name and price, not just a number.
Watch out
a deleted item is gone from the store, so chaining it after Watch Products Deleted leaves it with nothing to read.
Shift4Shop11

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Covers whatever the other modules leave out: any endpoint of the Shift4Shop API can be called from your scenario, with the same connection.

When to use it
you need an object or an operation that none of the 28 modules handles.
Watch out
you write the request yourself, so keep the Shift4Shop API documentation open and test with Run once before going live.
Shift4Shop12

Update a Cart

Action

In MakeUpdates a cart.

Edits a cart that already exists, which lets a scenario adjust its contents after the first draft without starting over.

When to use it
a buyer confirms an extra item by email and the sales team wants the cart updated before checkout.
Watch out
you need the cart's reference; keep it from the Create a Cart step or look it up with Get a Cart.
Shift4Shop13

Update a Customer

Action

In MakeUpdates a customer.

Changes the details of an existing customer, so a fix made in your CRM also lands in the store and both records stay alike.

When to use it
a client moves offices and updates the address in your CRM first.
Watch out
if a Shift4Shop change also updates the CRM, the two scenarios can bounce edits back and forth; pick one side as the master.
Shift4Shop14

Update an Order Item

Action

In MakeUpdates an order's item.

Adjusts one line inside an order, useful when a product is swapped or corrected after the purchase and the order record must reflect it.

When to use it
the warehouse replaces an out-of-stock variant and logs the swap in its own tool.
Watch out
it acts on one item of one order; fetch the order with Get an Order first to know which line to change.
Shift4Shop15

Update an Order Shipment

Action

In MakeUpdates an order's shipment.

Writes shipping news back to the order, so the store reflects what your carrier or warehouse tool already knows.

When to use it
your fulfilment app confirms a parcel left and you want the order updated without logging in.
Watch out
the change may start Watch Order Status Change in another scenario; make sure that chain does not call this module again.
Shift4Shop16

Update a Product Discount

Action

In MakeUpdates a product's discount.

Sets or changes the discount on a product, letting a promotion planned elsewhere go live in the store without manual edits.

When to use it
a marketing sheet lists the items on sale and the store prices should follow it.
Watch out
the edit will likely start Watch Products Change; filter that scenario if it writes back to the same item.
Shift4Shop17

Update a Product Feature

Action

In MakeUpdates a product's feature.

Edits a feature of a product, the kind of detail shoppers compare, so your spec source and the listing say the same thing.

When to use it
the product team updates specs in a database and the store must match.
Watch out
it changes one product at a time; for a whole range, place List Products before it so each item passes through.
Shift4Shop18

Update a Product Option

Action

In MakeUpdates a product's option.

Changes an option on a product, such as the choices a buyer picks before adding it to the cart, straight from a scenario.

When to use it
a colour or size runs out at the supplier and the choice should change in the store.
Watch out
an option is not a feature; to change a descriptive detail rather than a choice, Update a Product Feature is the module to try.
Shift4Shop19

List Customers

Search

In MakeLists all customers.

Returns your customers as a series of bundles, one per person, so the rest of the scenario can process them one by one.

When to use it
you move your whole customer base into a new email tool.
Watch out
every bundle that goes through later modules costs operations. Add a filter early if you only need part of the list.
Shift4Shop20

List Orders

Search

In MakeLists all orders.

Pulls orders in bulk, each arriving as its own bundle, which is what you need for a report or a backfill of past sales.

When to use it
you connect a new accounting tool and want the existing orders in it too.
Watch out
for new orders only, Watch New Orders is lighter; a search that rereads everything spends operations on data you already have.
Shift4Shop21

List Products

Search

In MakeLists all products.

Brings the catalog into the scenario item by item, the starting point for any change you want to apply across many products.

When to use it
you copy the full catalog into a sheet before a pricing review.
Watch out
a search can return zero, one or many bundles, so the modules after it run once per product.
Need help

Need help automating Shift4Shop with Make?

A person reads every message.

FAQ

Shift4Shop and Make: common questions

01Is the Shift4Shop Make integration free?
Yes, on the Make side. Shift4Shop is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lift those limits, with a minimum interval of one minute and unlimited active scenarios, and usage is counted in credits per month. You still need your own Shift4Shop subscription, which Make does not cover.
02What do you need to connect Shift4Shop to Make?
Two things on the Shift4Shop side: a developer account and a merchant store subscription with an API token. From the Developer Portal dashboard, you add a new application, give it a name, enter the callback URI if asked, then copy the Client ID and the Client secret. In Make, you click Create a connection on any Shift4Shop module, name the connection if you want and paste those credentials. For an instant module, Make asks you to click Create a webhook first.
03Do Shift4Shop triggers in Make react in real time?
Yes. All 7 Shift4Shop triggers are instant: the store calls Make through a webhook as soon as the event happens, whether that is a new order, a new customer, a status change or a stock movement. You will see the lightning badge on these modules in the editor. That also means the 15 minute interval of the Free plan does not delay them, since Make is not polling on a schedule. Only scenarios that start with another app or a List search depend on the clock.
04What if a Shift4Shop module is missing in Make?
Use Make an API Call. It lets you call any endpoint of the Shift4Shop API from your scenario with the connection you already set up, so you are not stuck with the 18 actions and 3 searches on the list. Nothing in the list creates an order, for instance, and this module is the place to look for such gaps. You write the request yourself, so read the Shift4Shop API documentation and test with Run once. If a scenario still misbehaves, check the connection and the webhook first.
05Should you use Make or n8n for Shift4Shop?
It depends on where the rest of your automations already run. On Make, Shift4Shop comes with 28 modules, instant triggers for orders, customers and products, and Make an API Call for the rest, on a visual editor that shows each bundle after Run once. n8n often has a node for the same app, so compare what each one covers for the Shift4Shop objects you need: orders, carts, customers or products. Neither tool is ranked above the other here; the match with your use case decides.