Staffing request approvals
Who has to approve a new hire depends on the request. Some need two sign-offs, some need four, and moving a position to another department goes all the way to the CEO. One flow handles every route and records each decision on the request.
- ToolPower Automate cloud flow
- Triggercalled from the staffing request form
- Routesfour, with up to four approvers each
- 01 Request comes in from the app
- 02 Saved and marked Submitted
- 03 Finance Business Partner approves
- 04 Hiring manager approves
- 05 Division Director approves
- 06 Vice-President approves
- 07 Marked Completed, history saved
Done in 7 steps: four approvals, each one logged on the request, and the requester emailed.
You’ve got mail
- From
- HR Staffing <no-reply@algonquinmutual.ca>
- To
- Nora Bennett <nora.bennett@algonquinmutual.ca>
- Subject
- HR Staffing Request - Approved - Senior Claims Adjuster
A working replica of a real Power Automate build, redone in HTML and JavaScript so you can click through it here. Algonquin Mutual Insurance is fictional; all names, people and numbers are illustrative. Open it full screen.
Want help building yours? hello@tenantcraft.ca
01How it works
Every build here sticks to standard connectors like SharePoint, Outlook and Approvals, so it runs on the Microsoft 365 licences you already pay for.
01 Called by the form
The form sends the item ID, the route and the approvers’ emails when someone submits a new request.
How to build it
- Start with When Power Apps calls a flow (V2) and define the inputs.
- Call it from the form’s
OnSuccess, passingLastSubmit.ID. Try it from the HR staffing request app. - Read the item back with Get item, so the list stays the source of truth.
02 A route for each kind of request
A switch picks the route. Routes ask for between one and four approvals, one after another.
How to build it
- Add a Switch on the route the form sent: A, B, C or D.
- In route B, a second switch on the type of change decides how senior the last approver is.
- End with Terminate on an unknown route, so a bad input can’t fail quietly.
03 Approvals with a paper trail
Every decision updates the status column and adds a dated line to a history column.
How to build it
- Use Start and wait for an approval with a 30-day timeout.
- After each response, append date, role, name, outcome and comments to
varHistory. - Write status and history back to the item with Update item.
04 Emails at the end
The requester hears the outcome either way. On approval, HR gets a “ready to post” email too.
How to build it
- Send an approval or rejection email from the same HTML template.
- Keep the HR recipient in one variable, so testing and go-live differ by one value.
02More builds
- Power AppsInterview request appA four-step canvas app that collects the interview panel, locations, time slots and candidates, and checks each step before the request can go in.Power Apps · Grocery retail
- Power AutomateInterview status emailsOne flow that watches the interview request list and sends the right email for each status, in place of two old SharePoint Designer workflows.Power Automate · Grocery retail
- Power AppsHR staffing requestA checklist, then a stepped request form. The approval scenario decides who signs off, and submitting starts the staffing approvals flow.Power Apps · Insurance
- Power AppsContractor insurance questionnaireProject managers answer 21 yes-or-no questions about a job and get the insurance clauses for the contract, ready to paste.Power Apps · K-12 education
- Power AutomatePosition number alertA small flow that tells position control when a new staffing request needs a position number created or changed.Power Automate · Insurance
- Power AutomateBudget adjustment approvalPick a budget file in the library, send it for approval, and the flow stamps the outcome on the file and emails the finance leads.Power Automate · Financial services