Resources · Make integration

AmeriCommerce Make integrationAutomate AmeriCommerce with Make.

Your store already knows every order, customer and stock level, so why copy them by hand? The AmeriCommerce Make integration gives you 33 modules, 8 of them triggers. This guide connects your account, builds a first scenario and explains each module in plain words.

Try the AmeriCommerce integration on MakeSee the 33 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the AmeriCommerce Make integration automate?

The AmeriCommerce Make integration links your store to Make, a visual tool where you chain modules into a scenario. A scenario is the automation you build; a module is one brick of it, such as a trigger, an action or a search. Your store data then moves to other apps without copy and paste.

Orders that reach the rest of your tools. Watch Valid Orders skips declined and cancelled orders, so only real sales flow on. Pair it with Get a Customer and you hold both the order and the buyer, ready for a CRM or a shared sheet.

Stock that follows another system. Set Inventory Count writes an exact quantity, while Remove an Inventory subtracts one. When a supplier file or a warehouse tool holds the truth, these modules copy it into AmeriCommerce.

A customer base kept tidy. Watch Customers and Watch Customer Updated notice new and edited accounts; Update a Customer and List Customers let you correct or review them in bulk.

What Make does not do here: all 8 triggers are scheduled, so nothing fires the second an order lands. When a module is missing, Make an API Call reaches the rest of the AmeriCommerce API. The same store may also exist as an n8n node; the n8n vs Make comparison sets the two side by side. To learn the editor itself, see the Make training, and check Make pricing before you scale up.

Connect

How do you connect AmeriCommerce to Make?

  1. 01

    Prepare your AmeriCommerce access

    You need an active AmeriCommerce account and an API key. For the OAuth2 route, open Tools > Apps and Addons > Apps and Integrations, create a new OAuth2 app, paste https://www.integromat.com/oauth/cb/americommerce3 as callback URI and save.

  2. 02

    Add a module and open the connection

    In your Make scenario, add any AmeriCommerce module and click Create a connection. A connection is your store account linked to Make once, then reused by every AmeriCommerce module. Naming it in Connection name is optional.

  3. 03

    Paste your credentials

    Copy the Client ID and the Client secret from the app details screen in AmeriCommerce, paste them into Make, or follow the on-screen instructions. Once saved, Make can read your store.

First scenario

Your first scenario: valid orders with their customer attached

GoalWhen a valid order is placed in AmeriCommerce, Make fetches the matching customer so both reach your next tool together.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. This first module decides when everything starts.

  2. 02

    Pick Watch Valid Orders

    Search AmeriCommerce, choose Watch Valid Orders and click Create a connection if your store is not linked yet. Declined and cancelled orders stay out.

  3. 03

    Add Get a Customer

    Click the + on the right of the trigger and add Get a Customer. Each order travels as a bundle, one item passed between modules; map the value that identifies the buyer.

  4. 04

    Test with Run once

    Place or wait for a valid test order, then click Run once. Open the bubbles above each module to read the bundles they received and confirm the right customer came back.

  5. 05

    Schedule and switch on

    On the first module, set the schedule (every 15 minutes by default) and switch the scenario on. Add the app that should receive the data with one more +.

Triggers

Which AmeriCommerce triggers start a scenario?

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

AmeriCommerce1Watch Customers

Watch Customers

Scheduled trigger

In Make“Triggers when a new customer has been created.”

Every account created in your store becomes a fresh bundle in Make, so a new buyer can land in your mailing tool or CRM without an export. It only reacts to creations, not to later edits.

How it fires
scheduled. Make checks AmeriCommerce on the scenario's schedule and picks up the customers added since the last check.
When to use it
welcoming each new customer or tagging them in another app right after sign-up.
Watch out
on the Free plan the shortest gap between checks is 15 minutes, so a welcome message leaves with that delay at most.
AmeriCommerce2Watch Customer Updated

Watch Customer Updated

Scheduled trigger

In Make“Triggers when a customer has been updated.”

Edits to an existing customer record reach Make, which lets a changed address or name propagate to the tools that keep a copy. Think of it as the sync half of customer automation.

How it fires
scheduled; Make polls your store at the interval set on the first module and collects the records changed in between.
When to use it
a support desk or accounting tool that must show the same details as the store.
Watch out
if the same scenario runs Update a Customer, its own edit counts as an update and can start the scenario again.
AmeriCommerce3Watch Orders

Watch Orders

Scheduled trigger

In Make“Triggers when a new order has been created.”

Each new order, whatever its outcome, shows up as a bundle, which gives you a complete log of checkout activity including declined and cancelled attempts.

How it fires
scheduled. On each run of the scenario, Make asks AmeriCommerce for orders created since its previous look.
When to use it
tracking every attempt in a sheet, or alerting the team when a payment fails and a sale needs a follow-up call.
Watch out
for fulfilment or revenue reporting, Watch Valid Orders is safer, because this trigger also passes orders that were declined or cancelled.
AmeriCommerce4Watch Order Updated

Watch Order Updated

Scheduled trigger

In Make“Triggers when an order has been updated.”

Changes on orders you already have reach Make, so a status move or an edited line can ripple to shipping, accounting or customer messages without anyone checking the admin.

How it fires
scheduled; Make queries the store at the rhythm of the scenario and returns the orders modified since the last query.
When to use it
telling a buyer their order changed, or keeping a fulfilment board aligned with AmeriCommerce.
Watch out
each run of Make costs operations even when it only confirms a small edit, so filter the updates that matter before the next module.
AmeriCommerce5Watch Products

Watch Products

Scheduled trigger

In Make“Triggers when a new product has been created.”

New items in your catalog appear in Make as bundles, so a product you publish can be announced, copied to a marketplace sheet or passed to the team that writes descriptions.

How it fires
scheduled. Make looks at AmeriCommerce whenever the scenario runs and returns products created after the previous pass.
When to use it
merchandising or marketing teams who hear about new products too late.
Watch out
it ignores edits to existing products; changes in price or stock need Watch Product Updated instead.
AmeriCommerce6Watch Product Updated

Watch Product Updated

Scheduled trigger

In Make“Triggers when a product has been updated.”

Edited products flow into Make, which keeps catalogs elsewhere in step with the store once a price, a description or a setting changes in AmeriCommerce.

How it fires
scheduled; Make checks your catalog on the scenario's clock and hands over products modified since its last visit.
When to use it
mirroring the catalog in a spreadsheet, a feed tool or a second sales channel.
Watch out
a scenario that ends with Update a Product on the same item triggers a new update, which can create an endless cycle. Filter those edits out.
AmeriCommerce7Watch Quotes

Watch Quotes

Scheduled trigger

In Make“Triggers when a new quote has been created.”

Quote requests become bundles in Make, so a sales rep hears about a prospect while the interest is still warm instead of discovering it in the admin later.

How it fires
scheduled. Make polls AmeriCommerce at the scenario interval and returns each quote created since the last run.
When to use it
B2B stores that handle quotes, when a new one should create a task, a deal or a chat message.
Watch out
a quote is not an order; if the buyer later converts, catch that sale with Watch Valid Orders rather than this trigger.
AmeriCommerce8Watch Valid Orders

Watch Valid Orders

Scheduled trigger

In Make“Triggers when a new valid order (not declined or cancelled) has been created.”

Only orders that were not declined or cancelled reach Make, which gives you a clean stream of real sales to feed fulfilment, invoicing or reporting.

How it fires
scheduled; on each run Make asks the store for new valid orders since the previous check.
When to use it
any scenario where acting on a failed payment would cost you, like shipping, sending a thank-you or adding revenue to a dashboard.
Watch out
an order cancelled after it was picked up stays in your downstream tools; handle that case with Watch Order Updated.
Modules

What can AmeriCommerce do inside a scenario?

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

AmeriCommerce1

Create a Customer

Action

In Make“Creates a new customer.”

A new customer account appears in AmeriCommerce from data that started elsewhere, such as a form, an event list or a CRM contact.

When to use it
a phone or trade-show sale where the buyer should exist in the store before the order is keyed in.
Watch out
run List Customers first if the person may already exist, or you end up with duplicates.
AmeriCommerce2

Create an Inventory

Action

In Make“Creates an inventory.”

Stock information gets its first record in AmeriCommerce straight from your scenario, handy when a new item comes from a supplier file rather than the admin.

When to use it
right after Create a Product, so the item has inventory the moment it goes live.
Watch out
for an item that already has stock, Set Inventory Count is the right module, not this one.
AmeriCommerce3

Create an Order

Action

In Make“Creates a new order.”

Orders placed outside the storefront, by email, phone or another sales channel, land in AmeriCommerce so all revenue sits in one admin.

When to use it
a marketplace or a sales form whose orders should be fulfilled through the store.
Watch out
make sure the buyer exists first; pair it with Get a Customer or Create a Customer earlier in the scenario.
AmeriCommerce4

Create a Payment

Action

In Make“Creates a payment.”

Money received through another channel gets recorded against the store, so AmeriCommerce reflects what was actually paid.

When to use it
a bank transfer or an invoice settled in an accounting tool that should be logged on the matching order.
Watch out
a scenario that retries after an error can record the same payment twice; check with List Payments before creating.
AmeriCommerce5

Create a Product

Action

In Make“Creates a new product.”

New catalog entries are born from a spreadsheet row, a supplier feed or a PIM, sparing you the manual form in the admin for each item.

When to use it
a seasonal range prepared in a sheet by the buying team and pushed to the store in one pass.
Watch out
each row is its own bundle and costs an operation, which Make counts on your plan.
AmeriCommerce6

Delete a Customer

Action

In Make“Deletes a customer.”

Customer records you no longer want in the store get removed by the scenario, useful for honoring an erasure request logged in another tool.

When to use it
a privacy form or a support ticket that asks to delete an account.
Watch out
a deletion cannot be undone from Make. Put a filter before this module and test with Run once on a dummy account.
AmeriCommerce7

Delete an Order

Action

In Make“Deletes an order.”

Test or duplicate orders disappear from AmeriCommerce without anyone opening the admin, which keeps reports free of noise.

When to use it
cleaning out orders placed during a checkout test, identified by a filter you trust.
Watch out
nothing brings a deleted order back. When a real sale only needs a change, Update an Order edits it instead of erasing it.
AmeriCommerce8

Delete a Payment

Action

In Make“Deletes a payment.”

A payment entry recorded by mistake gets removed, so an order no longer shows money it never received.

When to use it
fixing a duplicate created by an earlier scenario run, after List Payments has spotted it.
Watch out
removal is final. If the amount is only wrong, Update a Payment corrects it without removing the payment.
AmeriCommerce9

Delete a Product

Action

In Make“Deletes a product.”

Discontinued items leave the catalog automatically once another system marks them as dead, keeping the store in line with your range.

When to use it
a supplier sheet where a status column says an item is gone for good.
Watch out
deletion is permanent. For a seasonal pause, Update a Product is safer than wiping the item.
AmeriCommerce10

Get a Customer

Action

In Make“Retrieves a customer.”

Full details of one customer come back as a bundle, filling the gap when a trigger only hands you an order or a quote.

When to use it
after Watch Valid Orders, to send the buyer's details to a CRM or a thank-you email.
Watch out
it returns one known customer; to find people by criteria, List Customers is the module to pick.
AmeriCommerce11

Get an Inventory

Action

In Make“Retrieves an inventory.”

Current stock information for one item lands in your scenario, so the next module can decide based on what is really on the shelf.

When to use it
before promoting a product, to check it can still be shipped.
Watch out
the value reflects the moment of the run; a scheduled scenario reads stock at its own rhythm, not continuously.
AmeriCommerce12

Get an Order

Action

In Make“Retrieves an order.”

One order is loaded in full, which helps when a scenario starts from something else, like a support ticket or a payment notice, and needs the order behind it.

When to use it
a helpdesk message quoting an order that should be answered with its details.
Watch out
it targets a single order you can identify; to browse several, use List Orders.
AmeriCommerce13

Get a Payment

Action

In Make“Retrieves a payment.”

A single payment record comes into the scenario, so you can confirm what was paid before shipping, refunding or notifying the accountant.

When to use it
reconciling one order flagged by finance against what AmeriCommerce actually holds.
Watch out
it reads one payment only; List Payments is the choice when you need several payments at once.
AmeriCommerce14

Get a Product

Action

In Make“Retrieves a product.”

One product's current record arrives in Make, giving later modules the product exactly as the catalog stores it right now.

When to use it
enriching an order line or a marketing post with the product as it stands today.
Watch out
for a whole catalog export, List Products fits better, since this module handles one item per run.
AmeriCommerce15

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Any endpoint of the AmeriCommerce API becomes reachable with the connection you already set up, which covers whatever the listed modules leave out.

When to use it
a store object or operation that no listed module handles.
Watch out
you write the request yourself, so keep the AmeriCommerce API documentation open and test with Run once first.
AmeriCommerce16

Remove an Inventory

Action

In Make“Removes the specified quantity from the quantity in stock.”

Stock goes down by the quantity you pass, which mirrors items sold or lost outside the store without recalculating the total yourself.

When to use it
a sale on another channel or a damaged batch reported by the warehouse.
Watch out
a scenario that runs twice on the same bundle subtracts twice. When you know the true total, Set Inventory Count is safer.
AmeriCommerce17

Set Inventory Count

Action

In Make“Sets the quantity in stock to the specified quantity.”

Your stock lands on an exact number you choose, overwriting whatever AmeriCommerce held, which suits syncing from a system that owns the true count.

When to use it
a warehouse tool or supplier sheet that publishes current quantities.
Watch out
it replaces the stored value outright, so any stock change made in AmeriCommerce since your source counted gets overwritten.
AmeriCommerce18

Update a Customer

Action

In Make“Updates a customer.”

Changes made in another tool, such as a CRM or a support desk, flow back into the customer record in the store.

When to use it
a new address confirmed by support that should apply to the next delivery.
Watch out
combined with Watch Customer Updated in one scenario, each edit can wake the trigger again; add a filter to break the cycle.
AmeriCommerce19

Update an Order

Action

In Make“Updates an order.”

An existing order changes from your scenario, so progress recorded in shipping or finance tools shows up in AmeriCommerce too.

When to use it
a carrier or warehouse confirming a step that the store should display.
Watch out
if Watch Order Updated feeds the same scenario, this edit counts as a new update and can trigger it again.
AmeriCommerce20

Update a Payment

Action

In Make“Updates a payment.”

A payment already on file gets corrected, keeping the store in line with the bank or the accounting tool without deleting anything.

When to use it
a partial capture or a settlement that finance confirms after the order was placed.
Watch out
you need to target the right payment; Get a Payment or List Payments usually comes just before.
AmeriCommerce21

Update a Product

Action

In Make“Updates a product.”

Product details change in bulk from a sheet or a supplier feed, which saves editing items one by one in the admin.

When to use it
a price list revision prepared by the buying team for part of the range.
Watch out
with Watch Product Updated in the same flow, every edit reappears as a new update; filter it out to avoid a cycle.
AmeriCommerce22

List Customers

Search

In Make“Retrieves a list of customers.”

A set of customers comes back from the store, each as its own bundle, ready to be exported, deduplicated or enriched in another tool.

When to use it
checking whether an email already exists before Create a Customer, or building a list for a campaign.
Watch out
it can return zero, one or many bundles, and each following module runs once per bundle, costing an operation each.
AmeriCommerce23

List Orders

Search

In Make“Retrieves a list of orders.”

Several orders arrive at once, which lets you catch up on past sales that a trigger never saw or rebuild a report from scratch.

When to use it
filling a new dashboard with existing orders before Watch Orders takes over.
Watch out
a long list multiplies operations downstream; place a filter or an aggregator right after it.
AmeriCommerce24

List Payments

Search

In Make“Retrieves a list of payments.”

Payment records come back in a batch, giving finance a way to compare what AmeriCommerce logged against the bank or an accounting tool.

When to use it
hunting duplicates before Delete a Payment, or preparing a reconciliation sheet.
Watch out
it can return zero, one or several bundles, so plan for a run where nothing comes back.
AmeriCommerce25

List Products

Search

In Make“Retrieves a list of products.”

Your catalog, or part of it, flows into the scenario one product per bundle, ready for a feed, a price audit or a backup sheet.

When to use it
a marketplace listing or comparison sheet that needs the current range in one pass.
Watch out
a big catalog means many bundles; everything after this module repeats for each product and counts operations.
Need help

Need help automating AmeriCommerce with Make?

A person reads every message.

FAQ

Questions about AmeriCommerce and Make

01Is the AmeriCommerce Make integration free?
Yes, AmeriCommerce is a standard app, so it works on the Make Free plan. That 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, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one execution of one module on one bundle. Your AmeriCommerce subscription is separate and is not covered by Make.
02What do you need to connect AmeriCommerce to Make?
An active AmeriCommerce account and an API key. To use OAuth2, go to Tools, then Apps and Addons, then Apps and Integrations in AmeriCommerce, create a new OAuth2 app, enter the callback URI Make expects, save, then copy the Client ID and Client secret shown on the app details screen. In Make, add any AmeriCommerce module, click Create a connection, optionally name it, and paste those credentials. The connection is then shared by every AmeriCommerce module in your scenarios.
03Do AmeriCommerce triggers in Make react in real time?
No. All 8 AmeriCommerce triggers are scheduled, and none is instant. Make checks the store at the interval set on the first module of the scenario, every 15 minutes by default. On the Free plan 15 minutes is also the shortest gap; paid plans can go down to 1 minute. Each check collects what happened since the previous one, with that delay. For flows where a few minutes matter, pick a paid plan and a short interval.
04What if an AmeriCommerce module is missing in Make?
Use Make an API Call. It reaches any endpoint of the AmeriCommerce API with the same connection as the other modules, so an object or operation absent from the 33 listed modules is still within reach. You write the request yourself, which means reading the AmeriCommerce API documentation and testing with Run once. The Make documentation for this app is AI-generated from the AmeriCommerce docs and may contain mistakes, so check important details with AmeriCommerce directly.
05Make or n8n for AmeriCommerce?
It depends on where the rest of your automations live. On Make, AmeriCommerce comes with 33 ready modules covering customers, orders, products, inventory and payments, plus Make an API Call for the rest. Many apps also have an n8n node, so check whether AmeriCommerce has one and what it covers before you choose. Compare the modules each tool offers against the exact steps of your process, and keep your store automations in the tool your team already uses to build scenarios.
Same platform

Other docs you might need on this stack.

Browse all integrations