wix-cli-backend-event

Creates Wix CLI backend event extensions that respond to site events via SDK webhooks.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/yaelbro/Shelf-Control --skill wix-cli-backend-event-yaelbro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wix-cli-backend-event
Source: https://github.com/yaelbro/Shelf-Control/tree/main/.agents/skills/wix-cli-backend-event
Command: npx skills add https://github.com/yaelbro/Shelf-Control --skill wix-cli-backend-event-yaelbro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @wix/astro, @wix/crm, @wix/ecom, @wix/bookings, @wix/blog, @wix/essentials, @wix/data, and includes references (resource) components.

What problem does it solve? Building backend logic that reacts to Wix site events (like a new contact or paid order) requires correctly wiring SDK event handlers, extension builder files, UUIDs, and registration in the Wix CLI project structure, which is easy to get wrong. ## Core Features & Use Cases - Event Extension Scaffolding: Generates the two required files per event: a handler file importing the SDK event and an extension builder file using extensions.event() with a unique UUID. - Extension Registration Guidance: Ensures the new event is imported and registered in src/extensions.ts so it actually activates. - Common Events Reference: Provides SDK imports, handler calls, and required permissions for CRM, eCommerce, Bookings, and Blog events. - Use Case: When a contact is created on a Wix site, automatically run custom logic such as syncing to an external CRM or sending a welcome email using an elevated-permission handler. ## Quick Start Create a Wix CLI backend event extension that logs new contacts whenever a contact is created on the site.

Frequently Asked Questions about wix-cli-backend-event

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Wix CLI backend event extension?

Create a folder under src/extensions/backend/events/<event-name>/ containing a handler file that imports the SDK event (e.g. onContactCreated) and an .extension.ts file using extensions.event() with a unique UUID. Then register it in src/extensions.ts with .use().

What Wix events can I handle with SDK webhooks?

Common events include CRM contact created/updated/deleted, eCommerce order created/approved and cart events, Bookings confirmed/canceled, and Blog post created/updated. Each has a specific SDK import, handler call, and required permission scope.

Can I have two handlers for the same Wix event?

No. Only one handler per event is allowed in the app, including handlers configured in the dashboard. Attempting to register a second handler for the same event will conflict.

Why is my Wix event extension not triggering?

Common causes are missing registration in src/extensions.ts, unconfigured permission scopes in the app dashboard, or not releasing a version before testing. Some events are also not fully testable in local development.

How do I call Wix APIs inside an event handler with permissions?

Use auth.elevate from @wix/essentials to wrap the API call so it runs with the required permissions. For example, wrap items.query from @wix/data to query a collection inside the handler.