- Can I install freema/n8n-bundle in a Laravel application with Composer?
- Not as a Laravel package. It ships a Symfony Bundle subclass and DI Extension wired through Symfony's container, artifacts Laravel does not register or use. Composer may install it as a library if constraints allow, but you can only reuse it if the n8n client is decoupled from Symfony wiring; otherwise port the client or call n8n webhooks directly.
- Is freema/n8n-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It provides a Bundle subclass and dependency-injection extension, which have no meaning in Laravel's service-provider and container model. Laravel can consume Symfony components such as HttpClient, but it does not consume Symfony bundles, so the realistic fit is component-level reuse only if the core client is decoupled.
- How do I trigger an n8n workflow from Laravel without this package?
- Use Laravel's Http facade to post to the n8n webhook URL with the payload you need. For a basic trigger, Http::post($webhookUrl, $payload) is already a one-line integration. The bundle only justifies extra work if it adds workflow CRUD, credential handling, signature verification, async dispatch, retries, or similar value.
- What does freema/n8n-bundle provide beyond webhook triggering?
- The overview only confirms configurable webhook endpoints and helpers to trigger workflows and exchange data; it does not confirm workflow CRUD, executions, credential handling, or webhook signature verification. Read the source before assuming those features. If the bundle only triggers webhooks, Laravel's Http client already covers that in one line.
- Which n8n API version and authentication model does freema/n8n-bundle support?
- The provided context does not confirm which n8n API version or auth model it targets. n8n's public API has changed across versions, including API key versus JWT-era auth and endpoint changes, so a low-traffic wrapper may be pinned to one generation. Check the client code and Composer constraints before relying on it.
- Does freema/n8n-bundle support Laravel 10 or Laravel 11?
- There is no direct Laravel 10 or 11 support because this is a Symfony bundle. Laravel 10/11 on PHP 8.1+ already pulls Symfony components transitively, but registering this bundle is not applicable. If you attempt a port of a decoupled client, check symfony/http-client and symfony/config constraint conflicts at install time.
- How risky is adopting a five-star package like freema/n8n-bundle?
- High, and mostly because of maturity rather than code quality. The package shows 5 stars, 0 dependents, no evidence of production use, a single maintainer, and a composite score of 19.3 against an opportunity score of 25.7. It would sit on an authenticated path to an internal automation platform, so the upside is small relative to the blast radius; vendoring or forking shifts maintenance to you.
- Why does freema/n8n-bundle list a future release date?
- The listed last release date of 2026-10-01 is in the future, which is a registry metadata anomaly. Treat the release data as unreliable and verify Git tags, CHANGELOG, and Composer constraints directly. Do not trust any version claim until you confirm it from the repository.
- Is freema/n8n-bundle transport portable or tied to Symfony HttpClient?
- That is not confirmed in the overview or evaluation; you need to read the source. If the n8n client uses PSR-18/PSR-17 and is separated from Symfony's container, it is easier to wrap in a Laravel service provider. If it is hardcoded to Symfony HttpClient and fused to DI/config, porting cost and risk rise.
- What should I check before porting freema/n8n-bundle to Laravel?
- Timebox a half-day spike and answer six questions: whether the client is separated from Symfony's container, the real capability surface, target n8n API/auth version, PSR-18 transport, async/retry/idempotency support, and test/tag history. If the client is transport-portable and covers more than webhook triggering, a small Laravel provider may be feasible. If not, use Laravel's Http client for webhooks or build a minimal n8n client instead. Do not register the Symfony bundle in Laravel.