| name | sales-membervault |
| description | MemberVault platform help — "binge & buy" course/membership platform for creators (membervault.co): host all paid + free products in one marketplace, gamification, warm/hot lead tagging, communities, drip content, and direct Stripe/PayPal with 0% fees. There is no public REST API — integration is Zapier (7 triggers incl. Hot Lead, 2 actions) plus inbound webhooks (grant access from an external cart) and outbound webhooks (push contacts to an ESP). Use when wiring a MemberVault webhook or Zapier integration to grant access on external purchase, routing hot leads into a CRM, connecting an email service because MemberVault doesn't send email, choosing a plan (Free 100-member cap vs 5/15/Unlimited), or hitting limits (video hosting, member cancellation, marketplace design). Do NOT use for course/membership strategy across tools or platform comparison (use /sales-membership), email-marketing strategy (use /sales-email-marketing), or checkout optimization across platforms (use /sales-checkout). |
| argument-hint | [describe what you need help with in MemberVault] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","membership","courses","platform"] |
MemberVault Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Grant/revoke product access from an external purchase (inbound webhook / Zapier action)
- B) Route engagement signals out — Hot Lead, Completed Lesson, Earned EP — into a CRM or outreach tool
- C) Connect an email service (MemberVault doesn't send email)
- D) Configure a module — products, communities, gamification, drip, marketplace page
- E) Pick a plan — Free (100-member cap) vs 5 / 15 / Unlimited
- F) Fix a problem — video hosting, member cancellation, marketplace design, search
-
Where does data need to flow? Into MemberVault (grant access) / out of MemberVault (sync contact, route lead) — this decides inbound vs outbound webhook vs Zapier.
Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| Course/membership strategy, retention, or platform comparison | /sales-membership {question} |
| Email sequences and broadcasts (the ESP you connect) | /sales-email-marketing {question} |
| Email deliverability / inbox placement | /sales-deliverability {question} |
| Checkout / order-bump / upsell optimization across tools | /sales-checkout {question} |
| Selling digital products (pricing, launch) across tools | /sales-digital-products {question} |
When routing, give the exact command, e.g. "This is a retention-strategy question — run: /sales-membership how do I reduce course churn".
Step 3 — MemberVault platform reference
Read references/platform-guide.md for the full reference — the module map (what's webhook/Zapier-accessible vs UI-only), the plan gates (the Free 100-member cap and the product-count tiers), the email/Stripe/PayPal model, the member/product data model with JSON shapes, and quick-start recipes (grant access via inbound webhook; route hot leads into a CRM; sync members to an unsupported ESP).
Read for the integration surface — there's ; it documents the inbound webhook ("API URL" from Integrations → Advanced), the outbound webhook ("Call a web hook" product action), and the full Zapier trigger/action list.
