> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/recipes.md). # Recipes **Recipes are pre-built templates for common Gleantap workflows.** Instead of building a re-engagement flow, a lead-capture form, or a sales pipeline from scratch, you install a recipe and Gleantap deploys a working version — with segments, messaging, and stages already configured — into your workroom. Recipes are built and maintained by Gleantap. Every account has access to the same global library, filtered to what's relevant for your industry. *** ## What a Recipe is A recipe is a bundled template that includes: * **The underlying structure** — a Flow, Form, or Pipeline configuration * **Pre-built segments** — the audience the recipe targets * **AI-personalized messaging** — email and SMS content adapted to your business context * **Stages and triggers** — for pipelines, the sales-progression steps; for flows, the send timing and unenroll logic Recipes come in three types: | Type | What gets deployed | | -------------------- | ------------------------------------------------------------------------------------------------------- | | **Flow recipes** | A multi-step automation with segments, delays, actions, and unenroll criteria | | **Form recipes** | A ready-to-use form (typically lead-capture or booking) with field configuration and follow-up settings | | **Pipeline recipes** | A sales pipeline with stages, entry criteria, and automations | *** ## Browsing recipes Recipes live under the **Recipes** tab, accessible during workroom setup and from the main navigation. Recipes are organized by: * **Type** — Flow, Form, or Pipeline * **Industry** — Fitness & Wellness, Beauty & Personal Care, E-commerce, Education, and more * **Use case** — Onboarding, Re-engagement, Retention, Lead Capture, etc. Filter by the combination that matches what you're trying to accomplish. Each recipe card shows: * Title and short description * Type and use case tags * **When to use** — a note on the ideal scenario * **Install Recipe** button *** ## Installing a recipe Installation is one click. **Step 1** — On the recipe card, click **Install Recipe**. **Step 2** — Gleantap starts a background job that: 1. Fetches the recipe template. 2. Generates AI-personalized content (segments, messaging, stages) based on your business context. 3. Clones the recipe into your workroom's native Flow / Form / Pipeline tables. 4. Marks the recipe as installed for your workroom to prevent accidental duplicates. **Step 3** — Once installation completes (typically under a minute), you'll see the new Flow / Form / Pipeline in the relevant section of your workroom, ready to review and activate. **If you install the same recipe twice**, Gleantap shows a confirmation modal to prevent a duplicate. You can choose to install again (creating a second copy) or cancel. *** ## Customizing a deployed recipe Once installed, the recipe becomes a **regular Flow, Form, or Pipeline** in your account. You edit it the same way you'd edit anything you built from scratch: * **Flows** — open the flow builder, adjust steps, timings, unenroll criteria. See Creating a Flow. * **Forms** — open the form editor, adjust fields, design, tracking codes. See Creating a Form and Customizing Design. * **Pipelines** — open the pipeline configuration, edit stages and automations. See Pipeline Overview. The `recipe_id` link back to the original template is preserved, but your edits don't affect the source recipe — and future recipe updates from Gleantap don't overwrite your customizations. **Recommended workflow:** install, review the deployed configuration before enabling, adjust messaging to match your brand voice, then activate. Don't just install and turn on without reading through. *** ## Common questions ### "Can I create my own recipes and share them with other Gleantap accounts?" Not today. Recipes are built and shipped by Gleantap. If you have a workflow that would make a great recipe, share it with your Customer Success contact — successful patterns from customer accounts often become new recipes in the global library. ### "Will installing a recipe affect my existing flows / forms / pipelines?" No. Installing a recipe adds a new item — it never modifies or replaces something you already built. If you already have a Flow named similarly, the recipe creates a separate flow with its own identifier. ### "The recipe is close to what I want but not exact — should I customize the recipe or build from scratch?" Almost always customize the installed recipe. You save time on the structural setup (segments, triggers, stage progression), and you can adjust the messaging and specific criteria to match your business. Building from scratch is only worth it when your process is genuinely unique. ### "Where do I see which recipes I've already installed?" Recipes you've installed show an "Installed" state on the recipe card. In addition, the resulting Flow / Form / Pipeline appears in its normal location (**Flows**, **Forms & Pages**, or **Sales Pipeline**) — the recipe origin is tracked on the item's metadata. ### "The AI generated messaging in the deployed recipe doesn't sound like our brand — can I regenerate?" The messaging is a starting point, not final copy. Open the deployed Flow / Form / Pipeline and edit the messages directly. For campaign copy help, use Creative Playground (AI) with your brand voice specified in the prompt. ### "How often does Gleantap release new recipes?" New recipes are added periodically based on customer patterns and product releases. When we release a recipe relevant to your industry, it appears in your Recipes tab automatically. ### "Can I filter to only Fitness & Wellness recipes?" Yes — use the industry filter on the Recipes page. You can also stack filters (industry + type + use case) to narrow to exactly what you need. *** ## When to use a recipe vs. build from scratch **Use a recipe when:** * You're starting a new automation and don't have a specific structure in mind. * You want proven best practices baked in (e.g., timing between messages, unenroll criteria). * Speed matters more than perfect fit — recipes give you 80% for 10% of the effort. **Build from scratch when:** * Your process is genuinely unique to your business. * You have specific requirements that don't map to a common pattern. * You want full control from the first step. You can always start with a recipe and modify heavily — that's a valid third path and often the fastest way to a great result. *** ## Related pages * Flows → Creating a Flow — building flows from scratch * Forms → Creating a Form — building forms from scratch * Pipeline Overview — pipeline basics * Popular Use Cases — non-recipe use case ideas * Creative Playground (AI) — refining messaging in recipes --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.gleantap.com/recipes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.