Use cases

Business apps keep growing processes: approvals, reminders, hand-overs, follow-ups, escalations. Written by hand, each one becomes status columns, scheduled jobs and “if overdue then…” checks that only a developer can change. Workflows for Laravel runs such processes as data instead: a versioned JSON graph of steps and arrows, stored in your own database and run step by step on your own queue. Developers decide what the engine may read and do; the people who own the process arrange those pieces into workflows.

• Purchase and expense approvals — check the amount, ask an approver or several stages of approvers, reassign to a manager after two business days without a decision, notify the requester and update the request.
• Contract and document review that has to finish within business days — waits and deadlines count weekdays or your opening hours, holidays and DST changes included.
• Customer requests answered within business hours — wait until the ticket is resolved, re-checked whenever it changes, and start a chase workflow after four business hours.
• Onboarding and offboarding — a checklist of your own domain steps (create a task, create the accounts) and a child workflow the parent waits for.
• Nightly and weekday jobs — a cron schedule in a chosen time zone, once, or once for every record that matches a condition.
• Software products whose customers set up their own approval and follow-up processes — per-team definitions, a visual builder you build on the package’s schemas, catalogue, validation, dry runs and overlay.

The package is the engine behind such an editor. It stores, checks, runs and reports on workflows; it does not include the editor screen. Approval, notify, transition, opening-hours and form steps switch on when the matching Roundly package is installed — everything else works on its own.