| name | sales-viral-loops |
| description | Viral Loops (viral-loops.com) platform help — referral & viral-marketing campaign builder for startups/SaaS/ecommerce: templates for referral programs, pre-launch waitlists, giveaways, milestone referrals, ambassador programs, and leaderboards, plus an embeddable widget. REST API (app.viral-loops.com/api/v3, per-campaign publicToken, POST /campaign/participant), webhooks (participant/referral-count/convert/reward), and two-way Zapier. Use when adding or syncing participants to a campaign via the API or Zapier, attributing referrers so referrals count, reacting to referral-milestone or conversion webhooks to fulfill rewards, running a pre-launch waitlist with viral referral, deciding referral vs affiliate program, handling fake signups in a giveaway, or choosing the Build vs Accelerate plan. Do NOT use for audience-growth/referral strategy across tools (use /sales-audience-growth), designing an affiliate program across tools (use /sales-affiliate-program), or email deliverability (use /sales-deliverability). |
| argument-hint | [describe what you need help with in Viral Loops] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","audience-growth","referral","platform"] |
| github | https://github.com/viralloops |
Viral Loops 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) Add/sync participants to a campaign via the API or Zapier (and attribute referrers)
- B) React to referral-milestone / conversion / reward webhooks to fulfill rewards
- C) Pick + set up a campaign type — referral, pre-launch waitlist, giveaway, milestone, ambassador
- D) Connect Viral Loops to a CRM/ESP so the referral list lives where you nurture
- E) Decide referral vs affiliate program (different tools/strategy)
- F) Fix a problem — referrals not crediting, fake/disposable signups, plan/participant limits
-
API or no-code? A code integration → REST API (publicToken) + webhooks. No endpoint to host → two-way 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... |
|---|
| Referral / waitlist / audience-growth strategy across tools (which tool, viral mechanics) | /sales-audience-growth {question} |
| Designing an affiliate program (commissions, recruiting) across tools | /sales-affiliate-program {question} |
| Email deliverability of referral/notification emails | /sales-deliverability {question} |
| Connecting Viral Loops to a CRM/ESP generically (iPaaS) | /sales-integration {question} |
When routing, give the exact command, e.g. "This is a strategy question — run: /sales-audience-growth viral waitlist mechanics to maximize referrals".
Step 3 — Viral Loops platform reference
Read references/platform-guide.md for the full reference — the campaign-template + module map (what's API vs widget vs UI-only), the participant-based pricing model, the participant/webhook data model with JSON shapes, and quick-start recipes (add a participant; react to milestone webhooks; push leads via Zapier).
Read references/viral-loops-api-reference.md for the integration surface — base , the auth, , the leaderboard/convert/reward endpoints, the webhook events (new participant / referral-count / converted / reward-redeemed), and the two-way Zapier triggers/actions. Note the docs are partly JS-rendered — the reference marks unconfirmed paths.
