| name | sales-landingi |
| description | Landingi platform help — AI landing page builder (landingi.com): Lunar AI page generator, drag-and-drop Visual Builder, 400+ templates, form builder, A/B testing, EventTracker, Smart Sections, Dynamic Text Replacement (DTR), multi-language pages, programmatic landing pages, lead capture, and the Orbit MCP server. Developer surface: REST API (api.landingi.com, X-Api-Key or OAuth 2.0 Bearer) for landing pages / leads / form submissions, per-form webhooks, a WordPress plugin, and 170+ Zapier integrations. Use when your Landingi page won't publish or a custom domain is stuck, A/B testing or programmatic pages are gated to a higher plan, AI credits run out, leads aren't syncing to your CRM or email tool, setting up a form webhook or the API to pull leads, wiring DTR so the page matches your ad keyword, or choosing Landingi Build vs Optimize vs Scale. Do NOT use for cross-tool funnel/CRO strategy (use /sales-funnel) or checkout-conversion across platforms (use /sales-checkout). |
| argument-hint | [describe what you need help with in Landingi] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","funnel","landing-pages","platform"] |
| github | https://github.com/landingi |
Landingi 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) Fix a broken page — won't publish, custom domain stuck/slow, page not showing
- B) Build/optimize a page — template, form, A/B test, EventTracker, Smart Sections, DTR
- C) Scale — programmatic landing pages from a feed, agency sub-accounts, multi-language
- D) Wire automation — pull leads via the API, set up a form webhook, sync leads to a CRM/ESP
- E) Use AI — Lunar page generator, Solis insights, the Orbit MCP server, AI credits
- F) Pick or compare a plan (Build / Optimize / Scale / Enterprise)
-
Which plan are you on? Build ($24/mo), Optimize ($119/mo), Scale ($229/mo+), Enterprise, or free trial. Several features below are plan-gated.
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
Step 2 — Route or answer directly
| Problem domain | Route to |
|---|
| Funnel strategy, page structure, conversion benchmarks across tools | /sales-funnel — Run: /sales-funnel {user's original question} |
| A/B testing methodology, heatmaps, statistical rigor | /sales-vwo — Run: /sales-vwo {user's original question} |
| Email sequences after lead capture | /sales-email-marketing — Run: /sales-email-marketing {user's original question} |
| Growing the list, lead-magnet strategy | /sales-audience-growth — Run: /sales-audience-growth {user's original question} |
| Generic CRM/ESP iPaaS wiring (Zapier/Make) | /sales-integration — Run: /sales-integration {user's original question} |
| Checkout/cart optimization beyond Landingi's built-in payments | /sales-checkout — Run: /sales-checkout {user's original question} |
If the question is Landingi-specific, continue to Step 3.
Step 3 — Landingi platform reference
Read references/platform-guide.md for the full platform reference — modules, pricing/plan gates, data model, integration recipes, code examples. For raw endpoint/auth/webhook detail, read .
