---
title: "Wix Integration"
description: "Connect AI agents to your Wix site. Agents manage contacts and labels, read and write CMS data collections, run your store's products, orders, fulfillments, and coupons, draft blog posts, and look up site members and properties."
url: https://flowrunner.ai/integrations/wix
date_modified: 2026-08-04T10:04:16-07:00
---

# Wix

[Web Platform](https://flowrunner.ai/integrations/category/developer-infrastructure)

Connect AI agents to your Wix site. Agents manage contacts and labels, read and write CMS data collections, run your store's products, orders, fulfillments, and coupons, draft blog posts, and look up site members and properties.

[Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 34 actions · API key · available

[Wix website](https://wix.com/) · [Platform Documentation](https://dev.wix.com/docs/rest) · Capability data verified 2026-07-22

1.  A payment settles in the storefront and the order needs to move
2.  Search Orders pulls orders in APPROVED status that have no fulfillment yet
3.  Get Order retrieves line items, shipping details, and payment status for each
4.  Agent verifies the carrier and tracking number returned by the warehouse system
5.  An operations lead reviews any order where the shipped items do not match the order lines before fulfillment is recorded
6.  Create Order Fulfillment writes the fulfillment with tracking, which notifies the customer
7.  Update Contact stamps the buyer's CRM record with the fulfillment date
8.  A summary of fulfilled and held orders posts to the team channel

## What This Integration Enables

A Wix site is usually treated as the front door of the business and nothing more: a place where orders, form fills, and members arrive, and where someone eventually goes to copy them out. This connector treats the site as what it actually is, a database with a storefront attached. FlowRunner agents work the full surface: CRM contacts with labels, CMS data collections through the Wix Data v2 query language, the Stores catalog, eCommerce orders and fulfillments, draft blog posts, coupons, and site members.

-   Upsert leads into Wix CRM and segment them with labels as part of intake flows
-   Keep CMS collections synced from external systems with rerunnable Save Data Item calls
-   Cross-list and maintain the Stores catalog, pricing, and visibility
-   Match approved orders to warehouse confirmations and record fulfillments with tracking
-   Draft blog posts from plain text so publishing starts from a review queue, not a blank page
-   Issue and retire coupon codes under explicit human control

### Without FlowRunner

**The site is an island**: Orders, contacts, and content live inside the Wix dashboard while the rest of the business runs in other systems

**Fulfillment is a tab-switching job**: Someone reads the warehouse export, finds each order, and types tracking numbers in by hand

**The CMS goes stale**: Data collections that power the site's pages only change when a person remembers to edit them

### With FlowRunner

**The site is an endpoint**: Agents read and write contacts, orders, products, and CMS items as part of larger flows across your stack

**Fulfillment runs on approval**: Agents match warehouse confirmations to approved orders and a person clears only the mismatches

**Content syncs on schedule**: Save Data Item upserts keep collections aligned with the systems of record, rerunnable without duplicates

## Use Case Scenarios

### Inquiry to labeled lead without a copy-paste step

A sales inquiry lands in [Gmail](https://flowrunner.ai/integrations/gmail-service). The agent extracts the sender's name, email, and company, calls Query Contacts to check whether the person already exists, and either calls Create Contact or Update Contact accordingly. Label Contact then applies the "Leads" label so the segment the sales team already filters on picks the record up. The follow-up task lands in the rep's queue with the original email attached. Nobody exports a form submission again.

### Warehouse to customer, with a person on the mismatches

The 3PL emails shipment confirmations every afternoon. The agent parses each confirmation, calls Search Orders filtered to APPROVED and paid, and matches on order number. Clean matches get Create Order Fulfillment with the carrier and tracking number; Wix generates the tracking link and the customer gets notified. When a confirmation lists three items and Get Order shows four, the order goes to a human queue in [Slack](https://flowrunner.ai/integrations/slack) instead of being marked fulfilled. The operations lead resolves the short shipment, and the agent records the fulfillment only after that call.

### One catalog, two storefronts

The team sells on [Shopify](https://flowrunner.ai/integrations/shopify) and runs a Wix site for a second brand. When a product changes in the primary catalog, the agent pulls the details and calls Query Products on the Wix side to find the counterpart. Existing products get Update Product with the new price and visibility; genuinely new items get Create Product with name, type, price, and SKU. A weekly sweep lists products present in Wix but retired upstream and posts the list for review, because Delete Product is permanent and a person decides what leaves the catalog.

## Human-in-Loop Highlight

Create Coupon and Delete Coupon are where an agent can quietly move real money. A coupon created with the wrong discount type applies storewide by default, and once the code circulates, every checkout that redeems it is margin gone that cannot be recalled. So in FlowRunner, promotion flows draft the coupon spec, name, code, discount, validity window, scope, and post it for sign-off: "SUMMER20, 20 percent off, storewide, valid through August 31. Approve?" The marketing owner approves, the agent calls Create Coupon, and at the window's end the agent proposes Delete Coupon rather than executing it, because killing a code customers are mid-checkout with is also a judgment call. The agent does the drafting and the bookkeeping; the person owns the spend.

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

34 actions

### Contacts

8

-   **Query Contacts** Queries CRM contacts using the Contacts v4 query language, with raw filter objects, sorting, and offset paging. The lookup behind matching and segmentation.
-   **Get Contact** Retrieves a single contact by ID, including the revision needed for updates, primary email and phone, labels, and extended fields.
-   **Create Contact** Creates a new CRM contact with name, email, phone, label keys, and optional advanced info such as addresses, company, or extended fields.
-   **Update Contact** Updates fields on an existing contact. Handles Wix's revision-based optimistic locking automatically when the revision is omitted.
-   **Delete Contact** Permanently deletes a contact by ID. Contacts who are also site members or contributors cannot be deleted this way.
-   **List Contact Labels** Lists the system and custom labels defined on the site, with the keys used when labeling contacts.
-   **Label Contact** Adds one or more existing labels to a contact. The step that places a lead into the segment the team already works.
-   **Unlabel Contact** Removes labels from a contact without deleting the labels from the site.

### CMS Data

7

-   **Query Data Items** Queries items in a CMS data collection with the Wix Data v2 query language: raw filters, sorting, paging, and an optional total count.
-   **Get Data Item** Retrieves a single collection item by ID with its full data payload and system fields.
-   **Insert Data Item** Inserts a new item into a collection. Wix generates the ID unless one is provided.
-   **Update Data Item** Fully replaces an existing item's data, so every field to keep must be included.
-   **Save Data Item** Upserts by \_id: creates when the item does not exist, replaces when it does. The default write for rerunnable imports and sync jobs.
-   **Remove Data Item** Permanently removes an item from a collection and returns it as it existed before deletion.
-   **List Data Collections** Lists the custom and app collections on the site with field definitions and capabilities, so flows adapt to the site's actual schema.

### Store Products

5

-   **Query Products** Queries the Stores catalog with filters, sorting, paging, and optional full variant data.
-   **Get Product** Retrieves a product by ID, including pricing, stock, media, options, and additional info sections.
-   **Create Product** Creates a catalog product with name, type, and price, plus optional SKU, visibility, and advanced properties like variants and ribbons.
-   **Update Product** Updates only the fields provided, used for price changes, visibility toggles, and enrichment.
-   **Delete Product** Permanently deletes a product from the catalog. Retirement flows route this through review.

### Orders

3

-   **Search Orders** Searches eCommerce orders across Wix sales channels with raw filters on status or payment status, sorting, and cursor paging.
-   **Get Order** Retrieves an order with line items, buyer info, price summary, payment and fulfillment statuses, and shipping details.
-   **Create Order Fulfillment** Records a fulfillment on an approved order, with auto-generated tracking links for known carriers. The write that tells the customer their order shipped.

### Blog

4

-   **List Blog Posts** Lists published posts with paging, sorting, and an optional featured-only filter.
-   **Get Blog Post** Retrieves a published post by ID with title, excerpt, slug, hero image, and category and tag IDs.
-   **Create Draft Blog Post** Creates a draft post from plain text or Ricos rich content, with optional immediate publish. Drafting by default keeps a person on the publish button.
-   **List Blog Categories** Lists blog categories with IDs, labels, and post counts, used when creating or filtering posts.

### Coupons

4

-   **Query Coupons** Queries coupons by specification fields such as code, with paging, returning specs and usage data.
-   **Create Coupon** Creates a coupon with a discount type, code, and optional scope limiting it to specific products or collections.
-   **Get Coupon** Retrieves a coupon's name, code, discount, validity window, scope, and usage statistics.
-   **Delete Coupon** Permanently deletes a coupon so its code can no longer be redeemed. Gated in every FlowRunner promotion flow.

### Members

2

-   **List Members** Lists site members with a choice of fieldset depth. Member IDs also identify blog post authors.
-   **Get Member** Retrieves a single member by ID at the chosen fieldset depth.

### Site

1

-   **Get Site Properties** Reads the site's display name, language, locale, currency, time zone, and business contact details. The connection check and settings source for site-aware flows.

## Frequently Asked Questions

### What can FlowRunner do with Wix?

FlowRunner agents can run Query Contacts, Get Contact, and Create Contact in Wix, plus 31 more actions.

### Does connecting Wix to FlowRunner require OAuth?

No. Wix connects to FlowRunner with an API key, no OAuth flow required.

### Can Wix trigger a FlowRunner workflow automatically?

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

**Work at Wix?** This integration exposes Wix to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current.

---
Markdown version of https://flowrunner.ai/integrations/wix. Site index: https://flowrunner.ai/llms.txt
