Skip to main content
Storefront events fire when a shopper interacts with the cart or checkout. Like every Colossal app event, they trigger agents and are available through the HTTP request action for forwarding to external systems. These events share the same envelope as every other Colossal event. See Colossal triggers for the envelope format, webhook security, and delivery best practices. Cart and checkout triggers also support synchronous execution; see trigger modes.

​
Common Types

These types are reused across multiple event payloads.
​
CartItemData
object
​
Address
object

​
CART_CREATED

New shopping cart initialized.
​
payload
object

​
CART_ITEM_ADDED

Item added to a cart.
​
payload
object

​
CART_ITEM_UPDATED

Cart item quantity changed.
​
payload
object

​
CART_ITEM_REMOVED

Item removed from a cart.
​
payload
object

​
CHECKOUT_STARTED

Checkout session initiated.
​
payload
object

​
CHECKOUT_ADDRESS_SET

Billing address provided during checkout.
​
payload
object

​
CHECKOUT_PAYMENT_SELECTED

Payment provider selected during checkout.
​
payload
object

​
CHECKOUT_COMPLETED

Checkout completed successfully.
​
payload
object

​
CHECKOUT_PAYMENT_FAILED

Payment failed during checkout.
​
payload
object

​
CHECKOUT_VALIDATE_DISCOUNT_CODE

Customer submitted a discount code at checkout. Synchronous return trigger — workflow must produce a DiscountValidationResult. See trigger modes.
​
payload
object
Required workflow output:
​
DiscountValidationResult
object