CS-Cart

CS-Cart and CS-Cart Multi-Vendor are self-hosted store and marketplace platforms. Agents keep the catalog in step with a PIM or ERP, watch and update orders and shipments, manage customers and vendors, recover abandoned carts, and adjust taxes, shipping and payment settings.

135 actions Basic auth available

CS-Cart website Platform Documentation Capability data verified 2026-08-26

A schedule fires and List Recently Changed Orders runs with the last run time as the window

Agent reads each changed order with its lines, totals, and customer

Each order is matched against the warehouse dispatch file for the same day

Create Shipment attaches the carrier and tracking number to the order

Set Order Status moves the order forward with Notify Customer switched on

The fulfillment channel gets the order total and the customer name

Orders the dispatch file cannot explain go to a person, who decides whether to hold or ship

What This Integration Enables

CS-Cart is for merchants who decided to own the store rather than rent it. It is self-hosted, which means there is no central API host to point at: the base URL is your own server, the credential is an administrator's key, and the permissions that key inherits belong to that administrator's user group rather than to the key itself. Two perfectly valid connections can therefore see different halves of the same store. That is a real property of self-hosted commerce, not a defect, and it is worth knowing before an agent runs against production.

What the connector covers is the whole commerce surface a merchant actually automates: products with their categories, features, options, option combinations, exceptions, and variations; orders with their shipments and statuses; abandoned carts; customers and user groups; vendors and common products on CS-Cart Multi-Vendor; storefronts, taxes, shipping methods, and payment methods; content pages, reviews, and call requests. FlowRunner's connectors are built and verified against each vendor's official API, and the sharp edges of this one are handled in the operations rather than left in the flow: writes carry the content type CS-Cart demands, Set Order Status exists as its own operation because the customer notification is opt-in, and the connector falls back between the two URL generations a real CS-Cart install may serve.

Without FlowRunner

Nothing announces a change CS-Cart has no webhooks in core, so a status change is noticed when somebody opens the admin panel

Silent notification gaps An order is marked shipped through the API and the customer is never emailed, because the flags default to off

Catalog edits by hand Products, features, options, and variation groups are maintained one screen at a time

With FlowRunner

Changes are polled deliberately A scheduled window over recently changed orders becomes the trigger the platform never shipped

The customer is told on purpose The notification flags are set explicitly on every status move, so shipped means the shopper heard

The catalog follows its source Products and their structure are written from the PIM or spreadsheet that already owns them

Use Case Scenarios

The order loop that closes with the shopper

There is no event to subscribe to, so the agent polls. List Recently Changed Orders runs on a schedule with the previous run time carried as flow state, which is the change-detection primitive CS-Cart actually gives you. For each order that reached a shipped state in the warehouse, the agent calls Create Shipment with the carrier and tracking number, then Set Order Status with Notify Customer switched on, because a status change made through the API sends nothing to the shopper unless it is asked to. The order total and customer name go to the fulfillment channel in Slack. The failure this replaces is not a crash. It is a shipped order the customer was never told about.
Abandoned carts, reached without a bulk export

List Carts filtered to shoppers who left contact details gives the agent a recovery queue. For each cart it reads the line items and total, creates or updates the contact in Brevo, and sends a transactional message built around what was actually left behind rather than a generic reminder. Carts belonging to customers who have since ordered are dropped from the queue before anything is sent, which is the check that keeps a recovery sequence from emailing somebody who already paid.
Review moderation with a decision at the end

The agent pulls the disapproved queue with List Reviews And Comments, reads each one, and sorts it: obvious spam, genuine criticism, and everything ambiguous. Genuine reviews are published through Update Review Or Comment. Spam is logged to a sheet in Google Sheets with the reason. The ambiguous ones go to a person, because a store's review section is customer speech and a classifier's confidence score is a poor reason to delete any of it.

Human-in-Loop Highlight

Create Sign In Link is the most interesting operation in the CS-Cart API and the one that needs a person standing next to it. It takes a registered email address and mints a one-time sign-in link with an ekey. Anyone holding that link is that user until it is consumed. It is not an impersonation session with an audit banner and a timer, it is a log-in, and support workflows want it precisely because it is so effective: the agent can hand a shopper a link that drops them straight into their own account without a password reset. So the agent prepares everything and stops before minting. It posts to the support owner: "Ticket 4417 asks for account access recovery for orders@northfield.example. That address matches one customer account with 6 orders. Issuing a sign-in link gives whoever opens it full access to that account. Issue it, and to which verified channel?" The person confirms the identity and the destination, and only then is the link minted, sent, and never written to a log. Every other gate on this page could be argued about. This one is a credential, and credentials do not get issued by a rule.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

135 actions

Products

List Products Lists products with filters for price, quantity, category, and free-text search. Set Page Size explicitly, because CS-Cart's default is a per-store setting rather than a fixed number.
Get Product Retrieves one product with its stored field values. The read to run after any write that matters, because CS-Cart never echoes a record back.
Create Product Creates a product. Fields CS-Cart does not recognize are ignored silently, so named parameters are the safe way to write.
Update Product Updates a product's fields.
Delete Product Permanently deletes a product.
List Category Products Lists the products filed under one category.
List Vendor Products Lists the products belonging to one vendor on a Multi-Vendor store.
List Storefront Products Lists the products available on one storefront.

Orders

List Orders Lists orders with filters. The general-purpose order read.
List Recently Changed Orders Lists orders changed inside a time window. This is the change-detection primitive that stands in for the webhook CS-Cart does not have, so hold the last run time as flow state.
Get Order Retrieves one order with its lines, totals, and customer.
Create Order Creates an order. A new order always lands in the open status whatever you ask for, so a specific state needs a second call.
Update Order Updates an order, including the three customer, department, and vendor notification flags.
Set Order Status Moves an order to a new status and controls whether the customer, the order department, and the vendor are told. It exists as its own operation because none of those notifications happen by default.
Delete Order Deletes an order.

Shipments

List Shipments Lists shipments across orders.
Get Shipment Retrieves one shipment with its carrier and tracking number.
Create Shipment Creates a shipment against an order, which is where a carrier tracking number from a warehouse system lands.
Update Shipment Updates a shipment's carrier or tracking detail.
Delete Shipment Deletes a shipment.

Order Statuses

List Order Statuses Lists the store's order status letters. Also the connection check, because it exists on every install and its output is the vocabulary the rest of the order automation depends on.
Get Order Status Retrieves one status with its settings.
Create Order Status Creates a custom order status.
Update Order Status Updates a status, including its notification and inventory behavior.
Delete Order Status Deletes a custom order status.

Carts

List Carts Lists abandoned carts, filterable to shoppers who left contact details. The starting point of a recovery workflow.
Get Cart Retrieves one cart with its line items and total.
Delete Cart Deletes an abandoned cart.

Customers and Access

List Users Lists customer and administrator accounts.
Get User Retrieves one account.
Create User Creates a customer or administrator account.
Update User Updates an account's details.
Delete User Deletes an account.
List User Memberships Lists the groups an account belongs to.
Set User Membership Adds an account to a user group, which is what wholesale pricing and access rules key on.
Remove User From Group Removes an account from a group.
List User Groups Lists the store's user groups. Guests and Registered are reserved and do not appear here.
Get User Group Retrieves one user group.
Create User Group Creates a user group.
Update User Group Updates a user group.
Delete User Group Deletes a user group.
Create Sign In Link Mints a one-time passwordless sign-in link for a registered email address, optionally landing on a chosen page. Anyone holding the link is that user until it is used, which is why this page's human gate exists for it.

Product Structure

List Product Features Lists the store's product features, which are the structured attributes products are filtered and compared on.
Get Product Feature Retrieves one feature with its type.
List Product Feature Values Lists the values defined for a feature.
Create Product Feature Creates a feature.
Update Product Feature Updates a feature.
Delete Product Feature Deletes a feature.
List Product Options Lists the options buyers choose at purchase, such as size or finish.
Get Product Option Retrieves one option with its variants.
Create Product Option Creates an option on a product.
Update Product Option Updates an option.
Delete Product Option Deletes an option.
List Option Combinations Lists the stock-keeping combinations generated from a product's options.
Get Option Combination Retrieves one combination with its own stock and code.
Create Option Combination Creates a combination.
Update Option Combination Updates a combination's stock or code.
Delete Option Combination Deletes a combination. The parent product travels as a query parameter rather than a path segment, which is CS-Cart's own shape and its permission check.
List Option Exceptions Lists the option pairings a product forbids.
Get Option Exception Retrieves one exception.
Create Option Exception Creates an exception that blocks an impossible combination from being ordered.
Update Option Exception Updates an exception.
Delete Option Exception Deletes an exception, again with the product as a query parameter.

Product Variations

List Product Variations Lists the variations of a product on stores running the Product Variations add-on.
Get Product Variation Retrieves one variation.
Create Product Variation Creates a variation.
Update Product Variation Updates a variation's own price, stock, or code.
Delete Product Variation Deletes a variation.
Detach Product Variation Removes a variation from its group and leaves it as a standalone product.
Set Default Product Variation Chooses which variation the storefront shows first.
Generate Product Variations Generates the full set of variations from a product's features in one call.
List Variation Groups Lists variation groups, addressable by numeric id or symbol code.
Get Variation Group Retrieves one variation group.
Create Variation Group Creates a variation group from a set of products.
Update Variation Group Updates a group's membership or settings.
Delete Variation Group Disbands a variation group. The products in it are not deleted, they become regular products, which leaves orphans in the catalog if a flow expected otherwise.

Marketplace

List Vendors Lists the vendors on a Multi-Vendor store.
Get Vendor Retrieves one vendor with its status and store details.
Create Vendor Onboards a vendor.
Update Vendor Updates a vendor, including approving or suspending it.
Delete Vendor Deletes a vendor.
List Common Products Lists the shared product records several vendors can offer against.
Get Common Product Retrieves one common product.
Create Common Product Creates a common product for the marketplace catalog.
Update Common Product Updates a common product.
Delete Common Product Deletes a common product.
List Common Product Offers Lists the vendor offers attached to common products.
Get Common Product Offer Retrieves one vendor offer with its price and stock.
Create Common Product Offer Creates a vendor offer against a common product.
Update Common Product Offer Updates an offer's price or stock.
Delete Common Product Offer Removes a vendor offer.

Storefronts and Settings

List Storefronts Lists the storefronts configured on the install.
Get Storefront Retrieves one storefront's configuration.
Create Storefront Creates a storefront, optionally cloning an existing one's data, which turns spinning up a new store into a single call.
Update Storefront Updates a storefront.
Delete Storefront Deletes a storefront.
List Settings Lists the store's settings.
Get Setting Retrieves one setting's current value.
Update Setting Changes a setting. CS-Cart publishes no create or delete here, so settings can be changed but never added or removed through the API.

Store Configuration

List Taxes Lists the store's tax rules.
Get Tax Retrieves one tax rule.
Create Tax Creates a tax rule.
Update Tax Updates a tax rule.
Delete Tax Deletes a tax rule.
List Shipping Methods Lists shipping methods and their rate configuration.
Get Shipping Method Retrieves one shipping method.
Create Shipping Method Creates a shipping method.
Update Shipping Method Updates a shipping method, including what shoppers are charged for postage.
Delete Shipping Method Deletes a shipping method.
List Payment Methods Lists the payment methods offered at checkout.
Get Payment Method Retrieves one payment method.
Create Payment Method Creates a payment method.
Update Payment Method Updates a payment method.
Delete Payment Method Deletes a payment method.

Content

List Pages Lists the store's content pages.
Get Page Retrieves one page with its content.
Create Page Creates a content page.
Update Page Updates a page's content or status.
Delete Page Deletes a page.

Reviews and Comments

List Reviews And Comments Lists reviews and comments across the store, filterable to the disapproved queue that moderation starts from.
List Product Reviews And Comments Lists the reviews and comments on one product.
Get Review Or Comment Retrieves one review or comment with its author and rating.
Create Review Or Comment Creates a review or comment, used when migrating reviews in from another platform.
Update Review Or Comment Updates a review, which is how a held review is approved.
Delete Review Or Comment Deletes a review or comment permanently.

Call Requests

List Call Requests Lists callback requests left by shoppers.
Get Call Request Retrieves one callback request with its phone number and context.
Create Call Request Creates a callback request, used when routing one in from another channel.
Update Call Request Updates a callback request, such as marking it handled.
Delete Call Request Deletes a callback request.

Frequently Asked Questions

What can FlowRunner do with CS-Cart?

FlowRunner agents can run List Products, Get Product, and Create Product in CS-Cart, plus 132 more actions.

Does connecting CS-Cart to FlowRunner require OAuth?

No. CS-Cart connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can CS-Cart trigger a FlowRunner workflow automatically?

CS-Cart doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with CS-Cart

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us