Build your first Inflow application
Follow Nadia as she builds Leave requests for People Operations. Mohammad submits a request; Sara reviews it. You will build the data, forms, application pages and approval process that connect their work.
For the available screenshot examples, their capture-build note and captions, open the illustrated learning path. It distinguishes represented states from pages that still have partial screenshot coverage.
See the participant experience: the worked whole-day pilot follows an ordinary employee’s request through an assigned manager’s saved answer and actual completion. Five numbered guides include the untouched full-size screenshots. This example starts with prepared application access and a supplied task link; it does not demonstrate the entire worklist setup or a leave-record update.
Use a training workspace and fictional information. Ask your administrator to prepare ordinary employee and manager accounts and any connections needed by the optional lessons. You do not need to program the application server to follow the core journey.
Follow the story in this order
Some lessons deliberately pause while you build the next part. Follow the stages below rather than completing each linked lesson from top to bottom on your first visit.
| Stage | What you do | What you should have afterward |
|---|---|---|
| 1 | Prepare the people and workspace, stages 1–4 | People Operations, Nadia's builder access and ordinary accounts for Mohammad and Sara. |
| 2 | Build leave data and rules | A published, live data model, fictional leave records and a rule that finds requests. |
| 3 | Build forms and the App Shell, milestones 1–7 | An employee request form, a separate manager decision form and an application shell. |
| 4 | Build the approval workflow, milestones 1–4 | A published approval process with the correct manager assignment and decision form. |
| 5 | Return to forms and the App Shell, milestones 8–9 | A way to start the process and a manager page that selects and opens an assigned task. |
| 6 | Return to people and access, stage 6 | Reviewed application access for Employees and Managers. |
| 7 | Return to the approval workflow, milestones 5–8 | Mohammad starts a request; Sara opens the task, chooses a decision and submits it. |
| 8 | Finish interface milestone 10 and identity stage 7 | Checks that each person sees and can do the intended work. |
Keep three things separate: a record stores the business information, a case follows one request through the process, and a task asks someone to do a piece of work. Completing Sara's task changes the process. Updating a business record requires the update step you deliberately configure. The identity-stage review after the workflow reuses completed outcomes; it does not repeat the create or manager decision. My review tasks lists open work assigned to the signed-in person, so a completed task is not expected to remain there.
The sample records include leave-2026-014, Mohammad's pending request. The later create-record exercise uses leave-2026-017 so that you do not try to create the same request twice. Names and sample employee numbers are business examples; use the actual accounts you prepared when assigning work.
Add more to the application
| Lesson | What you learn | Prepare first |
|---|---|---|
| Build a query-driven page | Filter requests and show the results in an application page. | The leave model, sample records and query rule. |
| Add a document workflow | Upload a document, attach it to work and create a PDF where conversion is available. | An allowed training folder and the required document service. |
| Connect another system | Look up an employee and make a reviewed operation available to another application. | A connection and test destination approved by the owner. |
| Add an AI summary | Let a person request and review a summary without giving AI the approval decision. | An approved AI provider and permission to send the chosen test information. |
| Add App Chat to the published app | Give employees and managers an in-app conversation over publisher-connected guidance, records and their own available tasks. The person's normal row, field and task access still applies; an offered task action requires review and confirmation. | A published App Shell, connected sources, approved operations, an approved AI provider for live answers and the intended users' ordinary application access. |
| Prepare a release and hand over the application | Identify the signed release, inspect the exact target route and either verify supported delivery or record it as pending. | A published application and an administrator-prepared target environment. |
The illustrated Connection → Rules → Forms walkthrough offers another example. Its 17 images now have numbered focus marks and short matching legends; each image links to its unchanged source. Legacy QA captures and illustrative mockups are labeled separately and are not current-build screenshot evidence. Use the current navigation, connection publication steps and per-entry CRUD function-pack status described in the lesson and current manuals.
When you need help
Each lesson explains what to prepare, what to click, what result to expect and what to check when the result differs. Start with the consultant guide index for a particular topic or the Interface Builder handbook for forms and pages.
The optional technical reference library keeps programming and platform details separate. These written lessons were checked against the source; they do not mean that your environment or a particular user journey has already been tested. Check the real application with the intended users before handing it over.