Commerce & Payments · Integration
Wix
Add Wix to your product for your customers, and give your AI agents governed access to it.
Wix is best treated as a per-site platform rather than one account. Your app is installed on an individual site, the token it receives belongs to that site instance, and what the site can answer depends on which business solutions the owner added: eCommerce brings orders, products and inventory, Bookings brings services and sessions, and Contacts holds the CRM records. A site without Stores installed cannot answer a product call at all, so detecting what each instance supports belongs in onboarding rather than in an error handler. An owner running five sites is five separate installs to keep straight. fastn keeps each site instance and its refresh token apart, and follows Wix API changes for you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a site owner install your app on their own site, so orders and contacts reach your product per instance.
Detect which Wix business solutions a site has before your interface offers a feature that site cannot support.
Write products and inventory back to a Wix Stores site so a merchant maintains one catalogue rather than two.
Read bookings and the services behind them so scheduling in your product reflects what the site already accepted.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers a question about one site's recent store orders without touching the owner's other sites.
An agent updates a contact or adds a label within scoped permissions, and the site instance is recorded.
An agent checks which bookings are still unconfirmed for a service and reports what it found.
Example prompt
List this site's Wix Stores orders from the past week and flag any with no fulfilment yet.
Set up Wix in 4 steps
- 01Enable the Wix connector from your fastn dashboard.
- 02Have each customer authorise their own Wix account, so calls run under their credentials rather than a shared key.
- 03Decide which orders, payments and customers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Wix integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Wix integration without building it. Your customers connect their own Wix account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Wix update is not your on-call problem.
- One integration serves your product and your agents. The same governed Wix connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Squarespace
Shopify
WooCommerceOften used alongside
Tools the same teams tend to run next to Wix, across other categories.
NetSuite
Notion
Box
DocusignWix integration FAQ
How do I add a Wix integration to my product?
Enable the Wix connector in your fastn dashboard, then let each customer authenticate their own Wix account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Wix client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Wix account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Wix account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Wix integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent answers a question about one site's recent store orders without touching the owner's other sites.
Who maintains the Wix integration?
fastn does. When Wix changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Wix integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Wix integration?
A common starting point: let a site owner install your app on their own site, so orders and contacts reach your product per instance. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Wix integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Wix does not change your per-connector cost. You can start free with 3 connected accounts.
Add Wix to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.