Skip to main content
The Seller module workflows emit events after they write. Subscribe to them to send notifications, sync an outside system, or start follow-up work without polling. The event names are exported from @mercurjs/core/workflows as SellerWorkflowEvents, SellerMemberWorkflowEvents, and MemberInviteWorkflowEvents.
src/subscribers/store-approved.ts
This subscriber loads the store when it’s approved. Store events carry only the id, so retrieve the record when you need more.

Store events

SellerWorkflowEvents covers creation, updates, and every status transition. The address, professional details, payment details, and region workflows don’t emit events.

Membership events

SellerMemberWorkflowEvents covers memberships changed directly. Accepting an invite emits member_invite.accepted instead of seller_member.created.

Invite events

MemberInviteWorkflowEvents covers team invites. The created payload includes the signed token, so a subscriber can build the invite link.
The member_invite.created payload carries a working invite token. Don’t log it or forward it to systems that shouldn’t grant store access.