Laravel Flow Showcase

Discover real-world examples and use cases of Laravel Flow in action. See how different businesses leverage workflow management to streamline their processes and automate complex business logic.

Understanding Workflow Components

Each workflow in Laravel Flow consists of:

• States: Represent different stages in your process. Each state has a type:

  • Start (Initial): Entry point of the workflow
  • Middle (Intermediate): States between start and end
  • End (Terminal): Final states where the workflow completes

• Transitions: Define how work moves between states. Each transition can execute three types of tasks:

  • Restriction Tasks: Check if the transition is allowed (permissions, conditions)
  • Validation Tasks: Validate data before transitioning
  • Action Tasks: Execute actions when transitioning (notifications, updates, etc.)

E-Commerce Order Processing

Order Management System

Complete order lifecycle from placement to delivery

Overview

The E-Commerce Order Processing workflow manages the complete lifecycle of customer orders from the moment they are placed until final delivery or cancellation. This workflow ensures seamless coordination between payment processing, inventory management, fulfillment, and shipping operations. Each state transition triggers automated tasks that keep customers informed and maintain accurate inventory levels.

Key Features

• Automatic inventory updates
• Real-time customer notifications
• Payment verification and processing
• Shipping label generation
• Order cancellation handling

Business Benefits

• Reduced manual processing time
• Improved order accuracy
• Better customer experience
• Automated inventory management
• Real-time order tracking

Order Workflow

Start: PendingMiddle: Processing, ShippedEnd: Delivered, Cancelled

Orders begin in the Pending state when a customer places an order. They move to Processing once payment is confirmed, then to Shipped when items are prepared and dispatched. The workflow can end in either Delivered (successful completion) or Cancelled (if cancelled at any stage).

Transition Tasks

Each transition can have multiple tasks of each type (Restriction, Validation, Action), or none at all. Tasks are executed in order: Restriction → Validation → Action.

Transition	Restriction Tasks (Optional)	Validation Tasks (Optional)	Action Tasks (Optional)
Pending → Processing	Check payment status is completed Verify order is not already cancelled	Validate payment amount matches order total Validate payment method is valid	Update inventory levels Send order confirmation email to customer Create fulfillment task
Processing → Shipped	Check all items are available in inventory Verify shipping address is complete	Validate shipping address format Validate shipping method is available	Generate shipping label Send tracking number email to customer Update order tracking status
Shipped → Delivered	Verify delivery confirmation received	Validate delivery signature Validate delivery date	Send delivery confirmation email Update order status to delivered Request customer feedback
Pending → Cancelled	Check cancellation policy allows cancellation Verify cancellation time window	Validate cancellation reason is provided	Process refund payment Send cancellation confirmation email Update order status
Processing → Cancelled	Check system cancellation rules Verify cancellation is allowed at this stage	Validate cancellation reason Validate cancellation is authorized	Restore items to inventory Process refund payment Notify customer via email Update order status

Use Case: Automatically handle order status updates, send email notifications to customers at each stage, update inventory when orders are processed, trigger shipping label generation when orders are shipped, and send delivery confirmations.

Real-World Implementation:

This workflow is ideal for online stores, marketplaces, and e-commerce platforms. It ensures that every order is properly tracked, customers are kept informed at each stage, inventory is automatically updated, and shipping processes are streamlined. The cancellation paths allow for flexible order management while maintaining data integrity.

HR Leave Request Management

Employee Leave Request

Multi-level approval workflow for leave requests

Overview

The HR Leave Request Management workflow implements a hierarchical approval system where employee leave requests must pass through multiple levels of authorization. This ensures proper oversight, maintains leave balance accuracy, and automatically updates employee calendars. The workflow supports role-based access control, ensuring only authorized personnel can approve or reject requests at each stage.

Key Features

• Hierarchical approval routing
• Role-based access control
• Automatic leave balance deduction
• Calendar integration
• Multi-level notification system

Business Benefits

• Streamlined approval process
• Reduced administrative overhead
• Accurate leave tracking
• Improved compliance
• Better workforce planning

Approval Workflow

Start: SubmittedMiddle: TeamLeadReview, HRReviewEnd: Approved, Rejected

Employees submit leave requests which are automatically routed to their Team Lead for initial review. Upon Team Lead approval, requests proceed to HR for final authorization. Both Team Leads and HR can reject requests at their respective stages, with all parties notified of decisions.

Transition Tasks

Each transition can have multiple tasks of each type (Restriction, Validation, Action), or none at all. Tasks are executed in order: Restriction → Validation → Action.

Transition	Restriction Tasks (Optional)	Validation Tasks (Optional)	Action Tasks (Optional)
Submitted → TeamLeadReview	Auto-assign based on employee's team Check team lead availability	Validate leave dates are valid Validate leave balance is sufficient Validate no overlapping leave requests	Notify team lead Create review task
TeamLeadReview → HRReview	Check team lead role permission Verify approval authority	Validate approval reason is provided	Notify HR department Forward to HR queue Update review status
TeamLeadReview → Rejected	Check team lead rejection permission	Validate rejection reason is provided	Notify employee Log rejection in system
HRReview → Approved	Check HR role permission Verify final approval authority	Validate final approval conditions Validate all previous approvals	Update employee calendar Notify employee and team Deduct leave balance Create calendar event
HRReview → Rejected	Check HR rejection permission	Validate rejection reason	Notify employee Log final rejection

Use Case: Implement hierarchical approval workflows where leave requests must pass through multiple levels (Team Lead → HR → Final Decision) with role-based access control. Automatically notify relevant parties at each stage and update employee calendars upon approval.

Real-World Implementation:

Perfect for organizations with structured approval hierarchies. This workflow ensures that leave requests are properly vetted by immediate supervisors before reaching HR, maintaining operational continuity while providing necessary oversight. The automatic calendar updates and balance deductions eliminate manual data entry errors and ensure accurate leave records.

Financial Invoice Approval

Invoice Approval Process

Multi-stage financial approval with amount-based routing

Overview

The Financial Invoice Approval workflow implements intelligent routing based on invoice amounts, ensuring that high-value invoices receive appropriate levels of authorization. Small invoices ($1,000) require only manager approval, while larger invoices must pass through multiple approval stages including Finance and CFO review. This system maintains financial controls while streamlining the approval process for routine transactions.

Key Features

• Amount-based routing logic
• Multi-level approval chains
• Automatic journal entry creation
• Vendor notification system
• Payment processing integration

Business Benefits

• Enhanced financial controls
• Faster approval for small invoices
• Proper authorization for large expenses
• Automated accounting entries
• Improved vendor relationships

Dynamic Approval Routing

Start: Invoice CreatedMiddle: Manager Review, Finance Review, CFO ReviewEnd: Approved, Rejected, Payment Processing

Invoices are automatically routed based on their amount: Under $1,000 go directly to Manager for approval; $1,000-$10,000 require Manager and Finance approval; Over $10,000 must pass through Manager, Finance, and CFO. Once approved, invoices proceed to payment processing where funds are disbursed and accounting records are updated.

Transition Tasks

Each transition can have multiple tasks of each type (Restriction, Validation, Action), or none at all. Tasks are executed in order: Restriction → Validation → Action.

Transition	Restriction Tasks (Optional)	Validation Tasks (Optional)	Action Tasks (Optional)
Invoice Created → Manager Review	Check invoice amount threshold Verify invoice is not duplicate	Validate invoice data completeness Validate vendor information Validate invoice format	Assign to appropriate manager Send notification to manager
Manager Review → Finance Review	Check amount is greater than $1,000 Verify manager has approved	Validate manager signature Validate approval timestamp	Forward to finance department Notify finance team
Finance Review → CFO Review	Check amount is greater than $10,000 Verify finance has approved	Validate finance approval	Forward to CFO Notify CFO office
Manager/Finance/CFO → Approved	Check approver role permission Verify approval authority level	Validate approval signature Validate approval date	Create journal entry Notify vendor Update invoice status
Any Review → Rejected	Check rejection permission	Validate rejection reason is provided	Notify submitter Log rejection in system
Approved → Payment Processing	Check payment schedule Verify payment terms	Validate payment details Validate bank account information	Process payment Update accounting records Notify vendor of payment

Use Case: Implement dynamic approval routing based on invoice amount. Small invoices ($1,000) go directly to manager for approval. Medium invoices ($1,000-$10,000) require manager and finance approval. Large invoices ($10,000+) must pass through manager, finance, and CFO. Automatically create journal entries and notify vendors upon approval.

Real-World Implementation:

Ideal for companies with structured financial approval processes. This workflow ensures that routine small expenses are processed quickly while maintaining strict controls over significant expenditures. The automatic routing eliminates manual decision-making about who should approve each invoice, reducing processing time and ensuring compliance with financial policies.

Content Publishing Workflow

Content Publishing System

Editorial review, revision cycles, and scheduled publishing

Overview

The Content Publishing Workflow manages the complete lifecycle of content from initial draft creation through editorial review, revision cycles, and final publication. This workflow ensures content quality through structured review processes while supporting scheduled publishing and automated SEO optimization. Content can be revised multiple times based on editorial feedback before final approval and publication.

Key Features

• Editorial review process
• Revision cycle management
• Scheduled publishing
• Automated SEO optimization
• Social media integration
• Subscriber notifications

Business Benefits

• Consistent content quality
• Streamlined editorial workflow
• Automated publishing tasks
• Better SEO performance
• Increased content reach

Content Lifecycle

Start: DraftMiddle: Submitted, InReview, NeedsRevision, Approved, ScheduledEnd: Published, Archived

Content starts as a Draft where authors create and edit. Once Submitted, it moves to InReview for editorial assessment. Editors can either Approve for publication or request NeedsRevision, sending content back to Draft. Approved content can be Scheduled for future publication or immediately Published. After a period, published content is automatically Archived.

Transition Tasks

Each transition can have multiple tasks of each type (Restriction, Validation, Action), or none at all. Tasks are executed in order: Restriction → Validation → Action.

Transition	Restriction Tasks (Optional)	Validation Tasks (Optional)	Action Tasks (Optional)
Draft → Submitted	Check author permission	Validate content completeness Validate minimum word count Validate required fields are filled	Lock content for editing Notify editor
Submitted → InReview	Check editor assignment	Validate editor availability	Assign editor Create review task
InReview → Approved	Check editor role permission	Validate content quality standards Validate SEO requirements	Mark as approved Notify author
InReview → NeedsRevision	Check editor rejection permission	Validate revision notes are provided	Unlock content for editing Notify author with feedback
NeedsRevision → Draft	Check author edit permission	Validate revision completion	Unlock content Reset review status
Approved → Scheduled	Check publish date validity	Validate publish date format Validate date is in future	Set publish date Create scheduled job
Scheduled → Published	Check scheduled time reached	Validate publish conditions	Publish content Optimize SEO Generate sitemap Share on social media Notify subscribers
Published → Archived	Check archive period elapsed	Validate archive conditions	Move to archive Update sitemap Remove from active listings

Use Case: Manage content lifecycle with editorial review, revision cycles, and scheduled publishing. Automatically optimize SEO, generate sitemaps, share on social media, and notify subscribers when content is published. Archive old content after a specified period.

Real-World Implementation:

Perfect for blogs, news websites, content marketing platforms, and editorial teams. This workflow ensures that all content meets quality standards before publication while supporting iterative improvement through revision cycles. The automated SEO optimization and social media sharing maximize content reach and engagement without manual intervention.

Project Management Task Flow

Agile Task Management

Sprint-based task tracking with code review

Overview

The Project Management Task Flow implements an agile development workflow that tracks tasks from backlog through development, code review, and completion. This workflow supports sprint planning, tracks development time, manages code review processes, handles blocked tasks, and automatically calculates sprint velocity and burndown charts. It ensures proper code quality through mandatory review processes before task completion.

Key Features

• Sprint-based task management
• Time tracking integration
• Code review workflow
• Blocked task handling
• Automatic velocity calculation
• Burndown chart generation

Business Benefits

• Improved sprint visibility
• Better time management
• Enhanced code quality
• Accurate project tracking
• Data-driven decision making

Task Lifecycle

Start: BacklogMiddle: Todo, InProgress, InReview, BlockedEnd: Done

Tasks begin in the Backlog and move to Todo when added to a sprint. Developers move tasks to InProgress when starting work, triggering time tracking. Completed work moves to InReview for code review. Tasks can be Blocked if dependencies or issues arise, and return to InProgress when unblocked. After successful review, tasks are marked Done, updating sprint metrics.

Transition Tasks

Each transition can have multiple tasks of each type (Restriction, Validation, Action), or none at all. Tasks are executed in order: Restriction → Validation → Action.

Transition	Restriction Tasks (Optional)	Validation Tasks (Optional)	Action Tasks (Optional)
Backlog → Todo	Check sprint capacity	Validate task priority Validate dependencies are met	Add to sprint Update sprint backlog
Todo → InProgress	Check developer assignment	Validate task readiness	Assign developer Start timer Notify team
InProgress → InReview	Check code completion	Validate code quality Validate tests passed	Create pull request Assign reviewers Stop timer
InProgress → Blocked	Check blocking reason is provided	Validate blocking issue	Log blocker Notify team Update status
Blocked → InProgress	Check blocker resolved	Validate resolution	Remove blocker Resume timer Notify team
InReview → Done	Check reviewer approval	Validate all reviews passed	Merge code Update sprint velocity Calculate progress Generate burndown chart
InReview → InProgress	Check change request received	Validate feedback received	Reopen task Notify developer Reset review

Use Case: Manage agile development workflows with sprint tracking. Automatically update sprint velocity when tasks are completed, calculate project progress, notify team members when tasks are blocked, and generate burndown charts based on task state transitions.

Real-World Implementation:

Perfect for software development teams using agile methodologies like Scrum or Kanban. This workflow provides complete visibility into sprint progress, helps identify bottlenecks through blocked task tracking, and generates valuable metrics for sprint retrospectives. The mandatory code review ensures quality standards are maintained.

Customer Support Ticket System

Support Ticket Workflow

Priority-based ticket routing and escalation

Overview

The Customer Support Ticket System manages customer inquiries and issues through a priority-based routing system. High-priority tickets are automatically assigned to senior agents, while standard tickets are distributed based on agent availability. The workflow includes SLA tracking, automatic escalation for overdue tickets, customer response waiting states, and comprehensive ticket resolution tracking. This ensures timely response and proper issue resolution.

Key Features

• Priority-based auto-assignment
• SLA timer management
• Automatic escalation rules
• Customer response tracking
• Multi-channel support
• Resolution confirmation

Business Benefits

• Faster response times
• Improved customer satisfaction
• Better resource allocation
• SLA compliance tracking
• Reduced ticket backlog

Ticket Lifecycle

Start: New TicketMiddle: In Progress, Waiting for Customer, Escalated to ManagerEnd: Resolved, Closed

New tickets are automatically routed based on priority: high-priority tickets go to senior agents, while standard tickets are assigned to available agents. Tickets move to Waiting for Customer when agents need customer input, pausing SLA timers. High-priority tickets that exceed 24 hours are automatically Escalated to Manager. Once Resolved, tickets await customer confirmation before being Closed.

Transition Tasks

Each transition can have multiple tasks of each type (Restriction, Validation, Action), or none at all. Tasks are executed in order: Restriction → Validation → Action.

Transition	Restriction Tasks (Optional)	Validation Tasks (Optional)	Action Tasks (Optional)
New Ticket → In Progress	Check agent availability Check priority rules	Validate ticket data Validate category	Assign agent Start SLA timer Notify agent
In Progress → Waiting for Customer	Check customer response timeout	Validate no response received	Pause SLA timer Notify customer Set reminder
Waiting for Customer → In Progress	Check customer responded	Validate customer response	Resume SLA timer Notify agent Update status
In Progress → Resolved	Check resolution criteria met	Validate solution provided	Stop SLA timer Notify customer Request confirmation
In Progress → Escalated to Manager	Check escalation rules Check time threshold (24h for high priority)	Validate escalation reason	Assign to manager Notify manager Log escalation
Resolved → Closed	Check customer confirmation	Validate customer satisfaction	Close ticket Update statistics Archive ticket

Use Case: Automatically route tickets to appropriate agents based on category and priority. High-priority tickets are auto-escalated after 24 hours if not resolved. Maintain customer communication throughout the resolution process and automatically close tickets after customer confirmation.

Real-World Implementation:

Essential for customer service departments, help desks, and support centers. This workflow ensures that urgent issues receive immediate attention while maintaining efficient handling of routine inquiries. The automatic escalation prevents tickets from being forgotten, and the SLA tracking helps maintain service level agreements with customers.

Real Estate Property Listing

Property Listing Approval

Multi-stage property verification and publishing

Overview

The Real Estate Property Listing workflow manages property listings through a comprehensive verification process. Properties must pass photo review (minimum 5 photos) and document verification (title deed, ownership certificate) before being approved for publication. Once published, properties are automatically listed on multiple platforms, indexed in search engines, and interested buyers are notified. The workflow handles property sales and automatic archiving of expired listings.

Key Features

• Multi-stage verification
• Photo quality review
• Document verification
• Multi-platform publishing
• Search engine indexing
• Buyer notification system

Business Benefits

• Quality listing standards
• Increased property visibility
• Faster property sales
• Automated marketing
• Better buyer engagement

Verification Workflow

Start: DraftMiddle: PhotoReview, DocumentCheck, Approved, PublishedEnd: Sold, Archived

Properties start as Draft listings created by agents. After photos are uploaded, listings move to PhotoReview where a minimum of 5 quality photos must be approved. Approved photos lead to DocumentCheck where title deeds and ownership certificates are verified. Once Approved, properties are automatically Published to multiple platforms. Properties can be Sold or Archived when listings expire.

Transition Tasks

Each transition can have multiple tasks of each type (Restriction, Validation, Action), or none at all. Tasks are executed in order: Restriction → Validation → Action.

Transition	Restriction Tasks (Optional)	Validation Tasks (Optional)	Action Tasks (Optional)
Draft → PhotoReview	Check minimum photo count (5)	Validate photo quality Validate photo format	Upload photos Assign reviewer
PhotoReview → DocumentCheck	Check photos approved	Validate photo approval status	Proceed to document check Notify agent
PhotoReview → Draft	Check rejection reason provided	Validate rejection feedback	Notify agent Unlock listing
DocumentCheck → Approved	Check all documents verified	Validate title deed Validate ownership certificate	Mark as approved Ready for publishing
DocumentCheck → Draft	Check documents missing	Validate missing document list	Notify agent Request missing documents
Approved → Published	Check publish conditions	Validate all requirements met	Publish to platforms Index in search engines Notify interested buyers
Published → Sold	Check sale confirmation	Validate sale transaction	Mark as sold Remove from listings Notify agent
Published → Archived	Check listing expiration	Validate expiration date	Archive listing Remove from active Notify agent
Sold → Archived	Check sale completed	Validate sale finalization	Archive Remove from market Update records

Use Case: Manage property listings through verification stages. Ensure all required documents and photos are present before approval. Automatically publish to multiple listing platforms when approved, index in search engines, and notify interested buyers. Archive listings when sold or expired.

Real-World Implementation:

Ideal for real estate agencies, property management companies, and real estate platforms. This workflow ensures that only verified, high-quality listings are published, maintaining platform credibility. The multi-platform publishing maximizes property exposure, while automatic notifications keep interested buyers engaged throughout the listing lifecycle.

Loan Application Processing

Loan Application Workflow

Comprehensive loan processing with credit checks

Overview

The Loan Application Processing workflow manages the complete loan lifecycle from initial application through credit checks, document verification, multi-level approval, contract generation, and fund disbursement. The workflow implements amount-based routing where larger loans require higher-level approvals (Loan Officer → Senior Officer → Committee). Credit checks are performed early to filter out unqualified applicants, while document verification ensures all required paperwork is complete before approval.

Key Features

• Credit check integration
• Document verification
• Amount-based approval routing
• Multi-level authorization
• Contract generation
• E-signature support
• Fund disbursement tracking

Business Benefits

• Faster loan processing
• Reduced risk exposure
• Compliance with regulations
• Improved customer experience
• Automated workflow
• Better decision making

Loan Processing Workflow

Start: Application SubmittedMiddle: Initial Review, Document Verification, Loan Officer/Senior Officer/Committee Review, Contract Generation, Customer SignsEnd: Approved, Rejected, Funds Disbursed

Applications begin with Initial Review where credit checks are performed. Failed credit checks result in immediate Rejection. Successful applications proceed to Document Verification. Verified applications are routed to appropriate reviewers based on loan amount: small loans to Loan Officers, medium to Senior Officers, and large loans to Committee. Approved loans proceed to Contract Generation, then Customer Signs via e-signature, and finally Funds Disbursed.

Transition Tasks

Each transition can have multiple tasks of each type (Restriction, Validation, Action), or none at all. Tasks are executed in order: Restriction → Validation → Action.

Transition	Restriction Tasks (Optional)	Validation Tasks (Optional)	Action Tasks (Optional)
Application Submitted → Initial Review	Check application completeness	Validate application data Validate required fields	Assign reviewer Create review task
Initial Review → Document Verification	Check credit check passed	Validate credit score threshold	Proceed to document verification Notify customer
Initial Review → Rejected	Check credit check failed	Validate rejection reason	Notify customer Log rejection
Document Verification → Loan Officer/Senior Officer/Committee Review	Check amount threshold Check documents verified	Validate document authenticity Validate amount range	Route to appropriate reviewer Assign based on amount
Review → Approved	Check reviewer approval	Validate approval conditions met	Mark as approved Notify customer Proceed to contract
Review → Rejected	Check reviewer rejection	Validate rejection reason	Notify customer Log rejection
Approved → Contract Generation	Check approval status	Validate loan terms	Generate contract Prepare e-signature
Contract Generation → Customer Signs	Check contract generated	Validate contract completeness	Send for e-signature Notify customer
Customer Signs → Funds Disbursed	Check signature received	Validate signature authenticity	Disburse funds Update records Notify customer

Use Case: Process loan applications through multiple verification stages including credit checks, document verification, and approval routing based on loan amount. Automatically generate contracts, send for e-signature, and disburse funds upon completion.

Real-World Implementation:

Essential for banks, credit unions, and financial institutions processing loan applications. This workflow ensures compliance with lending regulations while streamlining the approval process. The early credit check filters out unqualified applicants, saving processing time. The amount-based routing ensures proper authorization levels while maintaining efficient processing for smaller loans. The automated contract generation and e-signature integration significantly reduce processing time.

Get Started

Ready to implement workflows in your application? Check out our comprehensive documentation:

⚙️

Installation

Install and configure Laravel Flow in your project

🚀

Quick Start

Start with HasFlow for simple single-flow scenarios

📚

Flow Service

Learn how to create and manage workflows