Create and manage a funnel

Open Project → Sites → Add funnel. Choose Blank, Lead capture, Purchase, Webinar, Booking or VSL. Each template starts one ordered journey; reshape it later with Add step, duplicate, reorder, rename and remove. Every added or duplicated step has independent editable source. Standard draft pages build without paid AI generation; AI customization is a separate action. Publish separately.

Funnel settings own the name, URL prefix and shared fonts, colours, spacing, corners and buttons. Step settings contain resource bindings, transitions and optional style overrides. Reset to funnel styling removes local overrides. Existing custom pages keep their appearance until you explicitly choose a standard layout. Delete the whole funnel from Project → Sites.

Typed steps and progression

Landing, pre-lander and product detail pages use next-step buttons. Opt-in, registration and application steps advance after accepted form submission. Booking advances after confirmation. Application + booking reveals a calendar on the same page after the application is accepted, then advances after booking. Video steps support approved media; webinar templates do not host webinars or send campaigns. Completion pages have no automatic transition by default.

Use step settings for managed forms, calendars and external exits. Internal destinations remain linear; reordering reconnects them. Activate resources before publishing. Unknown business details remain unfinished draft content. Preparing page and retry states replace unavailable previews.

Checkout and verified payments

Checkout steps start with a mock checkout until an offer/provider is configured. Preview can simulate completion and advance to the next step. Unconfigured live checkout cannot accept payment or advance. Connect an offer in Commerce; live payment progression requires server-verified payment. A thank-you visit or browser callback is never proof of payment. Add a One-click upsell step after Stripe checkout for an optional additional purchase. Bind a fixed-price, one-time Stripe offer in Commerce. The initial card checkout discloses and saves the payment method for upgrades the buyer explicitly accepts; existing checkouts without a reusable card are ineligible. Buyers see the additional amount, can decline, and complete any bank-required authentication before advancement. Accept and decline both follow the next configured step. Preview is simulated and takes no payment. Whop, Shopify, subscriptions and Payment Links are not supported for one-click upsells.

Agent workflow

Read get_funnels, then use edit_funnel_step with a requestId and current revisionId for atomic add, duplicate, type replacement, reorder, remove, settings and retry operations. The model uses the same type/template catalogue and edit logic. Saves reject stale revisions and conflicting active builds. The temporary funnels array contains exactly one journey per funnel child. Legacy multi-journey records require reconciliation rather than automatic merging. Draft and published revisions stay separate.