Templates
Start new flows from pre-built templates.
Templates
Templates are pre-configured flow starting points that save you from building common patterns from scratch. Setgreet includes a built-in template library with professionally designed templates you can use as a starting point.
Choosing a template
When you click Create Flow from the Flows page, you are taken to the template selection screen. All available templates are displayed as phone-sized previews showing how the flow will look on a device.
Click a template to create a new flow from it. Setgreet generates the flow with all the template's screens, components, and graph structure pre-populated, and opens it directly in the flow builder.
The new flow is automatically named (e.g., "Flow 1", "Flow 2"). You can rename it by clicking the flow name in the top bar of the editor.
The new flow is independent of the template. Changes you make do not affect the original template, and template updates do not retroactively change flows you have already created.
What a template includes
A template defines the following:
| Element | Description |
|---|---|
| Screens | One or more screens with pre-arranged component trees. |
| Components | Configured component instances with default text, colors, sizing, and layout. |
| Background | Screen background color. |
| Presentation style | Fullscreen or bottom sheet, including bottom sheet configuration. |
| Flow graph | The node-and-edge structure connecting the screens. |
Templates do not include:
- Trigger conditions (you configure these for your specific audience).
- App assignment (the app is selected when publishing).
- Localization content (you add translations after creating the flow).
Customizing after creation
After creating a flow from a template, treat it like any other flow. Common first steps:
- Update copy -- replace placeholder text with your own messaging.
- Adjust branding -- match colors, fonts, and images to your app's design system.
- Configure triggers -- set trigger conditions to target the right audience.
- Add or remove screens -- templates are a starting point, not a constraint. Add extra screens or remove ones you do not need.
- Set up branching -- if the template includes branchable components, configure Branch nodes to create personalized paths.
Tips
- Start with a template, then iterate -- even if no template perfectly matches your use case, starting from the closest one is faster than building from scratch.
- Preview before publishing -- after customizing a template-based flow, always preview it to verify the experience.