Resources · Make integration

SamCart Make integrationAutomate SamCart with Make.

Every SamCart sale, refund or charge can start an automation without a line of code. The SamCart Make integration gives you 10 modules: 6 triggers and 4 actions. This page shows how to link your account, then walks you through a first scenario built on new orders.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SamCart Make integration do for you?

The SamCart Make integration lets Make notice what happens in your store (a new order, a refund, a changed subscription) and pass it to the rest of your tools. You build a scenario, which is the automation itself: a chain of modules, each one a single brick such as a trigger or an action.

Refunds your support team hears about. Watch Refunds picks up each new refund, and the next module in the scenario can post it wherever your support team works, so nobody learns about it from an angry email.

A clean customer record for every sale. Start with Watch Orders, add Get a Customer to pull the buyer's full record, then send it to your CRM or a spreadsheet. Each order travels as one bundle, meaning one item passed from module to module.

Subscription changes that reach the right person. Watch Subscriptions fires when a subscription status changes, which is the moment a retention email or an account manager should step in.

Know the limits before you plan. All 6 SamCart triggers are scheduled: Make checks SamCart on the scenario's schedule rather than being called the second something happens. The three Get modules only retrieve data, judging by their descriptions, so nothing in the list creates or edits a record in SamCart. For any other endpoint of the SamCart API, Make an API Call uses the same connection.

New to the editor? The Make training covers the basics, and Make troubleshooting helps when a run fails. Weighing tools? Read n8n vs Make.

Connect

How do you connect SamCart to Make?

  1. 01

    Add a SamCart module

    Open your scenario in Make, add any SamCart module, then click Create a connection. A connection is your SamCart account linked to Make once and reused by every SamCart module afterwards.

  2. 02

    Paste your API key

    Give the connection a recognizable label in Connection name if you like; that field is optional. Then paste the key you received from the SamCart Support Team into the API Key field.

  3. 03

    Save and confirm

    Click Save. If Make asks you to authenticate your account and confirm the access, accept it. The connection then appears in the dropdown of every SamCart module you add.

First scenario

Your first scenario with SamCart and Make

GoalWhen a new order lands in SamCart, Make fetches the full customer record behind it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module.

  2. 02

    Add Watch Orders

    Search for SamCart, pick Watch Orders and choose your connection, or click Create a connection if this is your first SamCart module.

  3. 03

    Chain Get a Customer

    Click the + to the right of Watch Orders, choose Get a Customer and map the customer value from the order bundle into its field.

  4. 04

    Test with Run once

    Click Run once, place a test order if needed, then open the bubbles above each module to read the bundles they received and check the customer came through.

  5. 05

    Schedule and switch on

    Open the clock on Watch Orders to set the schedule (every 15 minutes by default), then turn the scenario on. Each check now picks up the orders that arrived since the last one.

Triggers

SamCart triggers in Make

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

SamCart1Watch Subscriptions

Watch Subscriptions

Scheduled trigger

In MakeTriggers when a status of subscription is changed.

Hear about it whenever a subscription changes status in SamCart, so the people who care about renewals and cancellations stop finding out late. Each changed subscription reaches the next module as its own bundle.

How it fires
scheduled. Make checks SamCart on the scenario's schedule, not the instant the status changes.
When to use it
you sell recurring plans and want a status change to trigger a retention email or a task for an account manager.
Watch out
the directory describes it as firing on a status change, so if the first purchase matters too, run Watch Orders alongside it.
SamCart2Watch Orders

Watch Orders

Scheduled trigger

In MakeTriggers when a new order is created.

Turn every new SamCart order into the starting point of a scenario, from a thank-you sequence to a line in your sales sheet. It is the natural first trigger for a new SamCart scenario.

How it fires
scheduled. Make checks SamCart for new orders on the scenario's schedule.
When to use it
a sale should update another tool, whether that is your CRM, your accounting app or a team chat.
Watch out
on the Free plan the shortest interval between two checks is 15 minutes, so plan follow-ups that can wait that long; paid plans go down to 1 minute.
SamCart3Watch Refunds

Watch Refunds

Scheduled trigger

In MakeTriggers when a new refund is created.

Catch each new refund recorded in SamCart and send it where it matters, so finance and support see the same event. The trigger only looks at refunds, which keeps the scenario quiet the rest of the time.

How it fires
scheduled. Make looks for new refunds in SamCart on the scenario's schedule.
When to use it
you want a refund to reach your bookkeeping tool or open a support follow-up without anyone copying it by hand.
Watch out
each refund counts as a bundle, and every module it passes through uses an operation on your plan.
SamCart4Watch Products

Watch Products

Scheduled trigger

In MakeTriggers when a new product is created.

Keep your other tools aware of your catalog: this trigger picks up each product newly created in SamCart and hands it to the next module. Useful when the product list lives in several places and drifts apart.

How it fires
scheduled. Make checks SamCart for new products on the scenario's schedule.
When to use it
a launch means adding the offer to a spreadsheet, a sales page tracker or an internal announcement channel.
Watch out
it is described as firing on newly created products, so test with Run once before counting on it for changes to an existing product.
SamCart5Watch Customers

Watch Customers

Scheduled trigger

In MakeTriggers when a new customer is created.

Get every new SamCart customer into your mailing list or CRM without exporting anything, since the trigger passes each fresh customer record along at Make's next check.

How it fires
scheduled. Make checks SamCart for newly created customers on the scenario's schedule.
When to use it
you care about the person more than the order, for example to tag a buyer in your email tool the first time they appear.
Watch out
it is described as firing on newly created customers; if you need every purchase, including repeat ones, Watch Orders is the safer start.
SamCart6Watch Charges

Watch Charges

Scheduled trigger

In MakeTriggers when a new charge is created.

Follow the money itself: this trigger returns each new charge created in SamCart, which gives your finance tools a feed of payments rather than orders.

How it fires
scheduled. Make checks SamCart for new charges on the scenario's schedule.
When to use it
your accountant or revenue dashboard needs to see each new payment without an export.
Watch out
this watches charges in general; to inspect one that failed, look at Get a Failed Charge in the modules below.
Modules

What the SamCart modules can do

SamCart gives you 4 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Searches

3 modules
SamCart1

Get a Charge

Action

In MakeRetrieve a specific charge by ID.

Pull the full details of one SamCart charge by its ID, so a later module can work with the exact payment rather than a summary.

When to use it
an earlier step, another app or a support ticket gives you a charge ID and you need the rest of the record before acting.
Watch out
it needs that ID up front; without one, start from Watch Charges.
SamCart2

Get a Customer

Action

In MakeRetrieve a specific customer.

Fetch one specific SamCart customer and bring the whole record into your scenario, ready to be mapped into a CRM or an email tool.

When to use it
right after Watch Orders or Watch Charges, when those bundles point to a buyer but you want their full profile.
Watch out
it returns one customer; to catch new ones as they come, Watch Customers is the better start.
SamCart3

Get a Failed Charge

Action

In MakeRetrieve a specific failed charge.

Look up one failed charge in SamCart so your scenario can react to a payment that did not go through, instead of discovering it later in a report.

When to use it
you run a dunning or follow-up flow and need the details of the failure before contacting the customer.
Watch out
no trigger watches failed charges directly, so the reference has to come from another step.

Other

1 module
SamCart4

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Reach any endpoint of the SamCart API from your scenario, reusing the connection you already created, when none of the ready-made modules covers what you need.

When to use it
you need something the other 9 modules do not offer, such as an endpoint listed in the SamCart API documentation.
Watch out
you describe the request yourself, so keep the SamCart API documentation open while you set it up.
Need help

Need help automating SamCart with Make?

A person reads every message.

FAQ

SamCart and Make: common questions

01Is the SamCart Make integration free?
Yes, SamCart is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a shortest gap of 15 minutes between two scheduled runs, 5 minutes of execution per run, 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 count usage in credits, meaning operations, per month. You still need your own SamCart account.
02What does it take to connect SamCart to Make?
Two things: a Make account and a SamCart API key. According to the Make documentation, the key is provided by the SamCart Support Team, so request it first; without it, you cannot finish the connection. Then add a SamCart module, click Create a connection, paste the key into the API Key field and click Save. If Make asks you to authenticate and confirm access, accept. The same connection then serves all 10 SamCart modules.
03Does the SamCart trigger in Make react in real time?
No. All 6 SamCart triggers are scheduled, and none is instant. Make checks SamCart at the interval set on the first module of the scenario: every 15 minutes by default, 15 minutes at the shortest on the Free plan and down to 1 minute on paid plans. When the check runs, every order, refund or charge created since the previous check comes through as its own bundle; it simply reaches you with that delay.
04What if the SamCart module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the SamCart API with the connection you already have, which covers what the other 9 modules do not; the three Get modules only retrieve data. Keep the SamCart API documentation next to you to know which endpoints exist. The Make documentation gives no numeric limit for this app, so there is no documented quota to plan around.
05Make or n8n for SamCart automations?
It depends on where your other automations already run. In Make, SamCart comes with 10 ready modules, including 6 scheduled triggers, and works from the Free plan. The same app often has an n8n node as well, so if your team already builds in n8n, check what that node offers before splitting work across two tools. The better choice is usually the platform your team already maintains, not a general ranking between the two.