Six Gravity Flow workflows where one step sends each entry down one of several paths: expense approval by amount tier, grant decisions, HR leave requests, vendor onboarding, content approval with a legal branch, and support escalation. Each one starts with a single Multi-Path Decision step from GravityOps Multi Path Step, followed by ordinary Gravity Flow approval and user input steps.
We built all six on this site and ran a test entry down every path, 27 in all, before writing this page. The tables below are the exact setup, so you can rebuild any of them in a few minutes.
How each workflow is put together
- The decision step comes first and is assigned to whoever makes the call.
- Each path is a button with its own label, status key and next step. A decision step takes 2 to 20 paths.
- The steps after it are standard Gravity Flow approval and user input steps. A rejection at any approval step ends the workflow.
- “Send it back” paths go to a user input step assigned to the form’s email field, with only the fields that need fixing editable. When it’s done, the entry returns to the decision step.
- A path that goes to “Workflow complete” ends the workflow, and the path’s status (Rejected, Declined, Resolved and so on) becomes the entry’s final status.
Expense approval by amount tier
Fields: Employee, Employee email, Amount (USD), Category, What it was for, Receipt link. Decision step: Manager review.
| Button | Goes to | Then |
|---|---|---|
| Approve: under $500 | Finance: pay it (approval) | Workflow complete |
| Needs director: $500 to $5,000 | Director approval | Approved: Finance: pay it |
| Needs CFO: over $5,000 | CFO approval | Approved: Finance: pay it |
| Ask for the receipt | Employee adds the receipt (user input, assigned to the Employee email field; Receipt link editable) | Back to Manager review |
| Reject | Workflow complete | Final status: Rejected |
The manager picks the tier; the step doesn’t read the amount. If you’d rather route by amount with no click at all, put conditions on the approval steps instead. The decision step is for when a person makes the call.
Grant decisions
Fields: Organization, Contact email, Amount requested (USD), Program area, Project summary. Decision step: Committee decision.
| Button | Goes to | Then |
|---|---|---|
| Fund in full | Prepare award letter (approval) | Workflow complete |
| Fund in part | Prepare award letter (approval) | Workflow complete |
| Revise and resubmit | Applicant revises (user input, assigned to the Contact email field; Amount requested and Project summary editable) | Back to Committee decision |
| Decline | Workflow complete | Final status: Declined |
| Defer to next cycle | Workflow complete | Final status: Deferred |
Two paths can share a destination. Fund in full and Fund in part both go to the award letter, but the entry keeps which one the committee chose.
HR leave requests by type
Fields: Employee, Employee email, Leave type, First day, Last day, Notes. Decision step: HR review.
| Button | Goes to | Then |
|---|---|---|
| Approve | Manager sign-off (approval) | Workflow complete |
| Send to benefits (parental or medical) | Benefits team (approval) | Workflow complete |
| Unpaid: send to payroll | Payroll adjustment (approval) | Workflow complete |
| Need more detail | Employee adds detail (user input, assigned to the Employee email field; Notes editable) | Back to HR review |
| Decline | Workflow complete | Final status: Declined |
Vendor onboarding
Fields: Vendor name, Vendor contact email, What they will provide, Expected yearly spend (USD), Will they handle our customer data? Decision step: Procurement review.
| Button | Goes to | Then |
|---|---|---|
| Standard vendor | Finance: set up vendor (approval) | Workflow complete |
| Needs security review | IT security review (approval) | Approved: Finance: set up vendor |
| Needs a contract | Legal: contract (approval) | Approved: Finance: set up vendor |
| Reject | Workflow complete | Final status: Rejected |
Content approval with a legal branch
Fields: Title, Author email, Draft link, Makes claims about results, pricing or competitors?, Notes for the editor. Decision step: Editor review.
| Button | Goes to | Then |
|---|---|---|
| Approve | Schedule publishing (approval) | Workflow complete |
| Send to legal | Legal review (approval) | Approved: Schedule publishing |
| Back to author | Author revisions (user input, assigned to the Author email field; Draft link and Notes editable) | Back to Editor review |
| Reject | Workflow complete | Final status: Rejected |
Support escalation tiers
Fields: Customer, Customer email, Plan, Severity, Issue. Decision step: Tier 1 triage.
| Button | Goes to | Then |
|---|---|---|
| Resolved | Workflow complete | Final status: Resolved |
| Escalate to Tier 2 | Tier 2 support (approval) | Workflow complete |
| Escalate to engineering | Engineering (approval) | Workflow complete |
| Billing or refund | Billing (approval) | Workflow complete |
How we tested them
On 18 November 2026, on brightleafdigital.io, a builder script created each form and its steps with invented sample data. For every path it submitted one entry through Gravity Forms’ own submission API, checked that the workflow started on the decision step, chose that path the way the assignee would, and recorded which step the entry landed on. All 27 paths landed where the tables say.
What we didn’t test: the steps after the first hop. Approving at Director approval and landing on Finance, for example, is standard Gravity Flow routing, so we set it up as shown but didn’t run it for every chain.
Before you use one
- Assignees: the demos assign every approval and decision step to the Administrator role. Change them to your own users, roles or fields.
- Emails: every step email is off in the demos, and the forms have no notifications. Turn on the assignee email on each step so people know an entry is waiting.
- Requirements: Gravity Forms, Gravity Flow and Multi Path Step.
- Options on the decision step: an optional confirmation prompt before a decision is submitted, and a workflow note that can be hidden, optional or required. Each path also appears as a quick action in the Gravity Flow inbox.
Download the workflows
One step after you import: open the Multi-Path Decision step in each imported workflow and, under Decision Paths, choose the Next Step for every path again, then save. A path set to Workflow Complete or Next step in list imports as it is, but a path that points at a named step still carries that step’s ID from our site, so until you re-pick it the entry won’t go where the table above says.
Each file is a Gravity Forms form export that carries its Gravity Flow steps. Import it under Forms → Import/Export.
| Workflow | File |
|---|---|
| Expense approval by amount tier | expense-approval-by-amount-tier.json |
| Grant decisions | grant-decisions.json |
| HR leave requests by type | hr-leave-requests-by-type.json |
| Vendor onboarding | vendor-onboarding.json |
| Content approval with a legal branch | content-approval-with-a-legal-branch.json |
| Support escalation tiers | support-escalation-tiers.json |
See any workflow as a diagram
Load a form export into the free Gravity Flow workflow diagram generator to get a flowchart you can share with a client, with Multi-Path branches and their labels drawn in.
Try Multi Path Step
Multi Path Step adds the Multi-Path Decision step to Gravity Flow. From $74.99 a year for one site, with a 14-day free trial (no card) and a 30-day refund guarantee.