Recipes & patterns (App Connect Flows)
Common App Connect Flows patterns: Inline Flow for quick UI glue, Page Flow for in-page orchestration, App Flow for reusable workflows with outputs.
App Connect Flows: recipes & patterns
Section titled “App Connect Flows: recipes & patterns”This how-to collection is meant to lower the entry cost for App Flows by starting from repeatable tasks instead of abstract theory. Use it to find the exact workflow you need, understand where that action lives in the editor, and then branch into the focused tour that matches your next step.
Pattern: React to UI events
Section titled “Pattern: React to UI events”Start from a user action (click, submit, change) and run follow-up steps.
Use Inline Flow for a short sequence. Use Page Flow when it becomes multi-step with branching. Use App Flow when you want reuse + results.
Pattern: Branch logic cleanly
Section titled “Pattern: Branch logic cleanly”Use conditions to branch and run different steps based on values, responses, or UI state.
Treat errors as a branch (happy path vs error path), and keep results/status explicit so your UI can react.
Pattern: Integrate data safely
Section titled “Pattern: Integrate data safely”Combine flows with data sources/actions (like API calls) to load, transform, and use data.
Rule of thumb: if it must be secure or touch the database, call a Server Connect Action, then use the response in your Page Flow / App Flow.
Pattern: Organize and reuse
Section titled “Pattern: Organize and reuse”Keep large projects manageable.
Inline Flow stays small and local. Page Flow keeps per-page orchestration readable. App Flow splits complex tasks into reusable flows and returns results.
Next steps
Section titled “Next steps”Pick what you want to learn next.