Menu

Mattering Automations Wix integration

Connect Wix to Mattering Automations: sites, contacts, members and CRM tasks, Stores products and inventory, eCommerce orders and fulfillments, and the Wix CMS as workflow steps, authenticated with one account API key.

The Mattering Automations Wix integration puts 55 Wix operations on your automation canvas: query the sites in your account and publish one, create and update contacts with labels and extended fields, read members, open and update CRM tasks, search and write Stores products and inventory, work eCommerce orders with fulfillments and tags, read abandoned checkouts, and read and write collections in the Wix CMS.

The credential is a Wix account API key, created in the API Keys Manager by an account owner or co-owner, stored alongside the account id shown on the same screen. Two things about how Wix wants that key sent are handled for you and are worth knowing because they are the usual reasons a hand-built Wix client fails: the key goes into the Authorization header raw with no Bearer prefix, and every call carries exactly one target header, the account id or the site id, never both. Setup takes a few minutes and this guide walks through each step before the full node reference.

One structural point is easier to absorb now than to hit later. A single Wix API key can reach every site in the account, so the site is not part of the credential. The account id is stored once with the key, and each site-level node carries its own Site field, which is a picker fed by Wix: Query Sites. You connect once for the account, then choose a site per step, and dependent pickers such as products and orders pass that site through so they only ever list things from the site the step is pointed at.

Before you start

  • A Wix account you own or co-own. Wix only lets account owners and co-owners create API keys, so a contributor or an editor on someone else's site cannot mint the credential this integration needs.
  • The apps the nodes you want actually depend on. The Stores catalog nodes need the Wix Stores app installed on the site, the members nodes need the Members Area, and Wix eCommerce cannot be installed 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, so a brand new free site is enough to verify the connection.
  • For the product nodes specifically, a site on the Wix Stores Catalog V3. Wix states that V1 and V3 are not backwards compatible, that a site runs on exactly one of them, and that moving to V3 is permanent. Every product node here targets V3, and Wix: Get Catalog Version is built as a one-call check so a workflow can find this out cheaply rather than halfway through a run.
  • A decision about which sites the key may reach. When you create it, Wix asks for all sites in the account or an explicit list. A key pointed at a site outside its permitted list returns a 403, not a 404, which is worth remembering when a node fails on one site and works on another.
  • A Mattering workspace with access to the Automations app.
  • Not required and not stored here: a site id. Sites are chosen on the nodes from a picker, which is what lets one credential cover an entire Wix account.

Create a Wix API key

Mattering authenticates to Wix with an account API key. Both values you need are on one screen, which keeps this short: the key itself, and the account id that gets stored beside it because a key is minted inside exactly one Wix account and means nothing outside it. There are no OAuth apps to register and no redirect to configure. Wix documents API keys as the path for external integrations that call Wix on your behalf, and documents that they are not available to third-party Wix apps, which use OAuth instead.

Sign in to Wix as the account owner or a co-owner and open the API Keys Manager at manage.wix.com.
Click Generate API Key, name the key something an operator will recognise later, and choose its permissions.
Choose which sites the key may reach: All sites for every site in the account, or Specific sites with an explicit list.
The key value is shown once. Copy it before leaving the page, and copy the account id from the same screen while you are there, because the credential needs both.
Wix's own troubleshooting for this screen covers not receiving a verification code, so expect account verification to be part of creating a key. Have the phone or device on the account to hand.
A key is account wide by design. Scoping it to a named list of sites is the practical way to keep an automation away from a site it should never touch.

Connect Wix to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Wix from the list.
Click Create new credential, paste the API key into API Key and the account id into Account ID, then save.
The key is stored encrypted in Google Secret Manager and never appears in workflow logs. The account id is not a secret and is stored alongside it so the account-level calls can be built.
Click Test Connection. Mattering calls the account-level site list, which takes no site id and works on an account with no sites at all, so it proves the key and the account id together on a brand new connection.
Mattering sends the key in the Authorization header with no Bearer prefix, which is what Wix requires, and picks the account or site header per call. A 401 here almost always means the key value itself, not the header shape.
Click Connect. All 55 Wix nodes appear in your canvas palette.

Verify it works

Open any automation canvas and check the palette for a Wix section listing the read and action nodes. Drop Wix: Query Sites onto the canvas and run a test step. It is the integration's natural probe: it is the one account-level node, it needs no input at all, and it returns each site in the account with its display name and its site id. Those ids are what every other node needs, and you should never have to copy one by hand, because this lister is what fills the site pickers.

Now try a site-level node, because that is the half where the site header matters. Drop Wix: Query Contacts onto the canvas and open its Site field: the picker should list your sites by name. Choose one and run the step. An account with no contacts yet returns an empty list rather than an error, which is still a pass, because it proves the site header was accepted. If you have a store, Wix: Get Catalog Version is the other verify worth doing before you build anything on products, since it tells you in one call whether that site is on Catalog V3.

Everything in this path is read-only, so it cannot reach any of the nine destructive nodes and is safe to re-run whenever you rotate the key.

Node reference

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

Read and query nodes 25

Wix: Get Catalog Version

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

Using the integration

On the automation canvas

Wix nodes chain with every other node in Mattering. A schedule can sweep Wix: Search Abandoned Checkouts each morning and open follow-ups with Wix: Create CRM Task, an inbound webhook from another system can write a row with Wix: Insert Data Item, and an order picked up by Wix: Search Orders can update a spreadsheet, message a channel and open a task in the same run. Two values do most of the wiring: the site, which comes from Wix: Query Sites and is chosen on each node, and whatever id that step needs, which almost always has a picker of its own sourced from the matching lister.

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. A comfortable agent surface is the read nodes plus the reversible writes: look a buyer up with Wix: Query Contacts, check stock with Wix: Query Inventory Items, read an order with Wix: Get Order, and record what happened with Wix: Create CRM Task. Wix publishes an MCP server of its own and you should know about it before choosing. It is hosted at mcp.wix.com, can be run locally through the package Wix publishes, and is available as a built-in connector in Claude with no configuration. Its tools are developer shaped: documentation search, code generation for the Wix platform, site management, and a generic call-any-Wix-API tool. For writing Wix code with an assistant, that is the better fit. This integration is the operations side: typed nodes on a canvas that run unattended on a schedule or an event, chain with every other connector, hold the credential once in the workspace rather than in each person's client config, and flag the destructive operations so they can be gated.

One credential, a site chosen per node

The account id lives on the credential because a key belongs to one Wix account and is meaningless in another. The site lives on the node because one key can reach every site in the account, and forcing one connection per site would make multi-site work impossible to express. In practice that means each site-level node has a Site field that is a picker showing site names, sourced from Wix: Query Sites, and dependent pickers chain the choice through: the product picker on Wix: Update Product lists products from the site you selected on that node, and the fulfillment picker chains twice, through the site and then the order. Wix requires exactly one target header per call, the account id or the site id and never both, and the connector picks the right one for each node rather than leaving it to you.

Contacts, labels and the fields underneath them

The CRM family is the most automatable surface in Wix and it has a shape worth learning once. Labels and extended fields are separate objects that contacts merely reference, so Wix: List Contact Labels and Wix: Find Or Create Contact Label exist to keep a workflow from inventing three spellings of the same segment, and Wix: List Extended Fields and Wix: Find Or Create Extended Field do the same for custom fields. Updates need care in one specific way: Wix: Update Contact requires the record's current revision, and revisions are not consistent across the API. Contacts want an integer, CRM tasks and products want a string, and members want none at all, so read the record back immediately before writing it. Members are their own object too: a member id is not a contact id, and passing one for the other returns a 404. Wix: Query Members and Wix: Get Member default to the full field set, because Wix's default returns unknown status values and no login email.

Products, inventory and orders

Catalog work starts with Wix: Get Catalog Version, because the product nodes target Catalog V3 and a V1 site cannot use them. After that, Wix: Search Products is the lister (it replaces the narrower query method and supports free text as well as filters), Wix: Create Product and Wix: Update Product write, and stock is separate: creating a product does not create inventory, so Wix: Update Inventory Item is its own step. Two behaviours cause most of the surprises. On Wix: Update Product, options, modifiers and variants are full array overwrites, so sending a partial array deletes the entries left out. And Catalog V3 omits fields such as description, url and currency from responses unless you ask for them, so a field that looks missing is usually just unrequested. On the order side, Wix: Search Orders excludes pending and rejected orders unless you filter for them and never returns initialized ones, Wix: Create Order Fulfillment can email the buyer depending on the site's settings and recalculates the order's fulfillment status asynchronously, and Wix: Cancel Order does not refund anything and refuses while an authorized transaction is outstanding.

The Wix CMS as a workflow database

The 13 Wix Data nodes are the most reusable part of the connector because they make no assumptions about what the site sells. Three details save most of the debugging. First, a collection id is a human readable name such as EvalCustomers, not a GUID, and app collections use an AppName/CollectionName form, which matters because Wix's own auto-generated schema text calls it a GUID and the sentence after it says otherwise. Second, Wix: Save Data Item replaces a row wholesale when the id already exists, so omitted fields are lost, and Wix: Patch Data Item is the merge most workflows actually want. Third, reads are eventually consistent, so a read straight after a write may not see it unless the consistent read option is set. Wix: Get Site Data Usage is how you see a site's storage and item counts against its ceilings, which Wix does not publish anywhere else.

The nine destructive nodes, and what Wix actually says about each

Wix: Delete Contact is documented as permanent, with no trash bin in the contacts version this connector targets, and it refuses with a 428 while the contact is also a site member, so delete the member first. Wix: Remove Data Item, Wix: Bulk Remove Data Items and Wix: Truncate Data Items are documented as unrestorable, and the truncate node is the sharpest edge in the whole connector because its only input is the collection: no filter, no condition, no dry run. Wix: Delete Data Collection is the one delete with any documented recovery, and it is weak, since Wix says only that a collection can be restored for a limited amount of time without publishing a duration or a restore endpoint, so take a backup or a CSV export first as Wix advises. Wix: Delete Product and Wix: Bulk Delete Products carry no permanence statement from Wix at all, which is exactly what the nodes say: there is no documented way to undo them, and hiding a product is the softer alternative. Wix: Cancel Order has no un-cancel call and does not refund. Wix: Delete Order Fulfillment loses the record and its timestamp, though an equivalent fulfillment can be created again with the same tracking number. Gate all nine behind a condition or an approval step rather than a bare trigger.

Paging, and why two styles appear

Wix uses offset paging on some families and cursor paging on others, and the connector reflects each one rather than inventing a single style. Contacts, labels, extended fields, members, collections and data items page by limit and offset. Sites, products, categories, inventory, orders, abandoned checkouts and CRM tasks page by cursor. The cursor style has one rule that quietly breaks loops: on a cursor request Wix ignores filter and sort, so send them on the first call only and then carry the cursor. Cursor tokens are also opaque and can be extremely long, so keep them in a workflow variable rather than a short column. Bulk methods have their own trap worth building around: they return HTTP 200 with per-item failures inside the response, so a 200 is not proof the work happened and every bulk node says so.

Troubleshooting

Test Connection fails with a 401
A 401 here is about the key value rather than the header shape, because Mattering already sends it the way Wix wants: raw in the Authorization header with no Bearer prefix. Re-copy the key from the API Keys Manager, watching for leading or trailing whitespace, and confirm the key still exists and has not been revoked. Also confirm the account id came from the same screen as the key, since the account-level probe sends both. If you built a working request by hand elsewhere with a Bearer prefix, that request was not talking to Wix.
A node returns 403 on one site and works on another
That is the key's site scope, not a broken credential. Wix keys are created with access to all sites in the account or to an explicit list, and a key pointed at a site outside its list returns 403 rather than 404, which is why the same node can succeed elsewhere. Check the key's permissions in the API Keys Manager and either add the site or use a key that already covers it. A 403 can also mean the key lacks the permission scope for that particular API even on a site it can reach, so read the error text the node passes through.
The product nodes fail on a site whose store works fine in the dashboard
Check the catalog version first. Every product node here targets the Wix Stores Catalog V3, and a site still on V1 cannot use them, which Wix explains as the two catalogs not being backwards compatible with a site on exactly one of them. Run Wix: Get Catalog Version against that site: it is one cheap call and it answers this directly. The other version of this symptom is a missing app, since the Stores nodes need the Wix Stores app installed on the site, the members nodes need the Members Area, and eCommerce arrives only as a dependency of Wix Stores, Bookings or Restaurants Orders.
An update fails complaining about the revision
Wix requires the record's current revision on most updates and it is not consistent about the type, which is the usual cause. Update Contact takes an integer revision, Update CRM Task, Update Product and Update Inventory Item take a string, and Get Member and the member nodes need none. The safe pattern is always the same: read the record back immediately before writing it and pass through the revision that read returned, rather than storing one from an earlier step in the run. A revision that was correct thirty seconds ago is stale if anything else touched the record.
Get Member returns 404 for a contact that definitely exists
A member id and a contact id are different identifiers for what looks like the same person, and Wix warns about this on nearly every member method. Passing a contact id to Wix: Get Member returns 404. Use Wix: Query Members to find the member record and its own id. While you are there, note that Wix defaults member queries to the public field set, which returns unknown status values and no login email, so the nodes here default to the full field set instead, and that member search defaults to nickname only unless the search fields are named.
A bulk node returned success but only some of the records changed
That is Wix's documented behaviour rather than a fault. The bulk methods answer HTTP 200 and report per-item outcomes inside the response body, with a total failure count alongside them, so the transport status says nothing about whether every item worked. Read the per-item results rather than the node's success flag, and branch on the failure count. The same shape applies to bulk product deletes, bulk order tag updates and the bulk data item nodes, and each one says so in its description.
A 429 that never clears no matter how long the workflow waits
Wix reuses 429 for two different things. One is throttling, where the published guidance is simply to wait a minute and retry, and Wix does not publish any rate limit numbers at all. The other is a resource quota, such as the hundredth contact custom field on a site, which returns 429 with a quota code and will never clear by waiting because it is a ceiling rather than a rate. Read the error code in the response before retrying. For storage and item count ceilings on the CMS, which Wix also does not publish, run Wix: Get Site Data Usage against the site to see where it actually stands.
A row lost fields after an update, or a product lost its variants
Two different overwrite behaviours, both documented and both easy to trip. Wix: Save Data Item replaces a row wholesale when the id already exists, so any field you left out of the request is gone. Use Wix: Patch Data Item when you mean to merge. On the catalog side, Wix: Update Product treats options, modifiers and variants as full array overwrites, so sending two variants on a product that had five deletes the other three. Read the current record first, merge your change into the full array, and send that.
A read straight after a write does not see the write
Wix CMS reads are eventually consistent, so a query that runs immediately after an insert or a patch can legitimately return the old state. The data nodes expose a consistent read option for exactly this case: set it on the read that follows a write in the same run. The related asynchronous case is on orders, where creating a fulfillment recalculates the order's fulfillment status in the background, so a status check chained straight onto Wix: Create Order Fulfillment may read the previous value.
Search Orders is not returning an order that exists
Order search hides things by default rather than failing. Wix excludes pending and rejected orders from search results unless you filter for those statuses explicitly, and never returns initialized ones at all. Add the status filter you need instead of assuming the result set is everything. A second reason for a surprising empty result is field projection on the catalog side: Wix omits several product fields unless the request asks for them, so a workflow filtering on a field it never requested finds nothing.

Wix 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