Menu

Mattering Automations Snipcart integration

Connect Snipcart to Mattering Automations: orders and fulfilment status, refunds, customers, products and inventory, discounts, abandoned carts, subscriptions and shipping methods as workflow steps, authenticated with one secret API key that also selects Test or Live mode.

The Mattering Automations Snipcart integration puts your store's REST API on the automation canvas: read and update orders, issue refunds, manage customers, import products and adjust inventory, run discounts, read abandoned carts, monitor and cancel subscriptions, and manage shipping methods, allowed domains and the storefront default domain.

The credential is a Snipcart secret API key. Snipcart authenticates with HTTP Basic where the key is the username and the password is empty, and Mattering builds that header from the key alone, so there is no password field on the Create new credential form for anyone to fill in wrongly. That single detail is worth knowing because it is the usual reason a hand-rolled Snipcart client returns 401 on every endpoint while looking correct.

One decision comes before any of the setup below, and it is the one that makes this integration comfortable to build against. Snipcart keys are created in Test mode or in Live mode, and Snipcart documents the two environments as isolated from each other: a Test key cannot read Live data and a Live key cannot read Test data. Paths, response shapes and behaviour are identical in both, so a Test credential is a full rehearsal environment rather than a reduced one, and Snipcart's documentation states that in the Test environment, using Snipcart is 100% free. Connect a Test credential, build the workflow, then add the Live key when the shape is settled. Setup takes a few minutes, and this guide walks through each step and ends with the full node reference.

Before you start

  • A Snipcart account you can create a secret API key in. Keys are created from the account API keys area of the Snipcart dashboard.
  • A decision about mode. A Test key and a Live key are separate credentials here, because Snipcart isolates the two environments from each other. Start with Test if the workflow includes Snipcart: Create Refund, Snipcart: Cancel Subscription or any of the delete nodes.
  • Somewhere to keep the secret key. It is a full access credential for its mode and is not the public API key your storefront embeds in the page. Do not put it in front end code.
  • A Mattering workspace with access to the Automations app.
  • Worth confirming with Snipcart before you build something your storefront depends on: nothing in Snipcart's API documentation states whether REST API access varies by plan, and Snipcart publishes no rate limit for the REST API. This integration claims no figure for either.

Create a Snipcart secret API key

Mattering authenticates to Snipcart with a secret API key sent as the username of an HTTP Basic header with an empty password, which is the form Snipcart's own documentation and curl example use. The only real choice at this stage is which mode the key belongs to, because that choice decides which data the credential can see.

Sign in to Snipcart and open your account API Keys.
Choose the mode you want this credential to reach, Test or Live, and create a secret key in it. Copy the value.
There is no password to supply anywhere. Snipcart's Basic header carries the key as the username with nothing after the separator, and Mattering assembles it for you, so a blank password field is not something you need to work around.
The secret key is a full access credential for its mode: with a Live key, one call can refund a customer, cancel a subscription or delete a shipping method that shoppers are checking out through. Keep it server side, never in storefront code, and prefer a Test key for anything you are still designing.

Connect Snipcart to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Snipcart from the list.
Click Create new credential, paste the secret API key, and save. Name it for its mode, for example Snipcart Test and Snipcart Live, because the two are indistinguishable once they are in the list.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection. Mattering calls Snipcart's order list endpoint, which is also the vendor's own documented example request, so a success proves host, path, method and the empty password Basic header at once. A 401 means the key is wrong, mistyped, or being used against the other mode's data.
Click Connect. All 43 Snipcart nodes appear in your canvas palette.
Five of those nodes are flagged destructive: Snipcart: Create Refund, Snipcart: Delete Customer, Snipcart: Delete Discount, Snipcart: Cancel Subscription and Snipcart: Delete Shipping Method. On a Live credential the first one moves money to a real gateway with nothing between the node firing and the transfer.

Verify it works

After connecting, open any automation canvas and check the palette: a Snipcart section should list the read and action nodes. Drop Snipcart: List Orders onto the canvas and run a test step. It is the integration's natural probe, because it needs no parameters and it is the request Snipcart's own authentication page demonstrates. Rows come back under data.items, with the paging counters beside them. Look at what you got back as well as whether it worked: if this is a Test credential you should be seeing test orders, and an empty list on a store you know has orders usually means the key is for the other mode.

Now confirm a second shape, because Snipcart uses more than one. Drop Snipcart: List Discounts onto the canvas and run it: that response is a bare array, so its rows read at data rather than data.items. Then open a node with a picker, for example Snipcart: Get Order, and click the Order field: it should list recent orders labelled by invoice number with the shopper email underneath, grouped by status. Everything in this verify path is read-only, so it cannot reach the five destructive nodes and is safe to re-run whenever you rotate the key.

Node reference

43 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 24

Snipcart: Count Subscriptions

snipcart_count_subscriptions

Count subscriptions in the given states. Returns a bare NUMBER, not an object, so the count lands at data itself. The cheapest way to alert on churn: count Stopped or CancellationRequested on a schedule.

Snipcart: Get Abandoned Cart

snipcart_get_abandoned_cart

Read one abandoned cart by its token: line items, quantities, totals, the shopper's email and the cart's current status.

Snipcart: Get Customer

snipcart_get_customer

Read one customer account by its id: email, confirmation status, billing and shipping addresses, and lifetime statistics (order count, total spend, subscription count).

Snipcart: Get Default Domain

snipcart_get_domain

Read the account's default domain and protocol. This is the domain Snipcart's cart is licensed to run on, so it is worth asserting in a deploy check before a release.

Snipcart: Get Discount

snipcart_get_discount

Read one discount by its id, including how many times it has been used (numberOfUsages) and how many uses are still on uncompleted carts (numberOfUsagesUncompleted).

Snipcart: Get Order

snipcart_get_order

Read one order by its token, including line items, applied discounts, taxes, addresses, tracking details and any pending withdrawal requests. This is the full order; the list endpoint's Excerpt format is the light version.

Snipcart: Get Product

snipcart_get_product

Read one product by its Snipcart GUID or your own user-defined id, including stock, the inventory management method (Single, Variant or Disabled), whether out-of-stock purchases are allowed, and per-variant stock levels.

Snipcart: Get Refund

snipcart_get_refund

Read one refund on an order by its id: amount, comment, creation and modification dates, and whether the payment gateway processed it.

Snipcart: Get Shipping Method

snipcart_get_shipping_method

Read one custom shipping method by its id: rates, weight and order-total conditions, country and province restrictions, postal-code regular expression, shipping zone and guaranteed delivery days.

Snipcart: Get Subscription

snipcart_get_subscription

Read one subscription: state, schedule, subscriber, payment status, gateway id and upcoming payments. Set version to V3 when the id you hold is an order token; leave it at V1 for a subscription GUID.

Snipcart: Get User Session

snipcart_get_user_session

Exchange a customer session token for the logged-in shopper's account: email, confirmation status, lifetime order statistics and both addresses, plus the session's expiry. Use it to identify the shopper behind a checkout in progress. The customer object sits at data.customer.

Snipcart: List Abandoned Carts

snipcart_list_abandoned_carts

List carts a shopper started and never completed, with their line items, totals and the shopper's email where known. This is the recovery-campaign feed. Note the pagination differs from the rest of the API: it uses a continuation token, so pass data.continuationToken back on the next call while data.hasMoreResults is true. Rows land at data.items[].

Snipcart: List Allowed Domains

snipcart_list_allowed_domains

List the additional domains and subdomains the cart is permitted to load on, beyond the default domain - staging hosts, preview deploys, tunnels. Returns a bare JSON array, so rows land at data[].

Snipcart: List Customer Orders

snipcart_list_customer_orders

List every order placed by one customer, with totals, payment method, shipping method and addresses. Returns a bare JSON array, so rows land at data[] - unlike List Orders, which is a paged object.

Snipcart: List Customers

snipcart_list_customers

List customer accounts with their lifetime order counts and totals, filtered by confirmation status, exact email, partial billing name or creation date range. Offset paginated: rows land at data.items[]. This is the source node behind every customer picker in this connector.

Snipcart: List Discounts

snipcart_list_discounts

List every discount on the account with its trigger, type, code, rate or amount, usage caps, usage counts, expiry and archived flag. Snipcart returns the WHOLE list as a bare JSON array with no pagination and no filters, so rows land at data[]. This is the source node behind the discount picker.

Snipcart: List Order Digital Goods

snipcart_list_order_digital_goods

List the digital goods attached to an order with their download URLs, how many times each has been downloaded, the download cap, days until expiry, and whether the link is still valid. Returns a bare JSON array, so rows land at data[].

Snipcart: List Order Notifications

snipcart_list_order_notifications

List the notifications and internal comments recorded against one order, newest first: invoices, tracking emails, refund notices, digital-download links and free comments, each with its delivery method and the time it was sent. Offset paginated: rows land at data.items[].

Snipcart: List Order Refunds

snipcart_list_refunds

List every refund already issued against one order, with amounts, comments and whether the payment gateway processed each one. Returns a bare JSON array, so rows land at data[]. Run this before Create Refund to see what has already gone back.

Snipcart: List Orders

snipcart_list_orders

List completed orders, newest first, with filters for status, payment status, date range, purchaser, invoice number, product and billing or shipping address. This is the Gate 1 auth probe: it needs no parameters and is the vendor's own example request. Offset paginated: rows land at data.items[] with data.totalItems giving the full count. This is the source node behind every order picker in this connector.

Snipcart: List Products

snipcart_list_products

List products Snipcart has seen in your carts, each with its price, image and SALES STATISTICS (number of sales and total sales value) computed over the from/to window. This is Snipcart's closest thing to a sales report: the date range bounds the statistics, not the rows. Offset paginated: rows land at data.items[]. This is the source node behind every product picker in this connector.

Snipcart: List Shipping Methods

snipcart_list_shipping_methods

List the account's manually defined shipping methods with their tiered rates, weight and order-total conditions, country and province restrictions, postal-code pattern and guaranteed delivery window. Returns a bare JSON array, so rows land at data[]. Note Snipcart spells the identifier property Id with a capital I on this resource only. This is the source node behind the shipping-method picker.

Snipcart: List Subscription Invoices

snipcart_list_subscription_invoices

List every invoice raised against one subscription, with amounts, invoice numbers, the linked order token and whether each was paid. Returns a bare JSON array, so rows land at data[].

Snipcart: List Subscriptions

snipcart_list_subscriptions

List subscriptions with plan name, subscriber, billing interval, price, lifetime spend, next billing date and the last invoice outcome. Note the path lives under /dashboard/, unlike the count endpoint. Offset paginated: rows land at data.items[], with data.totalDeclinedCount giving the count of failing subscriptions. This is the source node behind the subscription picker.

Action nodes 19

Snipcart: Add Allowed Domains

snipcart_add_allowed_domains

Permit one or more extra domains or subdomains to run the cart. The request body is a root-level JSON ARRAY of {domain, protocol} objects. The natural automation is whitelisting a preview deploy's hostname on every build, then removing it when the branch closes.

Snipcart: Archive Product

snipcart_archive_product

Archive a product. Snipcart's DELETE on a product sets archived to true rather than removing it: sales history and existing orders keep their reference, and the product reappears in List Products when `archived` is set to "true". It is therefore NOT flagged destructive - but be aware that no endpoint in this API un-archives a product, so the reversal is a dashboard action rather than a second node.

Snipcart: Batch Update Order Statuses

snipcart_batch_update_order_statuses

Move many orders to new statuses in one call. The request body is a JSON ARRAY of {id, status} objects, where id is the order token. Use it to mark a day's picking run as Shipped in a single request instead of one PUT per order. Statuses are freely reversible, so this is a reversible write.

Snipcart: Cancel Subscription

snipcart_cancel_subscription

DESTRUCTIVE AND IRREVERSIBLE. Ends a shopper's recurring billing relationship, and nothing in this API restarts it - the customer has to subscribe again through checkout. A V1 subscription is cancelled with the payment gateway immediately; a V3 subscription moves to CancellationRequested and stops at the next billing date. Cancelling refunds nothing already collected; use Create Refund separately for that.

Snipcart: Create Discount

snipcart_create_discount

Create a discount. Which fields are required depends on the trigger (Code needs a code, Total needs totalToReach, Product needs itemId) and on the type (Rate needs rate, FixedAmount needs amount, Shipping needs shippingCost, AlternatePrice needs alternatePrice). A newly created discount can be deleted or archived, so this is a reversible write.

Snipcart: Create Order Notification

snipcart_create_order_notification

Add a notification or internal comment to an order. WITH delivery_method set to Email OR Bcc THIS SENDS A REAL EMAIL TO THE CUSTOMER, and an email cannot be unsent - leave delivery_method blank or None to record a dashboard-only comment. It moves no money, so it is a reversible write, but treat the Email path as one-way.

Snipcart: Create Refund

snipcart_create_refund

DESTRUCTIVE - MOVES REAL MONEY AND CANNOT BE UNDONE. Snipcart's own documentation warns that creating a refund is irreversible and submits the refund to the payment gateway that processed the original order. There is no un-refund endpoint: the funds leave the merchant account on this call, with no second approval step between the node firing and the money moving. Refunds the given amount against an order, optionally refunding taxes proportionally and emailing the customer.

Snipcart: Create Shipping Method

snipcart_create_shipping_method

Create a custom shipping method: a named option with tiered rates that can vary by order weight (IN GRAMS) or order total, restricted to countries and provinces and to addresses matching a postal-code pattern. Snipcart states that creating a shipping method ENABLES SHIPPING on the account if it was disabled, which changes what every shopper sees at checkout.

Snipcart: Delete Customer

snipcart_delete_customer

DESTRUCTIVE AND IRREVERSIBLE. Permanently deletes a customer account, including the login the shopper uses to see their own order history and manage their subscriptions. Snipcart answers 204 with no body and this API offers no way to recreate the record. Use it for genuine erasure requests, not for tidying a list.

Snipcart: Delete Discount

snipcart_delete_discount

DESTRUCTIVE AND IRREVERSIBLE. Permanently removes a discount; there is no restore. Snipcart REFUSES the delete with HTTP 400 for a discount already used on a completed order and tells you to archive instead - which means the deletes that DO succeed are precisely the ones with no history holding them in place. Prefer Update Discount with archived set to "true", which is reversible.

Snipcart: Delete Shipping Method

snipcart_delete_shipping_method

DESTRUCTIVE AND IRREVERSIBLE. Snipcart states the shipping method is permanently removed with no recovery, and this is LIVE CHECKOUT CONFIGURATION: delete the only method covering a region and shoppers there can no longer check out. Answers 204 with no body, or 404 if the id does not exist. Recreating it means re-entering the whole rate table by hand.

Snipcart: Import Products From URL

snipcart_import_products

Import products into Snipcart by pointing it at a URL: an HTML page carrying Snipcart's buy-button markup, or a JSON product document. Snipcart fetches the URL and registers every product it finds. Returns a bare JSON array of the imported products, so rows land at data[]. Imported products can be archived afterwards, so this is a reversible write.

Snipcart: Remove Allowed Domains

snipcart_remove_allowed_domains

Stop permitting one or more domains to run the cart. The request body is a root-level JSON ARRAY of {domain} objects; the protocol is not used for matching. Not flagged destructive because Add Allowed Domains puts a domain straight back - but the cart stops working on that host the moment this runs, so never point it at the live storefront.

Snipcart: Update Customer

snipcart_update_customer

Update a customer's email and default billing or shipping address. Email is required by Snipcart on this call even when only an address is changing, so read the customer first and pass the existing email back if you are not changing it.

Snipcart: Update Default Domain

snipcart_update_domain

Set the account's default domain. HANDLE WITH CARE: this is live checkout configuration, and pointing it at the wrong host stops the cart working on the real storefront until it is set back. It is a reversible write because one further call restores the previous value, so read Get Default Domain first and keep the old value.

Snipcart: Update Discount

snipcart_update_discount

Update an existing discount, or ARCHIVE it by setting archived to "true". Archiving is the right way to retire a discount that has already been used, because Snipcart refuses to delete those - and unlike Delete Discount, it can be undone by setting archived back to "false". Only the fields you fill are sent.

Snipcart: Update Order

snipcart_update_order

Update an order: status, payment status, tracking number and URL, customer email, billing or shipping address, internal notes, custom fields and metadata. Only the fields you fill are sent. Setting status to Shipped with a tracking number is the normal fulfilment write. This does NOT move money - use Create Refund for that.

Snipcart: Update Product Inventory

snipcart_update_product_inventory

Update a product's INVENTORY only: the management method, the stock count, whether out-of-stock purchases are allowed, and per-variant stock. Snipcart accepts no other fields on this call - price, name and images come from your own catalog markup, not from here. Fully reversible by writing the previous numbers back.

Snipcart: Update Shipping Method

snipcart_update_shipping_method

Update a custom shipping method. Snipcart expects the COMPLETE representation on this call, not a patch, so read the method with Get Shipping Method first and send every field back with your changes applied - otherwise omitted fields are cleared. Reversible by writing the previous representation back.

Using the integration

On the automation canvas

Snipcart nodes chain with every other node in the workspace. A schedule can read Snipcart: List Orders filtered by status, write the day's totals into a Mattering database and open a task when an order sits unfulfilled too long. A warehouse file can drive Snipcart: Batch Update Order Statuses in one call instead of a loop. Snipcart: Update Product Inventory can follow a stock change in another system, and Snipcart: List Abandoned Carts can feed a follow up sequence. Most fields that take an identifier are pickers, sourced from the matching list node, so you choose an order by its invoice number and email rather than pasting an opaque token.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter, the assistant built into the platform, can drive the same surface. An assistant handling a customer question can find the order with Snipcart: List Orders, read it with Snipcart: Get Order and check refund history with Snipcart: List Order Refunds. Snipcart publishes an MCP server of its own, and it is worth knowing which job each is for. Snipcart's server is the right tool for an assistant working alongside you in an editor or client. This integration is the operations side: the same store reachable as scheduled and triggered canvas steps with nobody present, chained with every other connector in one workflow, with the credential held once in the workspace rather than in each person's local config, and with the destructive nodes flagged so an approval can sit in front of them.

Test mode is a full rehearsal, not a reduced one

This is the most useful thing about automating Snipcart. Snipcart documents Test and Live as isolated environments, and paths, envelopes and behaviour are the same in both, so a workflow that runs correctly on a Test credential runs the same way on a Live one. Test orders are placed with dummy payment details and never reach a real gateway, which means even Snipcart: Create Refund can be exercised end to end while you are still designing. Connect both credentials, build against Test, and swap the credential on the nodes when you are ready. One crossing point exists and is exposed as a field rather than hidden: the order surfaces accept an include test orders option that lets a Live key also see Test orders.

Orders, statuses and customer notifications

Snipcart: List Orders is the workhorse read, with filters for status, payment status and date range. Snipcart: Update Order writes the fulfilment status, tracking number and shipping details back, and Snipcart: Batch Update Order Statuses does a set at once. Two behaviours are worth designing around. The filter booleans on the order lists are three state rather than two: leaving one blank means no filter, while setting it to false actively selects the orders that do not have that property, so a field you did not mean to touch silently narrows every list. And Snipcart: Create Order Notification with the email delivery method sends a real message to the customer that cannot be unsent, so gate it the way you would gate any outbound mail.

Products, inventory and the archive that is not a delete

Snipcart: Import Products From URL loads or refreshes a catalog from a feed, Snipcart: Update Product Inventory adjusts stock, and Snipcart: List Products and Snipcart: Get Product read what the store believes today. One naming detail prevents a real mistake: Snipcart: Archive Product is the node behind Snipcart's product delete endpoint, because Snipcart archives the product rather than removing it, orders keep their reference, and no API call un-archives it. The reversal is a dashboard action. Two identifier kinds also live side by side here, which the pickers handle for you: the product endpoints take Snipcart's own product id, while the order and cart filters take the merchant's user defined product id, and passing one where the other belongs returns zero rows rather than an error.

Discounts, shipping methods and live checkout configuration

Some of these nodes change what every shopper sees at checkout the moment they run, so they deserve more care than their names suggest. Snipcart: Create Shipping Method enables shipping on the account if it was disabled, and Snipcart: Update Shipping Method is a full replacement rather than a patch, so a workflow that just bumps a rate has to send the whole rate table back or the omitted fields are cleared. Shipping rate weights are in grams, so a table built in kilograms prices every order at the top tier. Snipcart: Update Default Domain defaults the protocol to http when it is not set, which is the wrong value on a real storefront, so read Snipcart: Get Default Domain first and set it explicitly. On discounts, Snipcart refuses to delete a code that has been redeemed and points at archiving instead, so use Snipcart: Update Discount with the archived flag for campaign cleanup and keep Snipcart: Delete Discount for codes created in error.

The five destructive nodes, gated

Snipcart: Create Refund is the one that moves money: Snipcart documents it as irreversible and submitted to the payment gateway that processed the original order, with no un-refund endpoint anywhere. Snipcart: Cancel Subscription ends the shopper's billing relationship, refunds nothing already collected, and nothing in this API restarts it. Snipcart: Delete Customer removes the account a shopper signs into for order history. Snipcart: Delete Discount is permanent, and Snipcart: Delete Shipping Method removes live checkout configuration with no recovery, so deleting the only method covering a region stops shoppers there checking out and recreating it means re-entering the whole rate table. The pattern for all five is the same: rehearse on a Test credential, keep them off any agent-facing surface, and put a condition or an approval task between the trigger and the node. Two nodes deserve the same caution without carrying the flag: Snipcart: Remove Allowed Domains breaks the cart on that host immediately, though Snipcart: Add Allowed Domains puts it straight back, and Snipcart: Create Order Notification can send an email that cannot be recalled.

Troubleshooting

Test Connection fails with a 401 error
Snipcart returns 401 with the same body for two different causes, and the second one is the common one here. Either the secret key is wrong or mistyped, or the key is valid but belongs to the other mode: a Test key returns 401 against Live data and a Live key returns 401 against Test data. Check for leading or trailing whitespace from the copy, then confirm in the Snipcart dashboard which mode the key was created in. Note that you never need to supply a password: Snipcart's Basic header carries the key as the username with nothing after it, and Mattering builds that itself, so a missing password field is not the problem.
The order list is empty on a store that definitely has orders
Usually the credential is pointed at the other environment. Snipcart isolates Test and Live, so a Test key legitimately sees only test orders and reports an empty list rather than an error when there are none. Confirm which mode the key was created in, and if you need a Live credential to also surface test orders, use the include test orders option on the order nodes. The other cause is a filter that narrowed the list without looking like it did: the boolean filters here are three state, so setting one to false selects only the orders lacking that property rather than disabling the filter. Clear the filter fields you did not mean to set and run it again.
A subscription node returns not found for an id that exists
Snipcart supports two subscription generations and the identifier is a different kind of value in each, so the wrong combination returns a not found rather than an explanation of the mismatch. This matters most on Snipcart: Cancel Subscription, where nothing happened and cancelled the wrong thing look identical from the caller's side. Fill the identifier from the picker on Snipcart: List Subscriptions rather than pasting a value from elsewhere, and check the version field on the node against the value you are passing. A second cause of a bare 404 here is the path root: the count and the list of subscriptions live under different roots in Snipcart's API, which the nodes already handle, so a mismatch shows up as an id problem rather than a URL one.
Deleting a discount fails with a validation error
Snipcart blocks deletion of a discount that has already been redeemed and asks you to archive it instead. The consequence for a cleanup automation is worth stating plainly: the delete will succeed on the codes nobody used and fail on exactly the codes that mattered. Switch the workflow to Snipcart: Update Discount with the archived flag, which works regardless of usage history and keeps the reporting intact, and keep Snipcart: Delete Discount for codes created by mistake and never redeemed.
A product still appears after it was deleted
That is the documented behaviour rather than a fault. Snipcart's product delete archives the product instead of removing it, which is why the node is named Snipcart: Archive Product. Existing orders keep their reference to it, which is the point. No API call un-archives a product, so if it was archived by mistake, the reversal is a dashboard action in Snipcart rather than another node.
Updating a customer address fails
Snipcart's customer update requires the email address on every call, even when the only thing changing is an address. A workflow that patches one field therefore has to read the customer first with Snipcart: Get Customer and pass the existing email back alongside the change. The same shape catches people on shipping methods for a different reason: Snipcart: Update Shipping Method replaces the whole method rather than patching it, so any field you omit is cleared and a rate bump has to carry the entire rate table.
Shipping rates come out far higher than expected
Check the units on the rate table. Snipcart expresses shipping rate weights in grams, so a table authored in kilograms puts every order into the heaviest tier while looking correct at a glance. Read the current method back with Snipcart: Get Shipping Method, compare the tier boundaries against the weights your products actually carry, and remember that Snipcart: Update Shipping Method is a full replacement, so send the corrected table in full.
Adding a shipping method changed what shoppers see at checkout
Creating a shipping method enables shipping on the account if it was previously disabled, so a single add-a-rate call can change every shopper's checkout. It is expected behaviour rather than a bug, but it is not obvious from the node name. Treat Snipcart: Create Shipping Method as live storefront configuration: rehearse it on a Test credential first, and gate it behind an approval on Live. The same caution applies to Snipcart: Update Default Domain, which defaults the protocol to http when it is left unset, so read the current value with Snipcart: Get Default Domain and set the protocol explicitly.
A workflow needs to react the moment an order is placed
This connector polls rather than listens, and there are no trigger nodes for Snipcart, because Snipcart configures webhooks in its dashboard and documents no REST endpoints for managing them. For fulfilment, reconciliation and reporting, a schedule plus Snipcart: List Orders filtered by date or status is normally enough. If you need immediate reaction, configure a webhook in the Snipcart dashboard pointed at a Mattering webhook trigger, and use these nodes for every step after that first hop.

Snipcart is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products