| name | sales-memberful |
| description | Memberful platform help — membership + paid-subscription layer (Patreon-owned, memberful.com) for creators/publishers/communities: checkout, trials, coupons, gated content, private podcasts/newsletters/downloads, and OAuth SSO, on your own Stripe. Developer surface: a GraphQL API (endpoint ACCOUNT.memberful.com/api/graphql, Authorization: Bearer key from Settings > Custom applications; queries + mutations for members/subscriptions/passes/plans/coupons; cursor pagination) and 21 HMAC-SHA256-signed webhooks (X-Memberful-Webhook-Signature; member/subscription/order/plan/download events). WordPress/Discord/Mailchimp/Kit/Zapier integrations. Use when querying/mutating members via GraphQL, verifying a signed webhook, wiring OAuth SSO, untangling the dashboard-Plan-vs-API-Pass terminology, or weighing the 10%/4.9% fees. Do NOT use for membership-platform strategy/comparison (use /sales-membership), checkout-conversion optimization across tools (use /sales-checkout), or email marketing (use /sales-email-marketing). |
| argument-hint | [describe what you need help with in Memberful] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","membership","creator","platform"] |
| github | https://github.com/memberful |
Memberful 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) Query or mutate members / subscriptions / passes / coupons via the GraphQL API
- B) Verify a signed webhook and react to a lifecycle event (signup, renewal, refund…)
- C) Add "Sign in with Memberful" (OAuth SSO) to your own app
- D) Gate content / set up private podcasts / downloads (WordPress plugin or website builder)
- E) Sync members to Discord / Mailchimp / Kit / a CRM
- F) Pick a plan / understand the 10% vs 4.9% transaction fees
-
Front-end or back-end? Browser gating/checkout = WordPress plugin / website builder. Server-side member ops, OAuth callback, and webhook verification = GraphQL API + middleware (Bearer key, server-side only). This decides everything.
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... |
|---|
| Choosing or comparing membership/course platforms | /sales-membership {question} |
| Checkout / trial / dunning / upsell optimization across tools | /sales-checkout {question} |
| Email sequences/newsletters to members (Memberful doesn't send marketing email) | /sales-email-marketing {question} |
| Wiring Memberful into a CRM/warehouse or other tools generically | /sales-integration {question} |
| Membership/community structure, pricing, and retention strategy | /sales-membership {question} |
When routing, give the exact command, e.g. "Platform comparison — run: /sales-membership Memberful vs a hosted course platform".
Step 3 — Memberful platform reference
Read references/platform-guide.md for the full reference — the module map (GraphQL vs front-end vs webhook vs UI), the Plan-vs-Pass terminology trap, plan/transaction-fee gates, the member data model with JSON shapes, and quick-start recipes (query members paginated; verify a webhook + re-fetch; OAuth SSO).
Read for the integration surface — the GraphQL endpoint , API-key auth (from Settings → Custom applications), example query/mutation, Relay cursor pagination, member-metadata limits, the GraphQL error convention (HTTP 200 + ), the , the signature scheme (), and OAuth.
