Skip to content
tenantcraft
← The Studio
Power Automate · Insurance

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
make.powerautomate.com

Plays a quick run of the flow above. Nothing is sent.

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

  1. Start with When Power Apps calls a flow (V2) and define the inputs.
  2. Call it from the form’s OnSuccess, passing LastSubmit.ID. Try it from the HR staffing request app.
  3. 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

  1. Add a Switch on the route the form sent: A, B, C or D.
  2. In route B, a second switch on the type of change decides how senior the last approver is.
  3. 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

  1. Use Start and wait for an approval with a 30-day timeout.
  2. After each response, append date, role, name, outcome and comments to varHistory.
  3. 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

  1. Send an approval or rejection email from the same HTML template.
  2. Keep the HR recipient in one variable, so testing and go-live differ by one value.

02More builds

All builds →

(Your process)

Still running it on email?

Sneak peek

Document preview

100%

Loading the document…