Plugin examples
Extension examples and neutral SDK fixtures demonstrating common integration patterns.
Core ships no plugin packages. The examples live in the separate plugin examples repository, with a Composer manifest, signals.yaml, source and package-owned Pest tests for each example. The repository is prepared locally for publication; these links become available when its maintainer publishes it.
Accounting service sync
Browse ledger-sync — package signals/ledger-sync.
This illustrative accounting-service integration uses an encrypted token setting, one allowlisted example host, an invoice.issued listener and a read-only MCP/CLI status tool. Its data declaration allows invoice reads and writes only to custom_fields.accounting_reference. A response containing a reference writes that custom field; configure the field in the host before using that path.
The HTTP tests fake the outbound response and verify that undeclared hosts and write fields remain blocked. api.accounting.example is a placeholder, and the package includes no real credentials or live service integration. The package name is retained for the example; it implies no official partnership. For recurring work and paginated reads, the SDK also provides jobs and schedules and list().
Slots demo
Browse slots-demo — package signals/slots-demo.
The UI example registers a rental header action, a grouped rental detail tab, a dashboard stat card and a global modal. A navigation group leads to a config-driven page with a datatable. Palette commands link to that page, and its provider records a recent visit through PluginContext.
The migration creates plugin_signals_slots_demo_notes. Its package-owned Eloquent model supplies the datatable and card count. Tests verify migration and rollback, slot permissions and development autoloading through a helper in tests/.
Acme Notify channel fixtures
The framework includes the SDK-only example-channel fixture: a secret webhook URL and a fixed destination, with no destination override. It uses PluginContext::http() and caller-supplied configuration rather than host models.
The webhook-card-channel, bot-token-channel and api-key-message-channel fixtures prove structured cards, OAuth installations and personal linking, verified addresses, callbacks and retries through the host pipeline. These are test fixtures, not published or separate reference packages. See Plugin Channel Providers for the Acme Notify walkthroughs and SDK v2 upgrade steps.
Install and test
Copy one package directory into plugins/signals/<name> in a development framework checkout. Run its checks and tests before enabling it:
php artisan signals:plugin check signals/slots-demo
php artisan signals:plugin test signals/slots-demo --compact
php artisan signals:plugin install signals/slots-demo
php artisan signals:plugin install signals/slots-demo --accept-capabilities=<reviewed-plan-hash>
php artisan signals:plugin enable signals/slots-demo
The first install command displays the capability plan. Review it before repeating the command with its exact hash. Open Extensions → Plugins (/plugins) to manage the package, permissions and settings. New runtime registrations become available on the next application boot.
On a framework revision with wiring validation, also run signals:plugin check signals/slots-demo --wire --json. The examples' matrix CI workflow runs that check and the package tests for all three directories. See Testing plugins for the test harness and generated editor stubs.