Expense approval flow
Harbor Works' finance coordinator needs a recoverable expense decision record.
The event supplies reference, manager, requester and an explicit approval response. The Expenses list already holds the request. Create and await the approval, notify its requester, set only the matching item's status, post a team audit and save the decision file.
Harbor Works records each expense request before a manager decides it. Your flow must create an assigned approval, wait for a response, notify the requester and update the original list item. Approval creation alone must never mark an expense approved.
The two fixture requests take different paths. One is approved; one is rejected and has a known zero quantity. Preserve that existing quantity while updating Status. Each stage keeps its earlier actions, and the final audit record combines the reference with the observed response. Review the run history from creation through update before checking the last step. A useful handoff makes it possible to answer both questions: who decided this request, and which tracking item changed? The exercise uses fictional local effects throughout.
Cloud flow: Expense approval flow
Trigger: When an item is created
list: Expenses
Create an approval [approval]
Title: @concat('Expense ', triggerBody()?['reference'])
Assigned to: @triggerBody()?['manager']
Assignment and request identity come from the event.