hadiabedzadeh / laravel-journey-builder
Reusable drag-and-drop journey orchestration for Laravel with SMS and allowlisted HTTP APIs
Package info
github.com/Hadi-Abedzadeh/laravel-journey-builder
pkg:composer/hadiabedzadeh/laravel-journey-builder
Requires
- php: ^8.2
- illuminate/console: ^12.0
- illuminate/database: ^12.0
- illuminate/http: ^12.0
- illuminate/routing: ^12.0
- illuminate/support: ^12.0
- illuminate/validation: ^12.0
Requires (Dev)
- orchestra/testbench: ^10.0
- phpunit/phpunit: ^11.0
Suggests
None
Provides
None
Conflicts
None
Replaces
None
This package is auto-updated.
Last update: 2026-11-07 13:57:54 UTC
README
Drag-and-drop journeys, per-flow enrollment and scheduling, SMS/HTTPS API actions, reports, encrypted per-node API credentials and safe operational commands. Laravel 12 / PHP 8.2+. Primary SQL Server support; migration has MySQL/PostgreSQL fallback. Preview only: no production SQL Server or SMS end-to-end test has been performed.
Read README_FA.md for installation, migration, schema compatibility, security and publishing to Packagist. The package is not yet published on Packagist; change the placeholder your-vendor in composer.json and publish your own Git repository.
Feature highlights
journey-builder:enroll,journey-builder:tick,journey-builder:status,journey-builder:retry(dry-run by default)- Package auto-discovery through
extra.laravel.providers - Dashboard routes and views loaded automatically; no built-in login/password/session management
- Authentication delegated to host Laravel app (default
manage-journeysGate, optionalauthmode) or loopback-only inlocaldevelopment - SQL Server initial schemas specify
VARCHAR,NVARCHAR,BIGINT,INT,SMALLINT,DATETIME2(3)explicitly - Existing
jb_*tables are not changed by the new migration; usesql/sqlsrv_audit.sqlto inspect legacy type mismatches - No destructive database rollback
- Only HTTP(S) allowlisted host API calls; per-node credentials encrypted with
APP_KEY
Recommended release workflow
See the Persian guide. Publish as a prerelease, such as v0.1.0-beta.1, until deployment and concurrency tests pass.