Workflows
Recipes for real outcomes.
Use workflows when the job is bigger than a feature page: choose the offer, connect the integration, route the purchase event, and ship the handoff after checkout.
Builder paths
Start with the workflow shape.
A workflow page should help a builder choose the business path before opening API docs, SDK checkout, webhooks, integrations, stacks, sequences, or comparison pages.
Fan events into a custom stack
Use this when an app, backend, or agent-built workflow needs API keys, SDK checkout, webhooks, customer identity, metadata, and invoice context.
Recipe library
Pick the job, then follow the links into the stack.
Every workflow should connect to the product, platform, sequence, template, stack, docs, or comparison page that helps a builder continue.
beginner
Sell a Webflow product with Stripe Checkout
Wire a Plandalf hosted checkout into a Webflow site, accept Stripe payments, and fulfill on completion. A working Webflow → Plandalf → Stripe purchase flow with automated fulfillment.Product surfaces
Real app surfaces behind the recipes.
The recipes link back to the Plandalf screens that make the workflow inspectable: offer setup, buying moments, integrations, and automation.
Reference paths
Where recipes should send builders next.
Workflow pages should be practical entry points into Offers, Timers, Automations, integrations, docs, stacks, templates, and comparisons.