Resources · Make integration

29 Next Make integrationAutomate 29 Next with Make.

Can Make react to what happens in your 29 Next store? Yes. The 29 Next Make integration gives you 8 triggers and 20 actions across orders, customers, subscriptions and disputes. This guide is for store operators: connect your account, then build a first working scenario.

Try the 29 Next integration on MakeSee the 28 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the 29 Next Make integration do?

The 29 Next Make integration links your 29 Next store to Make, a visual tool where you chain modules into a scenario, meaning the automation you build. Each module is one brick: a trigger that notices something new in your store, or an action that reads or changes an order, a customer or a subscription.

Ship faster after checkout. Start with Watch New Orders and add Create a Fulfillment, so each new order moves toward delivery without someone copying it by hand. Every order that passes from one module to the next is called a bundle.

Follow up on lost sales. Watch New Abandoned Carts hands you each cart a shopper left behind. Pair it with Get a Customer to pull the shopper's record, then send it to your email or chat tool through another app's module.

Keep payment problems in view. Watch New Disputes and Get a Transaction let a support lead see each new dispute with its payment next to it, and Update a Dispute writes back once the case moves.

What Make does not do here: all 8 triggers are scheduled, so Make checks your store on the scenario's schedule instead of hearing from 29 Next the moment something happens. The Make documentation also carries no description for each module, so run a test before relying on one. Plans and limits are laid out on Make pricing, and errors are covered in Make troubleshooting. If you are still choosing a tool, n8n vs Make puts the two side by side.

Connect

How do you connect your 29 Next account to Make?

  1. 01

    Add a 29 Next module

    Open your scenario, add any 29 Next module, and click Create a connection. A connection is your 29 Next account linked to Make once, then reused by every 29 Next module you add later.

  2. 02

    Name the connection

    The Connection name field is optional. Filling it pays off when you run more than one store: a clear name tells you which account each scenario talks to.

  3. 03

    Paste your credentials

    Enter the credentials you copied from your 29 Next account, or follow the instructions Make shows on screen. You need an active 29 Next account and an API key before you start.

First scenario

Your first scenario: fulfill each new 29 Next order

GoalWhen a new order lands in 29 Next, Make creates a fulfillment for it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place your first module. That first module is the trigger: it decides when the rest runs.

  2. 02

    Pick Watch New Orders

    Search for 29 Next, choose Watch New Orders, and click Create a connection to link your store with the credentials from the section above.

  3. 03

    Add Create a Fulfillment

    Click the + on the right of the trigger and add Create a Fulfillment. Fill its fields by mapping values from the order bundle, so each fulfillment matches the order that started it.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can open the order and the fulfillment and check they line up.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Pick your interval, then switch the scenario on.

Triggers

Which 29 Next triggers can start a scenario?

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

29 Next1Watch Events

Watch Events

triggerIn the docs only

Watch Events is the widest door into your store: it starts a scenario from events that 29 Next reports, rather than from one kind of record. Treat it as the entry point when no narrower trigger fits.

How it fires
scheduled, so Make checks the app on the scenario's schedule and picks up what changed since the last check.
When to use it
you need to react to a store activity that none of the other seven triggers covers.
Watch out
the documentation does not describe which events this module returns, so click Run once and read a real bundle before you build anything on it.
29 Next2Watch New Abandoned Carts

Watch New Abandoned Carts

triggerIn the docs only

This trigger gives you one bundle per cart a shopper left without paying, which turns lost checkouts into something your team can act on instead of a number in a report.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a cart reaches your scenario at the next check, not the second it is abandoned.
When to use it
a recovery flow, where each abandoned cart goes to your email tool or to a sales rep.
Watch out
pair it with Get a Cart when you need the full contents, and test with Run once to see what the trigger already carries.
29 Next3Watch New Customers

Watch New Customers

triggerIn the docs only

Every new customer account in your store can open a scenario here, so a welcome sequence or a CRM record starts without anyone exporting a list.

How it fires
scheduled: Make checks the app on the scenario's schedule and passes along each customer created since its previous look.
When to use it
you want a fresh customer copied into a CRM, a newsletter tool or a shared sheet as soon as the scenario next runs.
Watch out
going by its name, it only sees new customers. Test with Run once whether an edited profile starts it before you count on that.
29 Next4Watch New Disputes

Watch New Disputes

triggerIn the docs only

A new payment dispute is the kind of event that costs money when it sits unread. Watch New Disputes brings each one into Make so it lands in front of the right person.

How it fires
scheduled. Make checks the app on the scenario's schedule, so shorten the interval if speed matters, within what your plan allows.
When to use it
alerting a finance or support channel, with the related transaction fetched through Get a Transaction.
Watch out
each dispute consumes operations along every module that follows, which counts on your Make plan, so keep the chain short.
29 Next5Watch New Orders

Watch New Orders

triggerIn the docs only

Watch New Orders is the trigger most store automations begin with: each order placed since the last check arrives in Make as its own bundle, ready for shipping, accounting or a team alert.

How it fires
scheduled: Make checks the app on the scenario's schedule. Orders placed between two checks arrive together on the next run.
When to use it
you care about orders as they are created, not about later edits.
Watch out
if you also need changes to existing orders, look at Watch Orders instead, and avoid running both on the same flow or you may process one order twice.
29 Next6Watch New Subscriptions

Watch New Subscriptions

triggerIn the docs only

For stores selling on a recurring basis, this trigger hands you each new subscription, which is the moment to set up onboarding, access or a first thank-you message.

How it fires
scheduled, meaning Make checks the app on the scenario's schedule rather than waiting for a signal from 29 Next.
When to use it
a subscriber should be added to a members list or a CRM segment right after signing up.
Watch out
it reports new subscriptions only. To act on a subscription later, fetch it with Get a Subscription and change it with Update a Subscription.
29 Next7Watch New Transactions

Watch New Transactions

triggerIn the docs only

Payments are what finance teams reconcile, and this trigger brings every new transaction into Make so it can be copied to a ledger or a sheet without manual export.

How it fires
scheduled. Make checks the app on the scenario's schedule, and all transactions created since the last check come through in one run.
When to use it
feeding accounting or a revenue dashboard that has to match what the store actually charged.
Watch out
a busy store can send many bundles per run, and every module after the trigger runs once for each, so watch your operation count.
29 Next8Watch Orders

Watch Orders

triggerIn the docs only

Watch Orders sits next to Watch New Orders but without the word new in its name, which suggests it follows orders more broadly. The documentation does not spell out the difference.

How it fires
scheduled: Make checks the app on the scenario's schedule and passes on the orders it finds.
When to use it
your scenario needs to see orders beyond the moment they are placed, for example to sync a status to another tool.
Watch out
before you trust it, click Run once on a known order and compare the output with Watch New Orders, so you pick the right one.
Modules

What can 29 Next actions do in a scenario?

29 Next gives you 20 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

29 Next1

Cancel an Order

ActionIn the docs only

Cancel an Order stops an order from your scenario, so a fraud check or an out-of-stock rule can end it without anyone logging into the admin.

When to use it
another module has already flagged the order as one that must not ship.
Watch out
a cancellation is hard to walk back, so test it on a dummy order with Run once before pointing it at real customers.
29 Next2

Create a Customer

ActionIn the docs only

With Create a Customer, a person captured in another tool becomes a customer record in 29 Next, ready for their first order.

When to use it
leads arrive through a form, an event list or a CRM and you want them in the store before they buy.
Watch out
run Get a Customer first if the person might already exist, or you risk ending up with two records for the same buyer.
29 Next3

Create a Fulfillment

ActionIn the docs only

Going by its name, Create a Fulfillment records that an order is on its way, the step that moves a paid order toward delivery in your store.

When to use it
right after Watch New Orders, or once your warehouse tool confirms that a parcel has left.
Watch out
map the order from the previous bundle rather than typing it, otherwise every run fulfills the same order.
29 Next4

Get Customer Orders

ActionIn the docs only

This module pulls the order history of one customer, which gives your scenario context before it decides what to send or whom to alert.

When to use it
a support ticket or an abandoned cart comes in and you want to know whether the person has bought before.
Watch out
a loyal customer may return many orders, and each one flowing into later modules uses operations.
29 Next5

Get Customer Subscriptions

ActionIn the docs only

Get Customer Subscriptions lists what a given customer is subscribed to, so your scenario can treat a subscriber differently from a one-time buyer.

When to use it
a customer writes in and your support tool should show their active plans next to the message.
Watch out
you need the customer first, so place Get a Customer or a customer trigger before this module.
29 Next6

Get a Cart

ActionIn the docs only

Get a Cart fetches one cart from your store, which is how a recovery email can mention what the shopper actually left behind.

When to use it
after Watch New Abandoned Carts, when the trigger's bundle does not carry everything your message needs.
Watch out
it reads one cart at a time, so map the cart from the trigger instead of fixing a single value in the field.
29 Next7

Get a Customer

ActionIn the docs only

This action reads a single customer record, giving later modules a name, contact details or account data to work with.

When to use it
a trigger hands you an order or a dispute and you need the person behind it for a follow-up.
Watch out
Get a Customer changes nothing in 29 Next, so it is safe to test freely; pair it with Update a Customer when an edit is the goal.
29 Next8

Get a Dispute

ActionIn the docs only

Get a Dispute loads one dispute so your team sees the case in full inside Slack, a helpdesk or a spreadsheet, not just a notice that one exists.

When to use it
a dispute needs to be looked up again later in its life, for example when a teammate asks for a status update.
Watch out
right after Watch New Disputes, run the trigger alone first; it may already hold what you need.
29 Next9

Get a Product

ActionIn the docs only

Get a Product reads one product from your catalog, which lets a scenario add product details to a message, a sheet or a listing on another channel.

When to use it
an order line points to a product and you want its full record in the next module.
Watch out
it returns a single product, so for many order lines Make runs it once per bundle and counts each run.
29 Next10

Get a Product Category

ActionIn the docs only

With Get a Product Category you read how the catalog groups a product, useful when reporting or routing depends on the kind of item sold.

When to use it
orders from one category go to a specialist team or a dedicated supplier.
Watch out
the category is separate from the product class; check which one your store actually uses before building routing rules on it.
29 Next11

Get a Product Class

ActionIn the docs only

Get a Product Class fetches the class a product belongs to, another way 29 Next organizes the catalog next to categories.

When to use it
your store sorts items into classes and a scenario must treat each class differently, for shipping or reporting.
Watch out
the Make documentation says nothing about what a class holds, so run it once on a real product and read the bundle before mapping anything.
29 Next12

Get a Stock Record

ActionIn the docs only

Get a Stock Record reads stock information from your store, so a scenario can check inventory before it promises delivery or triggers a restock.

When to use it
a new order comes in and you want to warn purchasing when an item is running low.
Watch out
this is a read. None of the listed modules changes stock, so plan the restock in another tool or with Make an API Call.
29 Next13

Get a Subscription

ActionIn the docs only

This module returns one subscription with its current state, which helps a scenario decide whether to extend access, send a reminder or do nothing.

When to use it
a payment or support event references a subscription and the next step depends on its status.
Watch out
to list every plan for one person, Get Customer Subscriptions is the better fit; this one expects a single subscription.
29 Next14

Get a Transaction

ActionIn the docs only

Get a Transaction reads one payment record, handy when an order or a dispute alone does not tell your finance team what was actually charged.

When to use it
next to Watch New Disputes, so the alert shows the contested payment along with the case.
Watch out
map the transaction from an earlier bundle; a fixed value would return the same payment on every run.
29 Next15

Get an Order

ActionIn the docs only

Get an Order loads a single order, so a scenario started by another app, say a support ticket, can see what the customer bought.

When to use it
the order reference comes from outside 29 Next and you need its full record in Make.
Watch out
after an order trigger this step is often redundant; click Run once and check whether the trigger already gives you enough.
29 Next16

Make an API Call

ActionIn the docs only

Make an API Call is the escape hatch: it reaches any endpoint of the 29 Next API with the connection you already set up, for what the listed modules leave out.

When to use it
you need a record or an action that no listed module offers.
Watch out
you write the request yourself, so keep the 29 Next API reference open and test with Run once on harmless data.
29 Next17

Update a Customer

ActionIn the docs only

Update a Customer writes changes back to a customer record, keeping 29 Next in sync when details are corrected somewhere else.

When to use it
your CRM is where the team edits contact details and the store should follow those edits.
Watch out
the documentation does not describe its fields, so try it on a test customer with Run once and check the record before you point it at real buyers.
29 Next18

Update a Dispute

ActionIn the docs only

This action lets a scenario push progress on a dispute back into 29 Next, so the store record keeps pace with what happens in your helpdesk.

When to use it
your team closes or advances a dispute in another tool and the store needs to reflect it.
Watch out
a dispute touches money; test the update on one case with Run once before letting the scenario run on its own.
29 Next19

Update a Subscription

ActionIn the docs only

Update a Subscription changes an existing subscription from inside a scenario, so plan changes decided elsewhere reach the store without manual edits.

When to use it
a customer asks your support team for a change and the ticket tool should apply it.
Watch out
fetch the subscription with Get a Subscription first and check its state, so you never change the wrong plan.
29 Next20

Update an Order

ActionIn the docs only

Update an Order edits an existing order, which lets information gathered after checkout, from a warehouse or a support tool, land on the order itself.

When to use it
a partner system returns details that belong on the order once it has been placed.
Watch out
pairing it with Watch Orders can loop, since your own edit may count as a change; add a filter so the scenario skips orders it already touched.
Need help

Need help automating 29 Next with Make?

A person reads every message.

FAQ

Questions about the 29 Next Make integration

01Is the 29 Next Make integration free?
Yes, as far as Make goes. 29 Next is a standard app, so its modules are available from the Free plan onward. The Free plan allows 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) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in operations each month. You still need an active 29 Next account, whose pricing is set by 29 Next.
02What do you need to connect 29 Next to Make?
You need an active 29 Next account and an API key. In Make, add any 29 Next module, click Create a connection, give it a name if you like, and enter the credentials copied from your store. For the advanced OAuth2 setup, log in to your store admin through its subdomain, open Settings, then the API section, click Create Application or Add Integration, name the application, enter the callback URI given in the Make documentation, then copy the Client ID and the Client secret back into Make.
03Do 29 Next triggers fire the instant something happens?
No. All 8 triggers for 29 Next are scheduled, and none is instant. Make checks your store on the scenario's schedule, every 15 minutes by default, and processes whatever appeared since the previous check. On a paid plan the interval can drop to 1 minute, while the Free plan stays at 15 minutes minimum. So a new order or dispute reaches your scenario at the next check. If speed matters for one flow, give that scenario the shortest interval your plan allows and keep its chain short.
04What if a 29 Next module you need is missing in Make?
Use Make an API Call. It exists for 29 Next and calls any endpoint of the 29 Next API with the same connection as the other modules, so you do not set up a second login. That covers records or actions that the 20 listed actions and 8 triggers do not reach. You write the request yourself, so keep the 29 Next API reference nearby. Keep in mind that the Make documentation for this app is AI-generated from the vendor's docs and may contain mistakes, so verify key details with 29 Next.
05Should you use Make or n8n for 29 Next?
It depends on how you like to work, not on a winner. On Make, 29 Next comes with 28 native modules and a visual editor where you test each step with Run once. The same app often has an n8n node too, but this page does not confirm one for 29 Next, so check before you decide. Compare the two on the modules each offers for your store, how you prefer to build, and how usage is counted on each side. The n8n vs Make comparison linked above sets those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations