Menu
Mattering Automations connector

A Wix MCP for scheduled, unattended Wix work, not just chat

Connect one Wix account API key and 55 nodes land on the canvas: query sites, create and label contacts, open CRM tasks, manage Stores products and stock, work orders and fulfillments, and read and write the Wix CMS. Runs on a schedule with nobody watching, chains with every other connector in the same workflow, and holds the key once in your workspace rather than in one person's client config.

55 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Wix MCP connector does

The Wix connector for Mattering Automations is 55 nodes over the Wix REST APIs, chosen as a coherent spine rather than a tour of the whole platform: 3 sites and platform nodes, 16 CRM nodes for contacts, labels, extended fields, members and tasks, 12 Stores catalog nodes for products, inventory and categories, 11 eCommerce nodes for orders, fulfillments, transactions and abandoned checkouts, and 13 CMS nodes over Wix Data. That splits 25 read nodes and 30 action nodes, with 9 flagged destructive. One account API key authenticates all of it.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can look up a buyer with Wix: Query Contacts, open a follow-up with Wix: Create CRM Task, and write the outcome into a collection with Wix: Insert Data Item, without anyone opening the Wix dashboard.

Wix ships an MCP server of its own, and it is worth naming plainly rather than working around. Wix hosts it at mcp.wix.com, it can also be run through the npx package the vendor publishes, and it is a built-in connector inside Claude that needs no configuration at all. Its tools are aimed at building on Wix: documentation search, code generation, site management, and a generic call-any-Wix-API tool. If what you want is a chat assistant that can answer Wix questions and poke the API while you watch, use the vendor server. This connector is aimed somewhere else. It is 55 typed nodes on a workflow canvas that run on a schedule or from another app's event with nobody present, chain with every other connector in one workflow, keep the credential in a shared workspace store instead of an individual developer's config, and carry destructive flags so a delete can be gated behind a condition or an approval step.

The auth model has one detail that trips almost everyone, so the connector handles it rather than hiding it. Wix does not use a Bearer token: the API key goes into the Authorization header raw, with no scheme in front of it, and every call must carry exactly one target header, either the account id or the site id, never both. One key also reaches many sites, so the site is not part of the credential. The account id is stored once with the key, and each site-level node carries a site field that is a picker fed by Wix: Query Sites, so you choose a site by name and the connector sends the right header for that call.

The scope is deliberate and the page says what is missing rather than implying full coverage. Bookings, Events, Restaurants, Blog, Pricing Plans, Loyalty and Inbox are not built. Neither are checkout, carts, draft orders or refunds through Wix eCommerce, because money movement is not a first-wave canvas node. Product coverage targets Catalog V3, so a site still on the older Wix Stores catalog cannot use the product nodes at all, which is why Wix: Get Catalog Version exists as a one-call check instead of an assumption.

One connection, three surfaces

  • Visual automations. Drag Wix nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Wix node, ready to drop on the canvas

55 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 25

Wix: Get Catalog Version

Report whether this site's store runs Wix Stores Catalog V1 or Catalog V3. Run this FIRST in any store workflow. The two catalogs are not backwards compatible, each site is on exactly one of them, the choice is permanent once a site moves to V3, and every product node in this connector targets V3 - so on a V1 site those nodes will not work and this node is how a workflow finds that out cheaply instead of by failing halfway through. Requires the Wix Stores app to be installed on the site (Wix's own 'Before you begin' for Products V3), and an API key whose permissions cover Wix Stores.

Wix: Get Contact

Fetch one contact by id with its full profile: name, emails, phones, addresses, company, job title, birthdate, locale, labels and extended field values, plus marketing subscription and email deliverability status. If the id belongs to a contact that was merged away, Wix returns the TARGET contact and sets responseType to MERGED, so check that field rather than assuming the id you sent is the id you got back.

Wix: Get Data Collection

Fetch one CMS collection's schema: every field's key, display name and type, the collection's permissions, its display field, its max page size, and its capabilities (which data operations it supports and its index limits). Read this before writing items, because Wix Data rejects keys the collection does not define. Also returns the revision that Update Data Collection requires.

Wix: Get Data Item

Fetch one row from a CMS collection by its item id. Note the split Wix uses here and nowhere else: the ITEM id travels in the URL path while the COLLECTION id travels as a query parameter, and both are required. The returned data object carries the system fields _id, _createdDate, _updatedDate and _ownerId alongside the collection's own fields.

Wix: Get Inventory Item

Fetch one inventory record: the quantity held for a single product variant at a single location, its availability status, whether quantity is tracked at all, and its preorder settings. Returns the current revision, which Wix: Update Inventory Item requires. Requires the Wix Stores app to be installed on the site (Wix's own 'Before you begin' for Products V3), and an API key whose permissions cover Wix Stores.

Wix: Get Member

Fetch one site member by member id, including login email and verification state, approval status, privacy and activity status, profile, and the CONTACT id the member is linked to. The member id is NOT the contact id; passing a contact id here returns 404. Ask for fieldsets FULL to see the login email and real status values. Requires the Wix Members Area app to be installed on the site (Wix's own 'Before you begin' for the Members API).

Wix: Get Order

Fetch one order in full: buyer and billing details, line items, price summary with subtotal, shipping, tax and total, payment and fulfillment status, tags, and the activity log. Fails with 404 ORDER_NOT_FOUND for an unknown id. Requires an eCommerce-enabled app on the site: Wix documents that the eCommerce platform cannot be installed on its own and arrives as a dependency of Wix Stores, Wix Bookings, Wix Restaurants Orders or a comparable business-solution app.

Wix: Get Product

Fetch one product with its full detail INCLUDING variants, which the list methods deliberately omit. Returns the product's name, slug, visibility, type, price range, inventory availability and each variant's id, SKU, choices and price. The variant ids returned here are what the inventory nodes key on. Also returns the current revision, which Wix: Update Product requires. Requires the Wix Stores app to be installed on the site (Wix's own 'Before you begin' for Products V3), and an API key whose permissions cover Wix Stores.

Wix: Get Site Data Usage

Read the site's CMS storage and item quotas and how much of each is used, split by live and sandbox environment and broken down per collection. This is the honest way to handle Wix Data limits: the ceilings are real and writes HARD-FAIL once they are reached, but Wix never publishes what sets them, so read them per site here instead of assuming a number. Note this endpoint is on /wix-data/v1, not v2.

Wix: List Contact Labels

List the site's contact labels with their keys, display names and type. This is the lookup that turns a human label name into the label KEY that Label Contact and the info.labelKeys filter need. Three label types exist: SYSTEM (Wix built-ins such as contacts.customers), USER_DEFINED (custom.*) and WIX_APP_DEFINED. Note that Wix gates even this read behind the MANAGE-LABELS permission (there is no read-only label permission), so a narrowly scoped key will 403 here.

Wix: List Data Collections

List the site's CMS collections with each collection's identifier, display name, type, field definitions and permissions. This is where a data workflow starts: the identifier returned here is what every data-item node needs, and the field list tells you what keys an item's data object may carry. Ordered by identifier ascending by default. Includes Wix app collections (Blog/Posts, Stores/Products and so on) alongside native ones.

Wix: List Extended Fields

List the contact custom fields defined on the site, with each field's key, display name and data type (TEXT, NUMBER, DATE or URL). Run this before writing info.extendedFields on a contact: the keys have to exist already and the data type is fixed at creation. Two field types come back: USER_DEFINED custom fields, and SYSTEM fields Wix maintains itself such as ecom.totalSpentAmount, which are read-only. Wix caps custom fields at 100 per site.

Wix: List Items In Category

List which catalog items sit in a category, returning each item's catalog id and the id of the app that owns it (for Wix Stores products that is the Wix Stores app id). This returns REFERENCES, not product detail - feed the returned catalogItemId values into Wix: Get Product for the actual products. Up to 100 items per page. Requires the Wix Stores app to be installed on the site (Wix's own 'Before you begin' for Products V3), and an API key whose permissions cover Wix Stores.

Wix: List Order Fulfillments

List every fulfillment recorded against one order, with its line items and quantities, tracking number, shipping provider, tracking link, status and whether it is marked complete. Note the path is under /fulfillments/, not under the order. There is no pagination on this call: the whole list comes back inline. Requires an eCommerce-enabled app on the site: Wix documents that the eCommerce platform cannot be installed on its own and arrives as a dependency of Wix Stores, Wix Bookings, Wix Restaurants Orders or a comparable business-solution app.

Wix: List Order Transactions

List the payments and refunds recorded against one order: amounts, payment status, gateway transaction id, card brand and last four digits, whether a refund is still possible, and each refund's reason and items. Note the path segment is /payments/, not /transactions/. An order with nothing recorded returns an empty transactions record rather than an error, and there is no pagination (payments cap at 100, refunds at 300). Requires an eCommerce-enabled app on the site: Wix documents that the eCommerce platform cannot be installed on its own and arrives as a dependency of Wix Stores, Wix Bookings, Wix Restaurants Orders or a comparable business-solution app.

Wix: Query CRM Tasks

List the site's CRM tasks with title, description, due date, status and the contact each one is attached to. Filter-object only (there is no free-text search here). Default sort is createdDate descending. Note this family uses CURSOR paging while contacts and members use offset paging. Cursor pagination: pass the cursor from the previous response to read the next page, and send filter and sort on the FIRST call only, because Wix ignores them on a cursor request.

Wix: Query Contacts

Find contacts by filter, sort and page, returning up to 1,000 per request with names, emails, phones, addresses, company, labels and custom (extended) field values. Offset pagination: pagingMetadata carries count, offset and total. Defaults are createdDate ascending, limit 50, offset 0. The `search` field is Wix's plain-text search and is documented as an EXACT match over first name, last name, email and phone only, so use `filter` with $startsWith for partial matching. Wix publishes no numeric rate limit; a 429 means throttled, and the documented remedy is to wait about a minute and retry.

Wix: Query Data Items

Read rows out of a CMS collection with filtering, sorting, paging and field projection. This is the workhorse read for anything stored in Wix's own database. Filter values for date fields are written as {"$date": "2026-05-05T00:00:00.000Z"}. Set returnTotalCount to get a total back; it costs performance, so it is off by default. Reads are eventually consistent unless consistentRead is set. Use includeReferencedItems to inline related rows instead of making a second call.

Wix: Query Inventory Items

List stock levels. One inventory item is one product variant at one location, so a two-variant product selling from two locations has four inventory items. Returns quantity, in-stock and availability status, preorder settings, and the variant's name and SKU. Unlike Query Products this method is generously filterable - by productId, variantId, locationId, quantity, inStock, availabilityStatus, product.name, product.variantSku and more - which makes it the practical way to find low stock. Up to 1,000 per page. Requires the Wix Stores app to be installed on the site (Wix's own 'Before you begin' for Products V3), and an API key whose permissions cover Wix Stores.

Wix: Query Members

Find site members by free-text search, filter, sort and page, returning up to 100 per request with login email, status, profile nickname and the linked CONTACT id. This is the one place in the Wix CRM surface with a real search expression rather than a filter object. Two traps worth knowing: search fields defaults to profile.nickname alone, so set search_fields explicitly; and members default to PRIVATE, so pass fieldsets FULL and use an admin-scoped key or the status fields come back as UNKNOWN with no login email. Requires the Wix Members Area app to be installed on the site (Wix's own 'Before you begin' for the Members API).

Wix: Query Sites

List the Wix sites this API key can reach, with each site's id, display name, live URL, editor type, published state and whether it is on a paid (premium) plan. This is the ACCOUNT-level node: it uses the account id stored on the credential and needs no site id, which makes it the first call to run on a new connection and the source of the site picker on every other Wix node. Up to 100 sites per request. Cursor pagination: pass the cursor from the previous response to read the next page, and send filter and sort on the FIRST call only, because Wix ignores them on a cursor request.

Wix: Search Abandoned Checkouts

Find carts that were started and never paid for, with the shopper's email and name, the line items, the cart total and a checkoutUrl the shopper can resume from. This is the recovery-campaign feed. Unlike Search Orders this one DOES take real free text, over first name, last name and email. Up to 100 per page. Requires an eCommerce-enabled app on the site: Wix documents that the eCommerce platform cannot be installed on its own and arrives as a dependency of Wix Stores, Wix Bookings, Wix Restaurants Orders or a comparable business-solution app.

Wix: Search Categories

Find store categories by free text, filter, sort and page, returning each category's id, name, slug, visibility, image and how many items it holds. Note the URL: categories are NOT under the /stores/ prefix, they live on their own /categories/v1 service, and every call must name the category TREE it addresses - which for Wix Stores is always the app namespace @wix/stores. Searchable fields are name and description. Requires the Wix Stores app to be installed on the site (Wix's own 'Before you begin' for Products V3), and an API key whose permissions cover Wix Stores.

Wix: Search Orders

Find orders by filter, sort and page, returning number, status, payment and fulfillment status, buyer, line items, price summary and tags. Despite the name this takes a FILTER OBJECT and has no free-text parameter, so match on buyerInfo.email with $startsWith rather than expecting a search box. Two documented behaviours to plan around: orders with status PENDING or REJECTED are excluded by default, and INITIALIZED orders are never returned at all no matter what you filter on. Up to 100 per page. Requires an eCommerce-enabled app on the site: Wix documents that the eCommerce platform cannot be installed on its own and arrives as a dependency of Wix Stores, Wix Bookings, Wix Restaurants Orders or a comparable business-solution app.

Wix: Search Products

Find store products by free text, filter, sort and page. This is the node to use for anything a human typed: Wix restricts Query Products to seven filterable fields and says outright that looking up products by name or brand belongs here instead. The free text is searched only across the fields named in search_fields, which is why this node defaults them to name and description. Up to 100 products per page. Requires the Wix Stores app to be installed on the site (Wix's own 'Before you begin' for Products V3), and an API key whose permissions cover Wix Stores.

Action nodes 30

Wix: Add Order Activities

Append entries to an order's activity log, up to 300 at a time. MERCHANT_COMMENT is the one to reach for when an automation needs to leave a human-readable note on the order ("flagged as high risk", "customer called"), which is how a workflow explains itself to whoever opens the order later. Other types record refunds, tracking additions, invoices and chargebacks. Wix ships no delete-activity method, so the log is append-only.

Wix: Bulk Delete Products

DESTRUCTIVE. Deletes up to 100 products in one call. Same permanence as the single delete: Catalog V3 documents no trash and no restore for products, so nothing undoes this. This is a Wix BULK method: it returns HTTP 200 even when individual items fail. Check results[].itemMetadata.success and bulkActionMetadata.totalFailures, never the status code alone. Requires the Wix Stores app to be installed on the site (Wix's own 'Before you begin' for Products V3), and an API key whose permissions cover Wix Stores.

Wix: Bulk Insert Data Items

Insert up to 1,000 rows into a CMS collection in one call - the practical way to load a data set from a spreadsheet, an API pull or another collection. Insert-only, so a row whose id already exists fails as WD_DUPLICATE_ID rather than overwriting. Set returnEntity to get the created rows back rather than just their ids. This is a Wix BULK method: it returns HTTP 200 even when individual items fail. Check results[].itemMetadata.success and bulkActionMetadata.totalFailures, never the status code alone.

Wix: Bulk Remove Data Items

DESTRUCTIVE AND IRREVERSIBLE. Removes up to 1,000 rows by id, with the same permanence as the single remove: Wix documents no restore, and reference fields in other collections pointing at the removed rows are cleared. Wix's own recommended retention flow is to query for the ids first, review them, then pass them here in batches. The optional condition filter is a useful safety rail: rows that do not match it are left alone. This is a Wix BULK method: it returns HTTP 200 even when individual items fail. Check results[].itemMetadata.success and bulkActionMetadata.totalFailures, never the status code alone.

Wix: Bulk Update Order Tags

Add or remove tags across up to 100 orders in one call - the practical way to mark a batch of orders as reviewed, exported or escalated. Fully reversible by calling again with the tag on the other side. One documented quirk: if the same tag appears in both assign and unassign, Wix ASSIGNS it. This is a Wix BULK method: it returns HTTP 200 even when individual items fail. Check results[].itemMetadata.success and bulkActionMetadata.totalFailures, never the status code alone.

Wix: Cancel Order

DESTRUCTIVE IN PRACTICE, and worth being precise about: Wix documents only that the order's status changes to CANCELED, says nothing either way about reversibility, and ships NO un-cancel or reinstate method - so treat it as one-way. It does NOT refund money: refunds are a separate Order Billing call, and Wix refuses to cancel an order that still has an authorized transaction (428) until that is voided or refunded. It also refuses on rejected and pending orders. Restocking happens only if you ask for it, and only for items in the Wix Stores inventory. Optionally emails the buyer.

Wix: Create CRM Task

Create a CRM task, optionally attached to a contact, so an automation can put follow-up work in front of a human in the Wix dashboard instead of only writing data. Status defaults to ACTION_NEEDED. Attaching an unknown contact id fails with 400 CONTACT_NOT_FOUND. Note that Wix's own curl example shows an assigneeId field that does not exist in the schema, so task assignment is not available through this API.

Wix: Create Contact

Create a contact in the site's contact list. The info object must include at least ONE of name, phone number or email address. By default Wix refuses to create a contact whose email is already in use by another contact; set allowDuplicates true to override that, which is usually the wrong choice in an automation because it is how duplicate CRM records get created on a retried run.

Wix: Create Data Collection

Create a CMS collection: the site's own database table. The collection object must carry an id, at least one field definition, and a complete permissions object with all four of insert, update, remove and read - Wix simply does not create the collection if any of those are missing. The id is immutable and is the human-readable identifier every other data node uses, not a generated GUID. Counts against the site's collection quota; read it with Wix: Get Site Data Usage.

Wix: Create Order Fulfillment

Record a shipment against an order: which line items went out, and either tracking details or custom fulfillment info. THIS CAN EMAIL A REAL CUSTOMER - Wix says a shipping notification may be sent to the buyer depending on the site's email settings. Only APPROVED orders can be fulfilled. Wix auto-builds the tracking link for fedex, ups, usps, dhl and canadaPost; any other carrier needs the link supplied. The order's overall fulfillmentStatus is recalculated asynchronously, so do not assert on it immediately. Reversible with Wix: Delete Order Fulfillment.

Wix: Create Product

Create a product in the Wix Stores catalog. Every product needs at least one VARIANT with a price, even a product with no options, and a PHYSICAL product also needs physicalProperties. This method does NOT create inventory records: the product exists but has no stock tracking until inventory is set up, so pair it with the inventory nodes. Reversible with Wix: Delete Product, but note that delete is itself irreversible. Requires the Wix Stores app to be installed on the site (Wix's own 'Before you begin' for Products V3), and an API key whose permissions cover Wix Stores.

Wix: Delete Contact

DESTRUCTIVE AND IRREVERSIBLE. Wix states plainly that this "permanently removes" the contact from the contact list, and the Contacts v4 API ships NO trash bin and no restore method, so there is nothing to undo it with. Wix refuses the delete (428) when the contact is also a site member, a Wix user, or holds a valid billing subscription: the member or user must be deleted and the subscription cancelled first, so the correct teardown order is member then contact. Returns an empty object on success.

Wix: Delete Data Collection

DESTRUCTIVE. Deletes a whole CMS collection and everything in it. This is the ONE delete in the Wix CMS with any documented recovery at all, and it is a weak one: Wix says "once a collection is deleted, it can only be restored for a limited amount of time" without saying how long, without naming a restore endpoint, and with no restore method in the API. Wix's own advice is to take a manual backup with the Backups API or export to CSV with the Data Movement Jobs API BEFORE deleting, and to check the collection is not connected to any site page or element first. Returns an empty object.

Wix: Delete Order Fulfillment

DESTRUCTIVE. Removes a fulfillment record from an order. Being precise about what is and is not recoverable: an EQUIVALENT fulfillment can be created again with the same line items and tracking number, so the shipment is not lost forever - but the original record and its creation timestamp are gone, Wix documents no undelete, and the entire published description is "Deletes an existing order fulfillment" with no statement about the order's fulfillmentStatus. Returns the order's remaining fulfillments.

Wix: Delete Product

DESTRUCTIVE. Deletes a product from the store catalog along with its variants. Wix Stores Catalog V3 ships NO trash, archive or restore method for products - the entire documented behaviour is "Deletes a product" - so there is nothing to undo this with through the API. To take a product off the storefront without destroying it, set visible false with Wix: Update Product instead. Returns an empty object. Requires the Wix Stores app to be installed on the site (Wix's own 'Before you begin' for Products V3), and an API key whose permissions cover Wix Stores.

Wix: Find Or Create Contact Label

Get a contact label by display name, creating it if it does not exist yet, and return its key. This is the ONLY way to create a label in Wix (there is no plain create method), and it is idempotent by design: an exact display-name match returns the existing label with newLabel false, so a retried automation run does not produce duplicates. Wix caps the number of labels per site and returns 428 LABELS_QUOTA_REACHED at the ceiling; the number is not published.

Wix: Find Or Create Extended Field

Get a contact custom field by display name, creating it if it does not exist, and return its key. Like labels this is the only creation path and it is idempotent: an existing field comes back with newField false. The data type is IMMUTABLE once the field exists, so a later call with a different dataType returns the original field rather than changing it. Wix hard-caps custom fields at 100 per site and returns HTTP 429 FIELDS_QUOTA_EXCEEDED at the ceiling - that 429 is a quota, not throttling, so retrying will never clear it.

Wix: Insert Data Item

Insert one new row into a CMS collection. This is CREATE-ONLY: supplying an id that already exists fails the request rather than overwriting, which is what makes it the safe choice when a duplicate would be a bug. If you instead want insert-or-replace, use Wix: Save Data Item. The collection must already exist. Reversible with Wix: Remove Data Item, but that removal is permanent.

Wix: Label Contact

Add one or more existing labels to a contact and return the updated contact. Labels are how Wix segments a contact list, so this is the node that drives audience membership from an automation. The label keys must ALREADY EXIST: create them first with Wix: Find Or Create Contact Label, or list them with Wix: List Contact Labels. Reversed by Wix: Unlabel Contact.

Wix: Patch Data Item

Change specific fields on a row, leaving everything else untouched - the only Wix Data write that MERGES instead of replacing. It is also the only one with server-side arithmetic and array mutation: INCREMENT_FIELD adjusts a number in place (negative values decrement), and APPEND_TO_ARRAY / REMOVE_FROM_ARRAY edit a list without read-modify-write, which is how concurrent workflows share a counter without losing updates. One documented limit: only collections created by Wix users can be patched, not Wix app collections.

Wix: Publish Site

PUBLISHES THE LIVE SITE: makes every change already saved in the editor visible to real visitors immediately. There is no API rollback, though Wix keeps the previous state in the site's history for a manual restore in the dashboard. Takes no parameters beyond the site itself and returns an empty object on success. Fails with 428 SITE_IS_NOT_DEFINED_AS_PUBLISHABLE when the site has neither a template nor a headless structure.

Wix: Remove Data Item

DESTRUCTIVE AND IRREVERSIBLE. Wix states it flatly: "once an item has been removed from a collection, it can't be restored". There is no trash and no restore method, and unlike the collection delete this doc offers no backup escape hatch. It also has a side effect worth knowing: any reference or multi-reference field in ANOTHER collection that pointed at this row is CLEARED. The removed row is returned in the response, which is the only copy you will get. Note the item id is in the path and the collection id is a query parameter.

Wix: Save Data Item

Insert or replace a row in one call, keyed on the item id: no id or an unused id creates the row, an existing id updates it. That makes it the idempotent choice for a workflow that may run twice on the same input - a retried run updates the same row instead of creating a second one. The response's action field says which happened, INSERTED or UPDATED. The trap: saving over an existing id REPLACES the row wholesale, so fields you leave out lose their values. Use Wix: Patch Data Item when you mean to merge.

Wix: Truncate Data Items

DESTRUCTIVE AND IRREVERSIBLE, and the single most dangerous call in this connector. It empties an ENTIRE collection, and its only parameter is the collection id - no filter, no condition, no dry run, no confirmation. Wix states "once items have been removed from a collection, they can't be restored", offers no trash and no restore method, and does not mention the Backups API here at all. Reference fields in other collections that pointed at the removed rows are cleared. The collection itself survives, empty. Returns an empty object.

Wix: Unlabel Contact

Remove one or more labels from a contact and return the updated contact. This removes the ASSOCIATION only: the label itself still exists on the site and still applies to every other contact carrying it, so it is fully reversible with Wix: Label Contact. Wix's own reference is inconsistent about where labelKeys travels (its schema says querystring, its curl example sends a JSON body); this node sends the body form, which is what the working example shows.

Wix: Update CRM Task

Update a CRM task: change its title, description, due date, attached contact, or flip its status to COMPLETED. The task's CURRENT revision must be inside the task object for optimistic concurrency. Wix returns revision as a STRING here ("1", "4") even though the contact revision is an integer, so pass it back exactly as it came out of Wix: Query CRM Tasks.

Wix: Update Contact

Update a contact's details. The contact's CURRENT revision must be supplied: Wix uses it for optimistic concurrency and rejects the call if another writer got there first, which is what stops two automations silently overwriting each other. Read it from Wix: Get Contact immediately before updating. One documented limitation: the primary EMAIL of a contact who is also a site member cannot be changed here at all; that has to go through the member's login email in the Members API.

Wix: Update Inventory Item

SET a variant's stock level at one location, or flip it between tracked and untracked. The inventoryItem object must carry its current revision (optimistic lock) and exactly ONE of quantity or inStock: sending quantity implies tracked stock, sending inStock implies status-only tracking with no count. This is an absolute SET, not an adjustment, so two concurrent workflows doing read-modify-write will fight - the revision check is what makes the loser fail loudly instead of silently losing a sale's worth of stock. variantId, locationId and productId are immutable. Requires the Wix Stores app to be installed on the site (Wix's own 'Before you begin' for Products V3), and an API key whose permissions cover Wix Stores.

Wix: Update Order

Update the editable parts of an order: buyer email, language, billing and recipient addresses and contact details, shipping destination, weight unit, the archived flag, attribution source, the seen-by-a-human flag and extended fields. Deliberately NOT editable here - pricing and line items go through Draft Orders, and payment status has its own method. Removing buyerInfo or contactDetails entirely is rejected. Reversible: send the previous value back.

Wix: Update Product

Update a product. Two Wix behaviours make this sharper than a normal patch. First, the product object must carry its CURRENT revision or the call is rejected - that is the optimistic lock. Second, ARRAY fields (options, modifiers and variantsInfo.variants) are FULL OVERWRITES, not merges: send the complete array or you will delete the entries you left out, and updating variants means also sending options. A variant sent without an id is created as a new one. Requires the Wix Stores app to be installed on the site (Wix's own 'Before you begin' for Products V3), and an API key whose permissions cover Wix Stores.

Connecting Wix takes one credential

Wix authenticates with an account API key created in the API Keys Manager at manage.wix.com, which only an account owner or co-owner can do. The same screen shows the account id, so both values are copied once from one place: the key is the secret, and the account id is stored beside it because a key is minted inside exactly one account and is meaningless outside it. Two details about how Wix wants the key sent are built into the connector, and both are common ways a hand-rolled integration fails. The key is placed in the Authorization header with no Bearer prefix, because Wix rejects the scheme, and each request carries exactly one target header: the account id for account-level calls, the site id for site-level ones, never both together. When you create the key, Wix asks which sites it may reach, either every site in the account or an explicit list, and a key pointed at a site outside its permitted list returns a 403 rather than a 404. Access to the interesting node families depends on which apps are installed on the site rather than on a plan tier: the Stores catalog nodes need Wix Stores, the members nodes need the Members Area, and eCommerce is not installable on its own because it arrives as a dependency of Wix Stores, Bookings or Restaurants Orders. The contacts, CRM task and CMS nodes work on a plain site with nothing added.

1

Sign in to Wix as the account owner or a co-owner and open the API Keys Manager at manage.wix.com. Create a key, choose whether it reaches all sites or a named list, and copy both the key and the account id shown on that page.

2

In Mattering Automations, open Connectors, click Add Connector, choose Wix, and create a credential with the key and the account id.

3

Click Test Connection. Mattering calls the account-level site list, which needs no site id and no site of any kind, so it proves the key and the account id together on a brand new connection.

4

All 55 Wix nodes appear in the canvas palette. Run Wix: Query Sites first: it returns each site in the account, and every site-level node's site picker is filled straight from it, so you never have to find an id by hand.

Common uses for the Wix MCP

Turn an inbound lead into a contact with a follow-up attached

A form submission, an email, or a row in another system arrives, and the workflow checks for an existing person with Wix: Query Contacts before writing anything. Wix: Create Contact adds them if they are new, Wix: Update Contact merges new details onto an existing record, Wix: Label Contact tags them for the segment they belong to, and Wix: Create CRM Task opens the follow-up with an owner and a due date. Wix: List Contact Labels and Wix: Find Or Create Contact Label keep the label vocabulary from drifting into near duplicates, and Wix: Find Or Create Extended Field does the same for custom contact fields.

Keep the store catalog in step with wherever the truth lives

Wix: Search Products finds products by free text, filter and sort, Wix: Create Product and Wix: Update Product write them, and Wix: Query Inventory Items and Wix: Update Inventory Item handle stock separately, because creating a product in Wix does not create its inventory. Two behaviours are worth designing around and both are stated on the nodes: Wix: Update Product treats options, modifiers and variants as full array overwrites, so a partial array removes what it leaves out, and Catalog V3 omits fields such as description, url and currency from responses unless you request them, so a missing field is usually an unrequested one.

Run the operational half of a store without opening the dashboard

Wix: Search Orders and Wix: Get Order pull the day's orders, Wix: Create Order Fulfillment records a shipment with its tracking number, Wix: List Order Fulfillments and Wix: List Order Transactions read back what happened, and Wix: Bulk Update Order Tags and Wix: Add Order Activities annotate an order for the humans who look at it later. Wix: Search Abandoned Checkouts is the recovery surface. Two honest caveats live on these nodes: order search excludes pending and rejected orders unless you filter for them, and creating a fulfillment can send a real email to the buyer depending on the site's settings.

Use the Wix CMS as the database a workflow already needed

The 13 Wix Data nodes are the highest reuse per node in the connector because they carry no vertical assumptions. Wix: List Data Collections and Wix: Get Data Collection describe what exists, Wix: Query Data Items and Wix: Get Data Item read rows, and Wix: Insert Data Item, Wix: Patch Data Item and Wix: Bulk Insert Data Items write them. The one to read twice is Wix: Save Data Item: it replaces a row wholesale when the id already exists, so fields you leave out are lost, and Wix: Patch Data Item is the merge you probably wanted. Wix: Get Site Data Usage reports how close a site is to its storage and item ceilings, which is the only reliable way to see those numbers.

One key, many sites, chosen per step

A Wix account API key can be scoped to every site in the account, which is exactly the case a multi-site operator has and the case a single connection normally makes awkward. Here the account lives on the credential and the site lives on the node, so one connection covers the whole account and each step names its own site through a picker sourced from Wix: Query Sites. A workflow can read a collection on one site and write a contact on another, and dependent pickers pass the site through, so a product list only ever shows products from the site that step is pointed at.

Give an agent the read surface and gate the rest

The safest surface to hand an assistant is the 25 read nodes plus the reversible writes: look up a contact, check stock, read an order, query a collection, open a task. The 9 destructive nodes are flagged as destructive so they can sit behind a condition, an approval task, or nothing at all. Wix: Truncate Data Items deserves the most attention of any node here, because its only input is the collection and it takes every row in one call with no filter and no dry run.

Example: A daily abandoned checkout sweep that ends in a task somebody actually sees

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a daily schedule fires in Mattering Automations.

2

Wix: Search Abandoned Checkouts returns yesterday's abandoned carts for the chosen site, with the buyer's email and the cart contents.

3

Wix: Query Contacts looks for each buyer by email. Where there is no match, Wix: Create Contact adds them, and either way Wix: Label Contact applies an abandoned checkout label so the segment stays queryable in the Wix dashboard.

4

A condition splits on cart value: small carts get a label and nothing else, larger ones continue.

5

Wix: Create CRM Task opens a follow-up on the larger carts with the buyer, the cart total and a due date, assigned to whoever owns recovery that week.

6

Wix: Insert Data Item appends a row to a CMS collection so the sweep has a history, and a Mattering task opens for a person only when the day's total moves further than a normal day should.

Wix MCP questions, answered

What Wix operations are supported?

55 nodes: 25 read and 30 action. Sites and platform (query sites, publish a site, read site data usage). CRM (query, get, create, update and delete contacts, label and unlabel them, list and find or create labels and extended fields, query and get members, and query, create and update CRM tasks). Stores catalog (catalog version, search and get products, create, update, delete and bulk delete them, query, get and update inventory items, search categories and list the items in one). eCommerce (search and get orders, update, cancel and tag them, add order activities, list and create fulfillments, delete a fulfillment, list order transactions, search abandoned checkouts). CMS (list, get, create and delete collections, query, get, insert, save, patch and remove items, bulk insert and bulk remove, and truncate a collection). Deliberately not built: Bookings, Events, Restaurants, Blog, Forum, Portfolio, Pricing Plans, Loyalty, Donations, Inbox messaging, domains and account administration, media uploads, and the checkout, cart, draft order and refund surfaces.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

Wix already publishes its own MCP server, and it is built into Claude. Why use this connector?

Both are true, and for some jobs the vendor server is the better answer. Wix hosts an MCP server at mcp.wix.com, publishes an npx package that runs it locally, and ships it as a built-in Claude connector that needs no configuration. Its roughly 17 tools cover Wix documentation search, code generation for the Wix platform, site management, and generic calls into the Wix API, authenticating with interactive sign-in or with an API key. For a developer asking questions while building a Wix site, that is the right tool and this connector is not trying to replace it. What this connector adds is everything that happens when nobody is watching: 55 typed nodes that run on a schedule or from another app's event, chain with every other connector in a single workflow so a Wix order can open a task, update a spreadsheet and post to a channel in one run, hold the key once in a shared workspace rather than in each person's local config, populate site and product pickers instead of asking for raw ids, and mark the nine destructive operations as destructive so they can be gated.

Do I need a paid Wix plan to use the API?

Wix does not state a plan tier for API access on any of the families this connector covers, and we are not going to invent one. What Wix does document are two other gates, and they are the ones that actually stop a workflow. The first is app installs: the Stores catalog nodes need the Wix Stores app on the site, the members nodes need the Members Area, and eCommerce cannot be installed on its own because it arrives as a dependency of Wix Stores, Bookings or Restaurants Orders. A bare site has none of those, so those nodes have nothing to talk to until the apps are added, while the contacts, CRM task and CMS nodes work on a plain site. The second is the key's own permissions: a key is scoped to all sites or to an explicit list, and pointing it at a site outside that list returns a 403. Creating an account and a key does not require a purchase.

What are the Wix API rate limits?

Wix publishes none. There is no rate limit, quota or throttling article anywhere in its REST documentation, no documented rate limit headers, and no per-endpoint table, so no number appears on this page. The one piece of published guidance is that a 429 usually means too many requests in a short period and the advice is to wait a minute and retry. There is a trap in that, and it is worth knowing before you write retry logic: Wix reuses 429 for resource quotas as well as for throttling. Creating a 101st contact custom field returns 429 with a quota code, and waiting will never clear it, because it is a ceiling rather than a rate. Wix also enforces storage, item count and collection count ceilings on the CMS that hard fail writes, and it does not publish those numbers either, so read them per site with Wix: Get Site Data Usage rather than assuming a value.

Why does every node ask which site to use?

Because one Wix API key routinely reaches many sites. A key is created inside one account and can be scoped to every site in it, so putting the site on the credential would force one connection per site and make the multi-site workflows those keys exist for impossible to express. The account id lives on the credential, where it belongs, since a key is meaningless in any other account, and the site lives on the node as a picker fed by Wix: Query Sites, which is an account-level call that works before you know a single id. Dependent pickers pass the chosen site through, so a product, order or collection list only ever shows things from the site that step is pointed at. It also lets the connector send the right header, because Wix requires exactly one of the account header and the site header on every call.

Can an AI agent delete something it should not?

Nine nodes are flagged destructive so you can decide: Wix: Delete Contact, Wix: Delete Product, Wix: Bulk Delete Products, Wix: Cancel Order, Wix: Delete Order Fulfillment, Wix: Delete Data Collection, Wix: Remove Data Item, Wix: Bulk Remove Data Items and Wix: Truncate Data Items. The honest detail is that Wix's own documentation is uneven about what is recoverable, so each node says what Wix actually states. Deleting a contact is documented as permanent. Removing data items, in single, bulk or truncate form, is documented as unrestorable. Deleting a data collection has a time-limited restore that Wix mentions without publishing a duration or an endpoint, so the node repeats Wix's advice to take a backup or a CSV export first. Cancelling an order has no un-cancel call and does not refund anything. For products, Wix makes no permanence claim at all, so the node says there is no documented way to undo it and points at the softer alternative, which is setting the product to hidden. Wix: Truncate Data Items is the sharpest edge in the connector: one collection id, every row, no filter and no dry run. Keep agents on the read nodes and put these behind a condition or an approval step.

Will the product nodes work on my store?

They work if the site is on the Wix Stores Catalog V3, and not if it is on the older V1. Wix states that the two are not backwards compatible, that a site is on exactly one of them, and that moving to V3 is permanent, so this connector targets V3 throughout rather than shipping two product object shapes. Rather than leaving you to discover that halfway through a run, Wix: Get Catalog Version is a first-class node: one cheap call tells a workflow which catalog a site is on, and a condition can stop cleanly instead of failing at the fifth step. The store also has to have the Wix Stores app installed, and categories are worth knowing about because they live outside the stores service in the Wix API, which is why Wix: Search Categories and Wix: List Items In Category are separate nodes.

55 nodes waiting on the canvas

Put Wix to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Wix is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products