PrestaShop

Run a self-hosted PrestaShop store from FlowRunner. Agents manage products, categories, stock levels, customers, orders, and addresses, advance order statuses to drive fulfillment, and reach any other webservice resource through a generic escape hatch.

28 actions Basic auth available

PrestaShop website ↗ Platform Documentation ↗ Capability data verified 2026-07-22

The fulfillment provider marks an order shipped in the warehouse system

Agent pulls the matching order with Get Order, reading line items from order_rows

Agent confirms the shipment matches the order's items and totals before touching status

List Order States resolves the store's Shipped state id instead of hardcoding it

Update Order Status advances the order, firing PrestaShop's own shipping email to the customer

Ops channel receives a digest of orders advanced and any that failed matching

Orders that cannot be matched cleanly wait for the store owner's call before any status change

What This Integration Enables

Merchants choose PrestaShop to own their store: self-hosted, their server, their data. The trade is a webservice API with sharp edges. Every PUT is a full replace, bodies are XML, and stock lives in separate stock_available records rather than on the product. FlowRunner's [connector](/concepts/connectors/) absorbs those edges. Update operations fetch the current record, merge your changes, and strip read-only fields before writing back, so an agent updating a price never wipes a description. On top of that foundation, agents run the loops that keep a store honest: syncing products and prices from a PIM or spreadsheet, holding storefront stock to the warehouse's numbers, advancing orders through fulfillment states, and exporting customers and orders to CRM and accounting systems. The 60-plus webservice resources without dedicated operations stay reachable through Call Webservice Resource, so combinations, specific prices, taxes, and carriers are never out of scope.

Without FlowRunner

Stock drift Storefront quantities lag the warehouse until someone re-keys them

Manual status clicks Every shipped order is advanced by hand in the back office

Risky record edits Webservice PUTs replace whole records, so a small edit can clobber fields you never meant to touch

With FlowRunner

Storefront matches warehouse Update Stock Quantity applies feed changes to each product's stock_available record

Status advances drive the store Update Order Status fires PrestaShop's own emails, invoices, and stock movements

Merge-safe writes The connector fetches the current record, merges your changes, and strips read-only fields before every update

Use Case Scenarios

Warehouse Stock Sync

The storefront says five in stock, the warehouse says zero, and a customer just bought one. To end that failure mode, an agent reads current warehouse quantities from [ShipBob](/integrations/shipbob), resolves each SKU to its PrestaShop product with List Products, finds the matching stock row with List Stock Availables, and writes the true quantity with Update Stock Quantity. The storefront stops selling inventory that does not exist, and the merchandiser stops reconciling spreadsheets.

Fulfillment Status That Drives the Store

When [ShipBob](/integrations/shipbob) reports an order shipped, the agent finds the order with List Orders filtered by reference, verifies the line items with Get Order, and advances it with Update Order Status. Because PrestaShop hangs real behavior off state changes, that single call sends the customer's shipping notification and updates invoicing per the store's state configuration. The agent also pushes new customer accounts from List Customers into [Klaviyo](/integrations/klaviyo) so marketing lists grow with the store.

Catalog Cleanup With a Human Gate

Years of imports leave a catalog with duplicate and orphaned products. The agent sweeps List Products for inactive entries, cross-references List Orders to confirm which have never sold, and checks List Carts for any sitting in an active cart. It assembles the evidence into a cleanup proposal and stops. A person decides what actually gets deleted, because in PrestaShop, deletion is forever.

Human-in-Loop Highlight

Delete Product is permanent. PrestaShop removes the product's combinations, images, and stock records along with it, and there is no undo. So the cleanup agent never deletes on its own judgment. It posts to the ops channel: "14 inactive products duplicate an active SKU and have no order history. Delete Product is permanent and takes combinations, images, and stock records with it. Reply with the ids to delete; everything else stays deactivated." The store owner picks. The agent deletes exactly that list, deactivates the rest through Update Product, and logs both sets. The same [human-in-the-loop](/concepts/human-in-the-loop/) gate guards Delete Customer, which permanently severs a customer account from their order history.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

28 actions

Products

List Products Lists catalog products with full field data, filtering by name, reference/SKU, and active status, with pagination and sorting. The starting point for sync and audit flows.
Get Product Retrieves one product by id, including prices, SEO fields, and associations: categories, images, combinations, and the stock_availables ids needed for stock updates.
Create Product Creates a catalog product, writing multilanguage fields for the configured language and auto-generating the URL slug when omitted. Stock is set afterward with Update Stock Quantity.
Update Product Updates a product safely against the webservice's full-replace PUT: the connector fetches the current record, merges your changes, strips read-only fields, and preserves other languages.
Delete Product Permanently deletes a product and its combinations, images, and stock records. Cannot be undone, which is why cleanup flows route this call through a human gate.

Stock

List Stock Availables Lists PrestaShop's per-product, per-combination stock rows. Filter by product id to find the record that Update Stock Quantity needs.
Get Stock Available Retrieves one stock record with its current quantity, owning product and combination, and out-of-stock behavior.
Update Stock Quantity Sets the available quantity on a stock record, merging into the current record before writing so nothing else changes. The core action of every warehouse sync.

Customers

List Customers Lists customer accounts with filtering by email and name. Used to export new shoppers to CRM and marketing platforms.
Get Customer Retrieves one customer with contact details, group membership, and newsletter and opt-in flags.
Create Customer Creates a customer account with a unique email; PrestaShop hashes the password on save.
Update Customer Updates a customer with the same fetch-merge-strip discipline as other updates. The stored password is never altered by this operation.
Delete Customer Permanently deletes a customer account. Orders remain in the store but lose their account link. Routed for sign-off.

Orders

List Orders Lists orders with totals, payment method, and current state, filtered by state, reference, or date range. Line items ride along in each order's associations.
Get Order Retrieves one order with totals, payment details, address ids, and line items in order_rows. No second call needed to see what was bought.
Update Order Status Advances an order by creating an order_history record, the way PrestaShop documents it. Depending on store configuration, this triggers customer emails, invoice generation, or stock movements.
List Order States Lists the store's configured order states with their paid, shipped, and invoice flags. Resolve state ids here instead of hardcoding them.

Addresses and Carts

List Addresses Lists address book records; filter by customer id to get a shopper's delivery and invoice addresses.
Get Address Retrieves one address with owner, country, street, postcode, city, and phone numbers.
List Carts Lists shopping carts including abandoned ones, with line items in cart_rows. Feeds cart-recovery and cleanup analysis.
Get Cart Retrieves one cart with its products, combinations, and quantities.

Store Reference

List Manufacturers Lists brands with name filtering. Manufacturer ids feed product creation and updates.
List Languages Lists installed languages with ids and ISO codes. Sets which language multilanguage fields read and write in.
List Currencies Lists configured currencies with ISO codes, conversion rates, and active status.

Escape Hatch

Call Webservice Resource Reaches the 60-plus webservice resources without dedicated operations: combinations, order_carriers, specific_prices, taxes, zones, and more. Reads return JSON; writes take PrestaShop XML bodies.

Frequently Asked Questions

What can FlowRunner do with PrestaShop?

FlowRunner agents can run List Products, Get Product, and Create Product in PrestaShop, plus 25 more actions.

Does connecting PrestaShop to FlowRunner require OAuth?

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

Can PrestaShop trigger a FlowRunner workflow automatically?

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

Start building with PrestaShop

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us