wix-cli-backend-event

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

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/nirganon/nir-beauty --skill wix-cli-backend-event-nirganon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wix-cli-backend-event
Source: https://github.com/nirganon/nir-beauty/tree/main/.agents/skills/wix-cli-backend-event
Command: npx skills add https://github.com/nirganon/nir-beauty --skill wix-cli-backend-event-nirganon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building backend logic that reacts to Wix site activity—like a new contact, order, or booking—requires correctly wiring SDK webhook handlers, extension builders, and registration files, which is error-prone without guidance. ## Core Features & Use Cases - Event Extension Scaffolding: Creates the two required files per event (<event-name>.ts handler and <event-name>.extension.ts builder with a unique UUID) under src/extensions/backend/events/. - Common Event Reference: Provides SDK imports, handler calls, and required permissions for CRM, eCommerce, Bookings, and Blog events. - Permission Elevation: Shows how to use auth.elevate from @wix/essentials when calling Wix APIs inside handlers. - Use Case: When a customer places an order on a Wix site, automatically run backend logic such as syncing the order to an external CRM or sending a notification. ## Quick Start Ask the assistant to create a Wix CLI backend event extension for a specific event, such as "create an event extension that runs when a contact is created."

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.

What Wix events can I handle with event extensions?

Common events include CRM contact created/updated/deleted, eCommerce order created/approved and cart events, bookings confirmed/canceled, and blog post created/updated. Each uses an SDK import like @wix/crm or @wix/ecom with a corresponding handler call.

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 Wix dashboard. Attempting to register a second handler for the same event will conflict.

How do I call Wix APIs inside an event handler?

Use auth.elevate from @wix/essentials to elevate permissions before calling Wix APIs, for example auth.elevate(items.query) from @wix/data. This ensures the call runs with the required permission scopes.

Why is my Wix event extension not triggering?

Common causes include 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.