Tips to Create Workflows in 15 minutes-1

How to Create an Approval Workflow

Sreenidhe SP Head of Content

Updated on 7 Nov 2026 • 9 min read

To create an approval workflow, define the trigger that starts each request, assign approvers, and choose an approval type (first to respond, everyone must approve, or sequential), then build it in a tool such as Microsoft Power Automate or Kissflow. Add a condition on the outcome so approved requests update their status and rejected ones return feedback. Notify the requester either way, and test with a sample request before you publish.

TL;DR

  • A trigger starts every approval workflow, such as a form submission, a new SharePoint item, or a button.
  • Approvers are assigned individually, by group, or in sequence, under one of three approval types.
  • Under “everyone must approve,” a single rejection rejects the request for every approver.
  • A condition on the outcome sends approved and rejected requests down separate branches that notify the requester.
  • Before you publish, test with sample requests, add exception rules, and decide where the audit trail lives.

An approval workflow is the fixed route a request follows from submission to a recorded decision. It sets who reviews the request, in what order, under which rule, and what happens after they decide. The request might be a purchase, a document, a contract, or an access change. Having a defined route is what separates an approval workflow from an email thread. For the broader concept, see Kissflow’s guide to approval workflows explained.

Here is what a missing route looks like in practice. A capital request for warehouse equipment arrives by email. Finance asks who else has signed it, and the requester forwards it again. The request itself is fine. What it lacks is a route. The six steps below hold in any tool, and two of them, exceptions and the audit trail, are easy to leave out.

The steps at a glance

  • Map the request: Decide what event triggers the workflow and what data the approver needs to see.
  • Choose approvers and approval type: Assign approvers by role, then pick the approval type that fits the decision.
  • Add outcome logic and notifications: Branch on the outcome so each result updates the status and tells the requester.
  • Handle exceptions: Decide in advance what happens when an approver is out, a deadline passes, or an amount changes.
  • Record the audit trail: Keep who approved what, and when, somewhere that outlasts the request.
  • Test and publish: Run sample requests through every branch before real ones arrive.

Step 1: Map the request and its trigger

Name the trigger first, because it settles half the design. Common triggers are a form submission, a new item in a SharePoint list or library, a file upload, and a button someone presses to start the flow by hand.

Write down three things before you open any tool:

  • The trigger event, and the system where it happens.
  • The fields an approver needs to decide without chasing the requester, such as amount, cost center, justification, and an attached quote.
  • The status values the request will pass through. A choice column with New, Submitted, Approved, and Rejected covers most processes.

The second item decides how fast approvers move. A request that shows everything on one screen gets decided. A request that makes the approver open an attachment, check a spreadsheet, and ask a colleague gets parked for later.

If that data lives in another system, plan the connection now. Kissflow’s notes on workflow integration tools and tips walk through the options.

Step 2: Choose approvers and an approval type

Assign approvers by role. A “finance director” step keeps working after a resignation, but a step assigned to one named person breaks when that person leaves. You can assign a single person, a group, or a chain of approvers in sequence. The approval type then decides how their responses combine:

  • First to respond: whichever assigned approver acts first settles the request.
  • Everyone must approve: every assigned approver has to approve, and one rejection rejects the request for all of them.
  • Sequential: approvers receive the request one at a time in a set order, and step two starts only after step one approves.

Thresholds belong in this step too. As an illustrative example, a capital request under US$25,000 could need only the department head. Anything above $25,000 would add the CFO as a sequential second approver.

Take the threshold from the spending policy your finance team already publishes. Do not invent a new one inside the tool, or the workflow and the policy will disagree on the first contested request.

Step 3: Add outcome logic and notifications

If nothing happens after the approval step, nobody hears about the decision. Add a condition on the outcome, then give each result its own actions:

If approved If rejected
Update the status column to Approved. Update the status column to Rejected.
Notify the requester by email, Microsoft Teams, or a mobile notice. Notify the requester and include the approver’s comments.
Hand the request to whoever acts next, such as purchasing. Return the request for revision, or close it if the policy allows no resubmission.

One optional step pays off on day one. Set the status to Submitted or Under Review the moment the trigger fires. Anyone checking the list then sees the request is moving and does not need to ask the requester.

Make the comment field required on rejection. A rejection without a reason produces a resubmission with the same gap, and the approver has to reject it twice.

Step 4: Handle exceptions before they happen

Approval workflows rarely break on the request they were designed for. They break on the approver who is on leave, the deadline nobody is watching, and the amount that changes after submission. Write the rules for those cases before launch:

  • Unavailable approver: Name a delegate for every approver role, and switch to the delegate when the approver is out of office.
  • Missed deadline: Send an automatic reminder after a set interval, then escalate to the approver’s manager if the request is still waiting.
  • Changed amount: When a revised amount crosses a threshold, route the request back through the path that matches the new figure.
  • Changed reviewers: When a role changes hands, update the approver list before open requests stall against someone who has moved on. Every exception rule adds a branch. Each new branch is one more path you have to test in Step 6.

Atlassian’s guidance on approval processes makes the same case. It recommends clear criteria for each stage, automatic reminders, and a simple escalation process.

Step 5: Record the audit trail

Months after a request closes, an auditor will ask who approved it, when, and under which rule. For every decision, record the approver, the outcome, the timestamp, any comments, and the version of the rule that routed the request.

Where that record lives depends on the tool. Microsoft saves Power Automate approval flows in Dataverse, and many teams also add a step to the flow that writes each outcome to a SharePoint list or another log they control.

Settle where the evidence will sit on audit day before the first request runs. A compliance lead who knows the answer in advance spends audit day handing over records instead of rebuilding them.

Step 6: Test and publish

Run at least three sample requests before anyone submits a real one: one that is approved, one that is rejected, and one that triggers an exception from Step 4. For each, check that the status updates, the notification arrives, and the audit record shows the decision.

In Power Automate, select Test in the top right of the flow designer and run the flow manually against a sample item.

Publish only after every branch has run at least once.

How do you create an approval workflow in Power Automate?

Microsoft Power Automate runs approvals through a single action, “Approvals: Start and wait for an approval”, which you add to any flow. The six steps above map onto flow actions like this:

  • Create the flow. You can start from a template, such as the one that sends an approval when an item is created in a SharePoint list. Or build from scratch with an automated trigger, or with an instant cloud flow that you start manually. From inside a SharePoint list, Integrate, then Power Automate, then Create a flow opens the same builder.
  • Add the Start and wait for an approval action. In the Approval type list, choose First to respond, Everyone must approve, or Sequential approval.
  • Enter the title, the assigned approvers, and the details the approver will see.
  • Add a Condition on the approval’s Outcome. In each branch, update the status column and add a Send an email (V2) action addressed to the requester.
  • Save the flow, select Test, and run it with a sample item.

Setup requires a Power Automate license, a Microsoft Dataverse database, a data source such as a SharePoint list with a status column, and someone to maintain the flow when approvers or rules change.

For one-off requests with no list behind them, the Approvals app in Microsoft Teams works without a flow. Open the app, select New approval request, add the details and approvers, set the order, and send.

How do you build an approval workflow in Kissflow?

Kissflow is an AI-powered enterprise application platform, driven by business logic, not code, where business teams and IT build, automate, and govern their core work. An approval workflow in Kissflow follows the same six steps, organized around a form:

  • Start with a form that holds the request data. It can be as simple as an attached PDF or as detailed as a line-item table that calculates the total.
  • Add the approval steps, starting with a single approver if that is all the process needs. The task owner is notified, reviews the data, and approves or rejects.
  • Bring in more stakeholders and conditions. For example, route each requester to their own manager, or add a senior approver only above a set dollar amount.

Kissflow’s guide to creating a workflow online from scratch shows the build in more detail.

Kissflow handles the structured work that falls at the edges of what the core systems were built to do, such as an approval whose supporting evidence sits in Salesforce while its budget check sits in Oracle. It works around SAP, Oracle, Salesforce, and Workday and never replaces them. Audit logs timestamp and attribute every action, so the record exists without a separate logging step.

  • Customers: Founded in 2012, Kissflow serves over 1,200 customers worldwide.
  • Production examples: New store opening and retail lifecycle management, oil rig shutdown and turnaround management, and end-to-end procurement and financial consoles.
  • Certifications: SOC 1 Type II, SOC 2 Type II, SOC 3, ISO/IEC 27001, HIPAA, GDPR, and CCPA.
  • Hosting: Google Cloud Platform (primary) and AWS (secondary).
  • Data residency: US, EU, APAC, and Oceania.
  • Uptime: A 99 percent uptime SLA.

Kissflow uses subscription-based, user-tier pricing. Users are grouped into blocks by level of platform interaction, such as builders versus occasional approvers. Integrations, APIs, and AI features are included in the subscription at no extra cost. Enterprise customers can access volume-based pricing and multi-year agreements, with three-year contracts typical. Implementation, consulting, and support are scoped separately, delivered directly or through partners.

Which tool should you use to create an approval workflow?

If a request starts, routes, and ends inside one system, use that system’s own approval feature. An approval that lives entirely on a Salesforce record belongs in Salesforce’s approval process. When an approval pulls evidence from one system, budget from another, and sign-off from people who use neither, it needs a governed approval layer. Those are the requests that otherwise end up back on email and spreadsheets.

Tool Where the request starts Approval step What setup requires
Microsoft Power Automate A trigger such as a new SharePoint item, a file upload, or a manual button Approvals: Start and wait for an approval, with an approval type A flow, a data source with a status column, and someone to maintain the flow
Microsoft Teams Approvals The Approvals app in Microsoft Teams New approval request, with approvers and order A Microsoft 365 account with Teams, and no flow to build
Salesforce A record submitted for approval An approval process created with the Standard Setup Wizard Setup access to define the process for that record type
Jira A work item in a workflow status An approval step added to that status in the workflow editor An approver field on the work item, and a Premium or Enterprise plan for business spaces
Smartsheet A row that meets set criteria The “Request an approval when specified criteria are met” template A sheet with the criteria columns and an automation built from the template
Jotform A form submission The Workflow Builder, with an Approval element A Jotform form to attach the workflow to
Kissflow A form submission Approval steps with conditions inside the workflow A form and the workflow steps

If your approvals run on SharePoint today and you are weighing other routes, Kissflow’s page on alternatives to SharePoint approval workflows sets out the trade-offs.

What to decide before you start

Every tool asks the same questions during setup. Answering them on paper first can turn a week of rebuilds into a single build.

  • What event triggers the request, and in which system does it happen?
  • Which roles approve, and does a single approver, a group, or a sequence decide?
  • Which of the three approval types in Step 2 applies?
  • What dollar thresholds change the route, and which written policy sets them?
  • What does a rejection send back, and can the requester resubmit?
  • Who covers for an absent approver, and when does a waiting request escalate?
  • Where will the record of each decision live after the request closes?

Frequently asked questions

What is a document workflow approval?

A document approval workflow is an approval workflow where the request being decided is a document, such as a contract or a file sent for sign-off. A trigger such as a file upload or a new item in a SharePoint library starts it. The document goes to assigned approvers, and the outcome updates a status and notifies the requester.

How to easily create workflows?

The easiest way to create a workflow is to settle the design on paper first and then build it in any tool. Name the trigger, assign approvers by role, choose an approval type, add approved and rejected branches with notifications, and test with a sample request before publishing. The same steps apply when you develop or create a new workflow in any tool. Starting from a template, such as one that sends an approval when a SharePoint list item is created, shortens the build.

How to trigger an approval process from flow?

A flow needs a trigger before its approval step can run. Use an automated trigger, such as a new item in a SharePoint list, or an instant cloud flow that someone starts manually. Then add the “Approvals: Start and wait for an approval” action after the trigger.

The route matters more than the tool

Every capable tool can send a request to an approver and branch on the answer. That part is settled. Workflows succeed or fail on the decisions made before the build: who approves by role, which threshold triggers which path, what happens when the approver is away, and where the record sits a year later.

Teams that skip those decisions end up building the same workflow twice, once for the happy path and again after the first audit. Teams that write them down build it once.

Start with your single highest-volume request, and answer the seven questions in the “What to decide before you start” checklist for it.

Build your first approval workflow with AI Builder and see every change land in one audit log.