Skip to main content
Storefront events fire when a shopper interacts with the cart or checkout. Storefront events trigger sync automations. This means they run on a user’s critical path and must be fast and deterministic. Because of this, they have some contraints:
  • they can’t use any of the Agent steps
  • they can’t use delay, wait_for_event, parallel, map steps
  • they have execution timeout of 10 seconds
  • only one automation can be active for each event
Shopper PII in storefront event payloads is privacy-safe. Fields like customer_email can be null, and address details may be omitted when they are not needed for the event.

Cart

New shopping cart initialized.
object
Item added to a cart.
object
Cart item quantity changed.
object
Item removed from a cart.
object

Checkout

Checkout session initiated.
object
Billing address provided during checkout.
object
Payment provider selected during checkout.
object
Checkout completed successfully.
object
Payment failed during checkout.
object
Customer submitted a discount code at checkout. Synchronous return event — automation must produce a DiscountValidationResult.
object
Required automation output:
object

Shared Types

object
object