Handle wishlist submission events from the Goodshuffle Pro Website Integration widget
domain: docs.goodshuffle.dev · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Listen for gspro-wishlist.submit to fire logic immediately when a user submits the wishlist form (before the API call completes) — use this only for non-blocking actions like analytics
Read data.detail.contact (firstName, lastName, email, phone) and data.detail.venue (address fields, venueName) from the submit event payload
Require Website Integration version 0.5.1+ and listen for gspro-wishlist.submit-complete to detect that the underlying wishlist API call succeeded
Use the submit-complete event (not submit) to trigger redirects to a thank-you page or open a confirmation modal
Read data.detail.wishlist as an array of cart items, each shaped like the item-card click payload, for order/lead-handoff logic
Known gotchas
Using gspro-wishlist.submit (rather than submit-complete) for redirects can navigate the user away before the underlying API call finishes, silently dropping the submission
submit-complete is only available on Website Integration 0.5.1+; older embeds never fire it, so version-check before relying on it
All personal data (contact/venue info) arrives client-side in the DOM event payload — treat it as user-supplied input needing validation before forwarding to another system
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?